Skip to Content

Changes for page R16 Docker - Double Lane

Last modified by Erik Bakker on 2025/04/07 10:15
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 25.1
edited by Erik Bakker
on 2025/04/07 10:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R10 Docker - Double lane
1 +R16 Docker - Double Lane
Content
... ... @@ -1,19 +1,19 @@
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 R16 double lane release.
2 2  
3 3  **Process**
4 -We upgrade in one step to use the new R10 release of the cloud template. This step is non-service affecting.
4 +To use the new R16 release of our cloud template we upgrade in one steps, the update is non service affecting. This update aims to increase the stability of models running in Production.
5 5  
6 6  **Overview**
7 -It adds the possibility of hosting an MQTT broker in a failover setting.
7 +* Security improvements to the eMagiz infrastructure.
8 +* Update control agent version.
8 8  
9 -**Updates**
10 -* Run an MQTT broker in a failover setting
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.
11 +* Use the final template (non service affecting)(duration: 3 minutes)
12 +** This step will upgrade the machines in your cloudslot
13 +*** The network drive containing the Artemis queue store and your Elastic IPs will remain.
14 +
15 15  * User actions after applying the final template:
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.
16 +** Check if all runtimes are up via the runtime overview
17 +** Check if all runtimes have been installed according to the active release
18 +** Check if messages pass through the bus by verifying a critical message flow in external systems
19 19