Changes for page R20 - Double lane
Last modified by Carlijn Kokkeler on 2024/01/18 11:42
From version 11.1
edited by Erik Bakker
on 2023/06/19 14:31
on 2023/06/19 14:31
Change comment:
There is no comment for this version
To version 13.1
edited by Carlijn Kokkeler
on 2024/01/15 13:34
on 2024/01/15 13:34
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 18- Double lane1 +R20 - Double lane - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,23 +1,17 @@ 1 - Service affecting R18template that improvessecurity and allowsfor theretrievalof Static IP addresses from Deploy Architecture.1 +Non-service affecting R20 template that improves auto healing. 2 2 3 3 **Process** 4 -We upgrade in two stepsto use the new R18release of the cloud template.Of thesetwosteps,theintermediatestepisnonservice affecting, and the final step is service affecting.4 +We upgrade in one step to use the new R20 release of the cloud template. This step is non-service affecting. 5 5 6 6 **Overview** 7 - Itimprovestheease withwhich Static IP Addressescan be gatheredanddistributed by a userwhileat thesame time improving thesecurity and auto-healing functionality.7 +This version contains auto healing performance improvements. 8 8 9 9 **Updates** 10 -* Ability to fetch Static IP Addresses 11 -* New Ubuntu version with new security patches. 12 -* Improved Cloud instance status check and auto repair 10 +* Update including auto healing performance improvements. 11 +* This upgrade is non-service affecting. 13 13 14 14 **Update Steps** 15 -* Use the intermediate template (non-service affecting) (duration: 4 minutes) 16 -** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot. 17 -** The network drive containing the Artemis queue store and your Elastic IPs will remain. 18 -* Use the final template (service affecting) (duration: 4 minutes) 19 -** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot. 20 -** The runtimes on the machines will be restored using the active release in the eMagiz portal. 14 +* Use the final template (non-service affecting) 21 21 * User actions after applying the final template: 22 22 ** Check if all runtimes are reachable by Deploy Architecture. 23 23 ** Check if all flows have been installed according to the active release.