Skip to Content

Changes for page R22 Docker - Double Lane

Last modified by Erik Bakker on 2026/06/29 09:47
From version 35.1
edited by Erik Bakker
on 2026/06/29 09:46
Change comment: There is no comment for this version
To version 8.1
edited by Erik Bakker
on 2023/03/03 11:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R22 Docker - Double Lane
1 +R6 Docker - Double lane
Content
... ... @@ -1,20 +1,17 @@
1 -{{info}}This environment template needs to be applied on all environments of all (your) models before August 29th, 2026{{/info}}
1 +Non service affecting final template to use the R6 double lane release.
2 +Process: To use the new R6 release of our cloud template we upgrade in one steps, the update is non service affecting.
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 -
5 -**Process**
6 -We upgrade in one step to use the new **R22** release of the cloud template. This step is non-service affecting.
7 -
8 8  **Overview**
9 -* Improve internal monitoring and alerting capabilities
10 -* Improve management of users and permissions
5 +This update changes the Cloud port check, coordination faled and clean store functionality on our 3rd generation runtimes.
11 11  
12 -**Update Steps**
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.
16 -* User actions after applying the intermediate template:
17 -** Check if all runtimes are reachable by the runtime dashboard
18 -** Check if all flows have been installed according to the active release
19 -** Check if messages pass through the bus by verifying a critical message flow in external systems
7 +**Updates**
8 +* Cloud Port check: When the software does not expose the right ports, it will be restarted
9 +* Coordnation failed: When the runtimes failes to startup due to a corrupted startup order, the runtime will restart freshly to remove the corrupted state.
10 +* Clean store: The functionality to clean a store is added for generation 3 runtimes. See [[this link>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.eMagiz Cloud Management.expert-emagiz-cloud-management-clean-store||target="blank"]]
20 20  
12 +**Update Steps**
13 +* Use the final R6 template (non service affecting) (duration: 4 minutes)
14 +* User actions after applying the final template:
15 +** Check if all runtimes are reachable by the runtime dashboard.
16 +** Check if all flows have been installed according to the active release.
17 +** Check if messages pass through the bus by verifying a critical message flow in external systems.