Skip to Content

Changes for page R13 Docker - Double Lane

Last modified by Carlijn Kokkeler on 2023/11/21 11:51
From version 14.1
edited by Erik Bakker
on 2023/08/03 16:16
Change comment: There is no comment for this version
To version 8.1
edited by Erik Bakker
on 2023/03/03 11:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R10 Docker - Double lane
1 +R6 Docker - Double lane
Content
... ... @@ -1,19 +1,17 @@
1 -Non-service affecting R10 template that unlocks the possibility of running a failover configuration on an MQTT Broker.
1 +Non service affecting final template to use the R6 double lane release.
2 +Process: To use the new R6 release of our cloud template we upgrade in one steps, the update is non service affecting.
2 2  
3 -**Process**
4 -We upgrade in one step to use the new R10 release of the cloud template. This step is non-service affecting.
5 -
6 6  **Overview**
7 -It adds the possibility of hosting an MQTT broker in a failover setting.
5 +This update changes the Cloud port check, coordination faled and clean store functionality on our 3rd generation runtimes.
8 8  
9 9  **Updates**
10 -* Run an MQTT broker in a failover setting
8 +* Cloud Port check: When the software does not expose the right ports, it will be restarted
9 +* Coordnation failed: When the runtimes failes to startup due to a corrupted startup order, the runtime will restart freshly to remove the corrupted state.
10 +* Clean store: The functionality to clean a store is added for generation 3 runtimes. See [[this link>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.eMagiz Cloud Management.expert-emagiz-cloud-management-clean-store||target="blank"]]
11 11  
12 12  **Update Steps**
13 -* Use the final template (non-service affecting) (duration: 10 minutes)
14 -** This step will update your cloud slot configuration to allow an MQTT broker with failover settings.
13 +* Use the final R6 template (non service affecting) (duration: 4 minutes)
15 15  * User actions after applying the final template:
16 -** Check if all runtimes are reachable by Deploy Architecture.
15 +** Check if all runtimes are reachable by the runtime dashboard.
17 17  ** Check if all flows have been installed according to the active release.
18 -** Check if messages pass through the model by verifying a critical message flow in external systems.
19 -
17 +** Check if messages pass through the bus by verifying a critical message flow in external systems.