Skip to Content

Changes for page R22 Docker - Double Lane

Last modified by Erik Bakker on 2026/06/29 09:47
From version 25.1
edited by Erik Bakker
on 2025/04/07 10:15
Change comment: There is no comment for this version
To version 36.1
edited by Erik Bakker
on 2026/06/29 09:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R16 Docker - Double Lane
1 +R22 Docker - Double Lane
Content
... ... @@ -1,19 +1,20 @@
1 -**Non-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 29th, 2026{{/info}}
2 2  
3 +**Non-service affecting** final template to use the **R22** double lane release. This is the only step for your upgrade to the new **R22** template.
4 +
3 3  **Process**
4 -To use the new R16 release of our cloud template we upgrade in one steps, the update is non service affecting. This update aims to increase the stability of models running in Production.
6 +We upgrade in one step to use the new **R22** release of the cloud template. This step is non-service affecting.
5 5  
6 6  **Overview**
7 -* Security improvements to the eMagiz infrastructure.
8 -* Update control agent version.
9 +* Improve internal monitoring and alerting capabilities
10 +* Improve management of users and permissions
9 9  
10 10  **Update Steps**
11 -* Use the final template (non service affecting)(duration: 3 minutes)
12 -** This step will upgrade the machines in your cloudslot
13 -*** The network drive containing the Artemis queue store and your Elastic IPs will remain.
14 -
13 +* Use the final **R22** template (non-service affecting) (duration: 10 minutes)
14 +** None of the runtimes will be touched.
15 +** Authorization servers will perform a rolling update.
15 15  * User actions after applying the final template:
16 -** Check if all runtimes are up via the runtime overview
17 -** Check if all runtimes have been installed according to the active release
18 -** Check if messages pass through the bus by verifying a critical message flow in external systems
17 +** Check if all runtimes are reachable by Deploy Architecture.
18 +** Check if all flows have been installed according to the active release.
19 +** Check if messages pass through the model by verifying a critical message flow in external systems.
19 19