Changes for page R20 - Double lane
Last modified by Carlijn Kokkeler on 2024/01/18 11:42
From 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
To version 12.1
edited by Carlijn Kokkeler
on 2023/10/11 16:08
on 2023/10/11 16:08
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 -R 20- Double lane1 +R19 - Double lane - Content
-
... ... @@ -1,17 +1,22 @@ 1 - Non-service affecting R20template that improvesautohealing.1 +Service affecting R19 template that improve NFS performance. 2 2 3 3 **Process** 4 -We upgrade in o nestep to use the new R20release of the cloud template.This step is non-service affecting.4 +We upgrade in two steps to use the new R19 release of the cloud template. Of these two steps, the intermediate step is non-service affecting, and the final step is service affecting. 5 5 6 6 **Overview** 7 -This version contains auto healingperformance improvements.7 +This version contains performance improvements for NFS. 8 8 9 9 **Updates** 10 -* Update including a utohealingperformanceimprovements.11 -* This upgrade is non-service10 +* Ubuntu version update including latest security patches. 11 +* This upgrade is service-affecting, as all instances have to be recreated. 12 12 13 13 **Update Steps** 14 -* Use the final template (non-service affecting) 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. 15 15 * User actions after applying the final template: 16 16 ** Check if all runtimes are reachable by Deploy Architecture. 17 17 ** Check if all flows have been installed according to the active release.