Changes for page R12 Docker - Single Lane

Last modified by Carlijn Kokkeler on 2024/03/29 13:47

From version 13.1
edited by Erik Bakker
on 2023/04/28 08:34
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 -R7 - Docker Single lane
1 +R6 - Docker Single lane
Content
... ... @@ -1,15 +1,17 @@
1 -Non service affecting final template to use the R7 single lane release.
2 -Process: To use the new R7 release of our cloud template we upgrade in one steps, the update is non service affecting.
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.
3 3  
4 4  **Overview**
5 -This update improves the security by disabling SSH access to cloud machines.
5 +This update changes the Cloud port check, coordination faled and clean store functionality on our 3rd generation runtimes.
6 6  
7 7  **Updates**
8 -* Improve security by disabling SSH access to cloud machines.
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"]]
9 9  
10 10  **Update Steps**
11 -* Use the final R7 template (non service affecting) (duration: 4 minutes)
13 +* Use the final R6 template (non service affecting) (duration: 4 minutes)
12 12  * User actions after applying the final template:
13 -** Check if all runtimes are reachable by Deploy Architecture.
14 -** Check if all images have been installed according to the active release.
15 +** Check if all runtimes are reachable by the runtime dashboard.
16 +** Check if all flows have been installed according to the active release.
15 15  ** Check if messages pass through the bus by verifying a critical message flow in external systems.