Skip to Content

Changes for page R21 Docker - Double Lane

Last modified by Erik Bakker on 2026/06/16 11:56
From version 32.1
edited by Erik Bakker
on 2026/02/10 10:51
Change comment: There is no comment for this version
To version 33.1
edited by Erik Bakker
on 2026/06/15 09:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R20 Docker - Double Lane
1 +R21 Docker - Double Lane
Content
... ... @@ -1,19 +1,16 @@
1 -=== Intermediate Template - Release Notes ===
1 +{{info}}This environment template needs to be applied on all environments of all (your) models before August 15th, 2026{{/info}}
2 2  
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.
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 4  
5 5  **Process**
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.
6 +We upgrade in one step to use the new **R19** release of the cloud template. This step is non-service affecting.
7 7  
8 8  **Overview**
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)
9 +* Upgrade cloud environment to prepare for IP address migration.
10 +* Update authorization server to enable future certificate rotations.
14 14  
15 15  **Update Steps**
16 -* Use this intermediate R20 template (non-service affecting)(duration: 15 minutes)
13 +* Use the final **R19** template (non-service affecting) (duration: 10 minutes)
17 17  ** This step will upgrade the backup machines hosted in the second Availability Zone in your cloudslot.
18 18  ** The network drive containing the Artemis queue store and your Elastic IPs will remain.
19 19  ** The runtimes on the machines will be restored using the active release in the eMagiz portal
... ... @@ -22,29 +22,3 @@
22 22  ** Check if all flows have been installed according to the active release
23 23  ** Check if messages pass through the bus by verifying a critical message flow in external systems
24 24  
25 -**Remarks**
26 -
27 -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.
28 -
29 -=== Final Template - Release Notes ===
30 -
31 -**Service affecting** final template to use the R20 double lane release.
32 -
33 -**Process**
34 -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.
35 -
36 -**Overview**
37 -* Security improvements to the eMagiz infrastructure
38 -* Update Ubuntu version
39 -* Update Docker version
40 -* Update control agent version
41 -* Update Authorization Server (if applicable)
42 -
43 -**Update Steps**
44 -* Use the final R20 template (non-service affecting)(duration: 15 minutes)
45 -** This step will upgrade the primary machines in the first Availability Zone in your cloudslot.
46 -** The runtimes on the machines will be restored using the active release in the eMagiz portal.
47 -* User actions after applying the final template:
48 -** Check if all ".01" runtimes are reachable by the runtime dashboard
49 -** Check if all flows have been installed according to the active release
50 -** Check if messages pass through the bus by verifying a critical message flow in external systems