Skip to Content

Changes for page R21 Docker - Double Lane

Last modified by Erik Bakker on 2026/06/16 11:56
From version 34.1
edited by Erik Bakker
on 2026/06/16 11:56
Change comment: There is no comment for this version
To version 11.1
edited by Erik Bakker
on 2023/06/19 14:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R21 Docker - Double Lane
1 +R9 Docker - Double lane
Content
... ... @@ -1,21 +1,27 @@
1 -{{info}}This environment template needs to be applied on all environments of all (your) models before August 15th, 2026{{/info}}
1 +Service affecting R9 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture.
2 2  
3 -**Non-service affecting** final template to use the **R21** double lane release. This is the only step for your upgrade to the new **R21** template.
4 -
5 5  **Process**
6 -We upgrade in one step to use the new **R21** 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.
7 7  
8 8  **Overview**
9 -* Upgrade cloud environment to prepare for IP address migration.
10 -* Update authorization server to enable future certificate rotations.
7 +It improves the ease with which Static IP Addresses can be gathered and distributed by a user while at the same thing improving the security by upgrading the Ubuntu version and auto-healing functionality.
11 11  
9 +**Updates**
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
15 +
12 12  **Update Steps**
13 -* Use the final **R21** template (non-service affecting) (duration: 10 minutes)
14 -** None of the runtimes will be touched.
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.
15 15  ** The network drive containing the Artemis queue store and your Elastic IPs will remain.
16 -** Authorization servers will perform a rolling update.
17 -* User actions after applying the intermediate template:
18 -** Check if all runtimes are reachable by the runtime dashboard
19 -** Check if all flows have been installed according to the active release
20 -** Check if messages pass through the bus by verifying a critical message flow in external systems
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.
23 +* User actions after applying the final template:
24 +** Check if all runtimes are reachable by Deploy Architecture.
25 +** Check if all flows have been installed according to the active release.
26 +** Check if messages pass through the model by verifying a critical message flow in external systems.
21 21