Changes for page R16 Docker - Double Lane
Last modified by Erik Bakker on 2025/04/07 10:15
From 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
To version 17.1
edited by Carlijn Kokkeler
on 2024/03/25 11:59
on 2024/03/25 11:59
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -R 8Docker - Doublelane1 +R14 Docker - Double Lane - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,16 +1,20 @@ 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. 1 +Non-service affecting final template to use the R14 double lane release. 3 3 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 + 4 4 **Overview** 5 -This update improves the security andenhances the auto-healing functionality onour3rd generationruntimes.7 +This version contains the ability to clean H2 infra databases from the portal. 6 6 7 7 **Updates** 8 -* Improve Locking mitigation in the Artemis server (autohealing). 9 -* Improve security by disabling SSH access to cloud machines. 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. 10 10 11 11 **Update Steps** 12 -* Use the final R 8template (non4minutes)15 +* Use the final R14 template (non-service affecting) (duration: 3 minutes) 13 13 * User actions after applying the final template: 14 -** Check if all runtimes are reachable by DeployArchitecture.15 -** Check if all images have been installed according to the active release.17 +** Check if all ".01" runtimes are reachable by the runtime dashboard. 18 +** Check if all flows have been installed according to the active release. 16 16 ** Check if messages pass through the bus by verifying a critical message flow in external systems. 20 +