Changes for page R20 - Double lane
Last modified by Carlijn Kokkeler on 2024/01/18 11:42
From version 9.1
edited by Erik Bakker
on 2023/06/06 08:04
on 2023/06/06 08:04
Change comment:
There is no comment for this version
To version 7.1
edited by Erik Bakker
on 2023/05/09 14:00
on 2023/05/09 14:00
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 -R1 8- Double lane1 +R17 - Double lane - Content
-
... ... @@ -1,24 +1,17 @@ 1 -Service affecting R18 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture. 1 +Non service affecting final template to use the R17 double lane release. 2 +Process: To use the new R17 release of our cloud template we upgrade in one steps, the update is non service affecting. 2 2 3 - **Process**4 - Weupgrade in twosteps to use thenew R18 releaseof thecloudtemplate.Ofthesetwosteps, theintermediate stepisnonserviceaffecting,andthefinalstepisserviceffecting.4 +Overview 5 +This update improves the security and enhances the auto-healing functionality on our 3rd generation runtimes. 5 5 6 -**Overview** 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. 7 +Updates 8 8 9 - **Updates**10 - *AbilitytofetchStaticIPAddresses11 - * NewUbuntu versionwith new securitypatches.9 +Improve Locking mitigation in the Artemis server (autohealing). 10 +Improve security by disabling SSH access to cloud machines. 11 +Update Steps 12 12 13 -**Update Steps** 14 -* Use the intermediate template (non-service affecting) (duration: 4 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: 4 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. 20 -* User actions after applying the final template: 21 -** Check if all runtimes are reachable by Deploy Architecture. 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 - 13 +Use the final R17 template (non service affecting) (duration: 4 minutes) 14 +User actions after applying the final template: 15 +Check if all runtimes are reachable by Deploy Architecture. 16 +Check if all images have been installed according to the active release. 17 +Check if messages pass through the bus by verifying a critical message flow in external systems.