Skip to Content

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 14.1
edited by Erik Bakker
on 2023/06/06 08:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R7 - Docker Single lane
1 +R8 - Docker Single lane
Content
... ... @@ -1,15 +1,21 @@
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 +Service affecting R8 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture.
3 3  
3 +**Process**
4 +We upgrade in one step to use the new R8 release of the cloud template. This step is service affecting.
5 +
4 4  **Overview**
5 -This update improves the security by disabling SSH access to cloud machines.
7 +It improves the ease with which Static IP Addresses can be gathered and distributed by a user while at the same thing improving the security by upgrading the Ubuntu version.
6 6  
7 7  **Updates**
8 -* Improve security by disabling SSH access to cloud machines.
10 +* Ability to fetch Static IP Addresses
11 +* New Ubuntu version with new security patches.
9 9  
10 10  **Update Steps**
11 -* Use the final R7 template (non service affecting) (duration: 4 minutes)
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.
12 12  * User actions after applying the final template:
13 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 messages pass through the bus by verifying a critical message flow in external systems.
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 +