Changes for page R9 Docker - Double lane
Last modified by Erik Bakker on 2023/07/10 15:13
From version 8.1
edited by Erik Bakker
on 2023/03/03 11:30
on 2023/03/03 11:30
Change comment:
There is no comment for this version
To version 9.1
edited by Erik Bakker
on 2023/04/28 08:36
on 2023/04/28 08:36
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -R 6Docker - Double lane1 +R8 Docker - Double lane - Content
-
... ... @@ -1,17 +1,16 @@ 1 -Non service affecting final template to use the R 6double lane release.2 -Process: To use the new R 6release of our cloud template we upgrade in one steps, the update is non service affecting.1 +Non service affecting final template to use the R8 double lane release. 2 +Process: To use the new R8 release of our cloud template we upgrade in one steps, the update is non service affecting. 3 3 4 4 **Overview** 5 -This update changes theCloud port check, coordinationfaled andcleanre functionality on our 3rd generation runtimes.5 +This update improves the security and enhances the auto-healing functionality on our 3rd generation runtimes. 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"]] 8 +* Improve Locking mitigation in the Artemis server (autohealing). 9 +* Improve security by disabling SSH access to cloud machines. 11 11 12 12 **Update Steps** 13 -* Use the final R 6template (non service affecting) (duration: 4 minutes)12 +* Use the final R8 template (non service affecting) (duration: 4 minutes) 14 14 * User actions after applying the final template: 15 -** Check if all runtimes are reachable by the runtimedashboard.16 -** Check if all flows have been installed according to the active release.14 +** Check if all runtimes are reachable by Deploy Architecture. 15 +** Check if all images 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.