Skip to Content

Changes for page R24 Docker - Double Lane

Last modified by Erik Bakker on 2026/10/09 13:13
From version 38.1
edited by Erik Bakker
on 2026/10/09 13:13
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 -R24 Docker - Double Lane
1 +R21 Docker - Double Lane
Content
... ... @@ -1,17 +1,21 @@
1 -{{info}}This environment template needs to be applied on all environments of all (your) models before November 18th, 2026{{/info}}
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 **R24** double lane release. This is the only step for your upgrade to the new R24 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 **R24** release of our cloud template we upgrade in one step, which is non-service affecting
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 -* Preparation for updating our databases underneath the authorization server
9 +* Upgrade cloud environment to prepare for IP address migration.
10 +* Update authorization server to enable future certificate rotations.
10 10  
11 11  **Update Steps**
12 -* Use this final R24 template (non-service affecting) (duration: 10 minutes)
13 -** None of the runtimes will be touched.
14 -* User actions after applying the final template:
15 -** Check if all runtimes are reachable by Deploy Architecture.
16 -** Check if all flows have been installed according to the active release.
17 -** Check if messages pass through the model by verifying a critical message flow in external systems.
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
20 +** Check if messages pass through the bus by verifying a critical message flow in external systems
21 +