Skip to Content

Changes for page R17 Docker - Single Lane

Last modified by Erik Bakker on 2025/10/23 08:46
From version 12.2
edited by Erik Bakker
on 2023/03/03 11:29
Change comment: Update document after refactoring.
To version 23.1
edited by Carlijn Kokkeler
on 2024/03/29 13:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R6 - Docker Single lane
1 +R12 Docker - Single Lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,17 +1,19 @@
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.
1 +Non-service affecting template to use the R12 single lane release.
3 3  
3 +**Process**
4 + To use the new R12 release of our cloud template we upgrade in one step. The update is non-service affecting.
5 +
4 4  **Overview**
5 -This update changes the Cloud port check, coordination faled and clean store functionality on our 3rd generation runtimes.
7 +This version contains the ability to clean H2 infra databases from the portal.
6 6  
7 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"]]
10 +* This upgrade contains the ability to clean H2 infra databases from the portal.
11 +* This upgrade is non-service affecting.
11 11  
12 12  **Update Steps**
13 -* Use the final R6 template (non service affecting) (duration: 4 minutes)
14 +* Use the final R12 template (non-service affecting) (duration: 3 minutes)
14 14  * User actions after applying the final template:
15 -** Check if all runtimes are reachable by the runtime dashboard.
16 +** Check if all runtimes are reachable by the runtime overview.
16 16  ** Check if all flows have been installed according to the active release.
17 17  ** Check if messages pass through the bus by verifying a critical message flow in external systems.
19 +