Skip to Content

Changes for page R9 Docker - Double lane

Last modified by Erik Bakker on 2023/07/10 15:13
From version 9.1
edited by Erik Bakker
on 2023/04/28 08:36
Change comment: There is no comment for this version
To version 10.1
edited by Erik Bakker
on 2023/06/06 08:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R8 Docker - Double lane
1 +R9 Docker - Double lane
Content
... ... @@ -1,16 +1,24 @@
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 +Service affecting R9 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture.
3 3  
3 +**Process**
4 +We upgrade in two steps to use the new R9 release of the cloud template. Of these two steps, the intermediate step is non-service affecting, and the final step is service affecting.
5 +
4 4  **Overview**
5 -This update improves the security and enhances the auto-healing functionality on our 3rd generation runtimes.
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 Locking mitigation in the Artemis server (autohealing).
9 -* Improve security by disabling SSH access to cloud machines.
10 +* Ability to fetch Static IP Addresses
11 +* New Ubuntu version with new security patches.
10 10  
11 11  **Update Steps**
12 -* Use the final R8 template (non service affecting) (duration: 4 minutes)
14 +* Use the intermediate template (non-service affecting) (duration: 10 minutes)
15 +** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot.
16 +** The network drive containing the Artemis queue store and your Elastic IPs will remain.
17 +* Use the final template (service affecting) (duration: 10 minutes)
18 +** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
19 +** The runtimes on the machines will be restored using the active release in the eMagiz portal.
13 13  * User actions after applying the final template:
14 14  ** Check if all runtimes are reachable by Deploy Architecture.
15 -** Check if all images have been installed according to the active release.
16 -** Check if messages pass through the bus by verifying a critical message flow in external systems.
22 +** Check if all flows have been installed according to the active release.
23 +** Check if messages pass through the model by verifying a critical message flow in external systems.
24 +