Skip to Content

Changes for page R16 Docker - Double Lane

Last modified by Erik Bakker on 2025/04/07 10:15
From version 17.1
edited by Carlijn Kokkeler
on 2024/03/25 11:59
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 -R14 Docker - Double Lane
1 +R6 Docker - Double lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,20 +1,17 @@
1 -Non-service affecting final template to use the R14 double lane release.
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 -To use the new R14 release of our cloud template we upgrade in one step. The update is non-service affecting.
5 -
6 6  **Overview**
7 -This version contains the ability to clean H2 infra databases from the portal.
5 +This update changes the Cloud port check, coordination faled and clean store functionality on our 3rd generation runtimes.
8 8  
9 9  **Updates**
10 -* Ubuntu version update including latest security patches.
11 -* This upgrade is non-service affecting, as all instances have to be recreated.
12 -* This upgrade contains the ability to clean H2 infra databases from the portal.
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"]]
13 13  
14 14  **Update Steps**
15 -* Use the final R14 template (non-service affecting) (duration: 3 minutes)
13 +* Use the final R6 template (non service affecting) (duration: 4 minutes)
16 16  * User actions after applying the final template:
17 -** Check if all ".01" runtimes are reachable by the runtime dashboard.
15 +** Check if all runtimes are reachable by the runtime dashboard.
18 18  ** Check if all flows have been installed according to the active release.
19 19  ** Check if messages pass through the bus by verifying a critical message flow in external systems.
20 -