Skip to Content

Changes for page R21 Docker - Double Lane

Last modified by Erik Bakker on 2026/06/16 11:56
From version 9.1
edited by Erik Bakker
on 2023/04/28 08:36
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 -R8 Docker - Double lane
1 +R21 Docker - Double Lane
Content
... ... @@ -1,16 +1,21 @@
1 -Non service affecting final template to use the R8 double lane release.
2 -Process: To use the new R8 release of our cloud template we upgrade in one steps, the update is non service affecting.
1 +{{info}}This environment template needs to be applied on all environments of all (your) models before August 15th, 2026{{/info}}
3 3  
4 -**Overview**
5 -This update improves the security and enhances the auto-healing functionality on our 3rd generation runtimes.
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.
6 6  
7 -**Updates**
8 -* Improve Locking mitigation in the Artemis server (autohealing).
9 -* Improve security by disabling SSH access to cloud machines.
5 +**Process**
6 +We upgrade in one step to use the new **R19** release of the cloud template. This step is non-service affecting.
10 10  
8 +**Overview**
9 +* Upgrade cloud environment to prepare for IP address migration.
10 +* Update authorization server to enable future certificate rotations.
11 +
11 11  **Update Steps**
12 -* Use the final R8 template (non service affecting) (duration: 4 minutes)
13 -* User actions after applying the final template:
14 -** Check if all runtimes are reachable by Deploy Architecture.
15 -** Check if all images have been installed according to the active release.
16 -** Check if messages pass through the bus 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 +