Skip to Content

Changes for page R19 Docker - Single Lane

Last modified by Erik Bakker on 2026/03/22 21:42
From version 40.1
edited by Erik Bakker
on 2026/03/22 21:42
Change comment: There is no comment for this version
To version 12.2
edited by Erik Bakker
on 2023/03/03 11:29
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R19 Docker - Single Lane
1 +R6 - Docker Single lane
Content
... ... @@ -1,17 +1,17 @@
1 -**Service affecting** final template to use the **R19** single lane release. This upgrade is service-affecting, as all instances have to be recreated.
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 -**Process**
4 -We upgrade in one step to use the new **R19** release of the cloud template. This step is service affecting.
5 -
6 6  **Overview**
7 -* Remove need for recycling underlying instance when adding containers to machine
5 +This update changes the Cloud port check, coordination faled and clean store functionality on our 3rd generation runtimes.
8 8  
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"]]
11 +
9 9  **Update Steps**
10 -* Use the final **R19** template (service affecting) (duration: 15 minutes)
13 +* Use the final R6 template (non service affecting) (duration: 4 minutes)
11 11  * User actions after applying the final template:
12 -** Check if all runtimes are reachable by Deploy Architecture.
15 +** Check if all runtimes are reachable by the runtime dashboard.
13 13  ** Check if all flows have been installed according to the active release.
14 -** Check if messages pass through the model by verifying a critical message flow in external systems.
15 -
16 -**Remarks**
17 -Adding/moving/deleting containers from machines will now not replace the underlying instances. This was only the case for singlelanes. Doublelanes do not have this behaviour and are not affected.
17 +** Check if messages pass through the bus by verifying a critical message flow in external systems.