Skip to Content

Changes for page R16 Docker - Double Lane

Last modified by Erik Bakker on 2025/04/07 10:15
From version 22.1
edited by Erik Bakker
on 2025/01/13 09:24
Change comment: There is no comment for this version
To version 14.1
edited by Erik Bakker
on 2023/08/03 16:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R15 Docker - Double Lane
1 +R10 Docker - Double lane
Content
... ... @@ -1,23 +1,19 @@
1 -Service affecting final template to use the R15 double lane release.
1 +Non-service affecting R10 template that unlocks the possibility of running a failover configuration on an MQTT Broker.
2 2  
3 3  **Process**
4 -To use the new R15 release of our cloud template we upgrade in two steps, with only the second step being service affecting. The goal of this update is to increase the security of the disks related to your machine by encrypting them and to update the control agent version to 2.21.4.
4 +We upgrade in one step to use the new R10 release of the cloud template. This step is non-service affecting.
5 5  
6 6  **Overview**
7 -* Security improvements to the eMagiz infrastructure.
8 -* Update control agent version.
7 +It adds the possibility of hosting an MQTT broker in a failover setting.
9 9  
10 -**Update Steps**
11 -* Use this intermediate template (non service affecting)(duration: 10 minutes)
12 -** This step will upgrade the backup machines hosted in the second Availability Zone in your cloudslot
13 -*** The network drive containing the Artemis queue store and your Elastic IPs will remain.
14 -* Use the final template (service affecting)(duration: 10 minutes)
15 -** This step will upgrade the primary machines in the first Availability Zone in your cloudslot
16 -** This step will upgrade the control agent version on **all** machines (cloud and on-premise) to version 2.21.4
17 -*** The runtimes on the machines will be restored using the active release in the eMagiz portal
9 +**Updates**
10 +* Run an MQTT broker in a failover setting
18 18  
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.
19 19  * User actions after applying the final template:
20 -** Check if all runtimes are up via the runtime overview
21 -** Check if all runtimes have been installed according to the active release
22 -** Check if messages pass through the bus by verifying a critical message flow in external systems
16 +** Check if all runtimes are reachable by Deploy Architecture.
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.
23 23