Skip to Content

Changes for page R21 Docker - Double Lane

Last modified by Erik Bakker on 2026/06/16 11:56
From version 33.1
edited by Erik Bakker
on 2026/06/15 09:37
Change comment: There is no comment for this version
To version 24.1
edited by Erik Bakker
on 2025/01/20 07:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R21 Docker - Double Lane
1 +R15 Docker - Double Lane
Content
... ... @@ -1,21 +1,24 @@
1 -{{info}}This environment template needs to be applied on all environments of all (your) models before August 15th, 2026{{/info}}
1 +Service affecting final template to use the R15 double lane release.
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 **R19** release of the cloud template. This step is non-service affecting.
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 for **all** machines.
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 +* Security improvements to the eMagiz infrastructure.
8 +* Update control agent version.
11 11  
12 12  **Update Steps**
13 -* Use the final **R19** template (non-service affecting) (duration: 10 minutes)
14 -** This step will upgrade the backup machines hosted in the second Availability Zone in your cloudslot.
15 -** The network drive containing the Artemis queue store and your Elastic IPs will remain.
16 -** The runtimes on the machines will be restored using the active release in the eMagiz portal
17 -* User actions after applying the intermediate template:
18 -** Check if all ".02" runtimes are reachable by the runtime dashboard
19 -** Check if all flows have been installed according to the active release
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 +*** The network drive containing the Artemis queue store and your Elastic IPs will remain.
17 +** This step will upgrade the control agent version on **all** machines (cloud and on-premise) to version 2.21.4
18 +*** The runtimes on the machines will be restored using the active release in the eMagiz portal
19 +
20 +* User actions after applying the final template:
21 +** Check if all runtimes are up via the runtime overview
22 +** Check if all runtimes have been installed according to the active release
20 20  ** Check if messages pass through the bus by verifying a critical message flow in external systems
21 21