Changes for page R11 Docker - Single Lane

Last modified by Carlijn Kokkeler on 2023/11/21 11:47

From version 19.1
edited by Carlijn Kokkeler
on 2023/11/21 11:47
Change comment: There is no comment for this version
To version 13.1
edited by Erik Bakker
on 2023/04/28 08:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R11 Docker - Single Lane
1 +R7 - Docker Single lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,21 +1,15 @@
1 -Service affecting template that introduces faster machine boot up and improved auto-healing.
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.
2 2  
3 -**Process**
4 -We upgrade in one step to use the new R11 release of the cloud template. This step is service affecting.
5 -
6 6  **Overview**
7 -This version contains performance improvements for auto-healing and machine boot up time.
5 +This update improves the security by disabling SSH access to cloud machines.
8 8  
9 9  **Updates**
10 -* Ubuntu version update including latest security patches.
11 -* This upgrade is service-affecting, as all instances have to be recreated.
8 +* Improve security by disabling SSH access to cloud machines.
12 12  
13 13  **Update Steps**
14 -* Use the final template (service affecting) (duration: 10 minutes)
15 -** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
16 -** The runtimes on the machines will be restored using the active release in the eMagiz portal.
11 +* Use the final R7 template (non service affecting) (duration: 4 minutes)
17 17  * User actions after applying the final template:
18 18  ** Check if all runtimes are reachable by Deploy Architecture.
19 -** Check if all flows have been installed according to the active release.
20 -** Check if messages pass through the model by verifying a critical message flow in external systems.
21 -
14 +** Check if all images have been installed according to the active release.
15 +** Check if messages pass through the bus by verifying a critical message flow in external systems.