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 31.1
edited by Erik Bakker
on 2026/02/10 10:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R21 Docker - Double Lane
1 +R20 Docker - Double Lane
Content
... ... @@ -1,21 +1,52 @@
1 -{{info}}This environment template needs to be applied on all environments of all (your) models before August 15th, 2026{{/info}}
1 +=== Intermediate Template - Release Notes ===
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.
3 +**Non-service affecting** intermediate template to use the R20 double lane release. This is the first of two steps for your upgrade to the new R20 template.
4 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.
6 +To use the new R20 release of our cloud template we upgrade in two steps, with only the second step being service affecting. Below is the first step.
7 7  
8 8  **Overview**
9 -* Upgrade cloud environment to prepare for IP address migration.
10 -* Update authorization server to enable future certificate rotations.
9 +* Security improvements to the eMagiz infrastructure
10 +* Update Ubuntu version
11 +* Update Docker version
12 +* Update control agent version
13 +* Update Authorization Server (if applicable)
11 11  
12 12  **Update Steps**
13 -* Use the final **R21** template (non-service affecting) (duration: 10 minutes)
14 -** None of the runtimes will be touched.
16 +* Use this intermediate R20 template (non-service affecting)(duration: < 15 minutes)
17 +** 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
19 +** The runtimes on the machines will be restored using the active release in the eMagiz portal
21 21  
21 +User actions after applying the intermediate template:
22 +Check if all ".02" runtimes are reachable by the runtime dashboard
23 +Check if all flows have been installed according to the active release
24 +Check if messages pass through the bus by verifying a critical message flow in external systems
25 +
26 +**Remarks**
27 +
28 +To allow the user to have more control of the upgrade process we now allow to upgrade to the intermediate template as a seperate step. This gives you the option to wait longer before updating the **service affecting** final template. In this time you can do additional verifications on your model.
29 +
30 +=== Final Template - Release Notes ===
31 +
32 +**Service affecting** final template to use the R20 double lane release.
33 +
34 +**Process**
35 +To use the new R20 release of our cloud template we upgrade in two steps, with only the second step being service affecting. Below is the remaining step.
36 +
37 +**Overview**
38 +* Security improvements to the eMagiz infrastructure
39 +* Update Ubuntu version
40 +* Update Docker version
41 +* Update control agent version
42 +* Update Authorization Server (if applicable)
43 +
44 +**Update Steps**
45 +* Use the final R20 template (non-service affecting)(duration: < 15 minutes)
46 +** This step will upgrade the primary machines in the first Availability Zone in your cloudslot.
47 +** The runtimes on the machines will be restored using the active release in the eMagiz portal.
48 +
49 +User actions after applying the final template:
50 +Check if all ".01" runtimes are reachable by the runtime dashboard
51 +Check if all flows have been installed according to the active release
52 +Check if messages pass through the bus by verifying a critical message flow in external systems