Skip to Content

Changes for page R21 Docker - Double Lane

Last modified by Erik Bakker on 2026/06/16 11:56
From version 26.1
edited by Erik Bakker
on 2025/06/30 09: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 -R17 Docker - Double Lane
1 +R21 Docker - Double Lane
Content
... ... @@ -1,17 +1,21 @@
1 -**Service affecting** final template to use the R16 double lane release.
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** final template to use the **R21** double lane release. This is the only step for your upgrade to the new **R21** template.
4 +
3 3  **Process**
4 -o use the new R17 template on your environment, we replace all connections to activate the new configuration. This update is service affecting and aims to enable data traffic via our new carwash.
6 +We upgrade in one step to use the new **R19** release of the cloud template. This step is non-service affecting.
5 5  
6 6  **Overview**
7 -* New connections to a **new** carwash.
9 +* Upgrade cloud environment to prepare for IP address migration.
10 +* Update authorization server to enable future certificate rotations.
8 8  
9 9  **Update Steps**
10 -* Use the final template (non service affecting)(duration: < 10 minutes)
11 -** This step will replace all connections.
12 -
13 -* User actions after applying the final template:
14 -** Check if all runtimes are up via the runtime overview or Deploy Architecture
15 -** Check if all runtimes have been installed according to the active release
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
16 16  ** Check if messages pass through the bus by verifying a critical message flow in external systems
17 17