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 12.1
edited by Erik Bakker
on 2023/06/19 14: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 +R9 Docker - Double lane
Content
... ... @@ -1,17 +1,25 @@
1 -Non-service affecting R10 template that unlocks the possibility of running a failover configuration on an MQTT Broker.
1 +Service affecting R9 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture.
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 +We upgrade in two steps to use the new R9 release of the cloud template. Of these two steps, the intermediate step is non-service affecting, and the final step is service affecting.
5 5  
6 6  **Overview**
7 -It adds the possibility of hosting an MQTT broker in a failover setting.
7 +It improves the ease with which Static IP Addresses can be gathered and distributed by a user while at the same time improving the security and auto-healing functionality.
8 8  
9 9  **Updates**
10 -* Run an MQTT broker in a failover setting
10 +* Ability to fetch Static IP Addresses
11 +* New ubuntu version with new security patches.
12 +* Disable IPv6 on startup
13 +* Enable new Out of Memory killer to protect instance becoming unhealthy
14 +* Improved Cloud instance status check and auto repair
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.
17 +* Use the intermediate template (non-service affecting) (duration: 10 minutes)
18 +** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot.
19 +** The network drive containing the Artemis queue store and your Elastic IPs will remain.
20 +* Use the final template (service affecting) (duration: 10 minutes)
21 +** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
22 +** The runtimes on the machines will be restored using the active release in the eMagiz portal.
15 15  * User actions after applying the final template:
16 16  ** Check if all runtimes are reachable by Deploy Architecture.
17 17  ** Check if all flows have been installed according to the active release.