Skip to Content

Changes for page R19 - Double lane

Last modified by Carlijn Kokkeler on 2023/10/11 16:08
From version 6.1
edited by Erik Bakker
on 2023/04/28 08:41
Change comment: There is no comment for this version
To version 12.1
edited by Carlijn Kokkeler
on 2023/10/11 16:08
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R17 - Double lane
1 +R19 - Double lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,15 +1,24 @@
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.
1 +Service affecting R19 template that improve NFS performance.
3 3  
3 +**Process**
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 +
4 4  **Overview**
5 -This update improves the auto-healing functionality of our current generation runtime architecture. In this cloud template an earlier bug surrounding the "lock reclaim" auto-healing has been fixed.
7 +This version contains performance improvements for NFS.
6 6  
7 7  **Updates**
8 - * Improve Locking mitigation in the Artemis server (autohealing)
10 +* Ubuntu version update including latest security patches.
11 +* This upgrade is service-affecting, as all instances have to be recreated.
9 9  
10 10  **Update Steps**
11 -* Use the final R17 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.
12 12  * User actions after applying the final template:
13 -** Check if all runtimes are reachable by the runtime dashboard.
21 +** Check if all runtimes are reachable by Deploy Architecture.
14 14  ** Check if all flows 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.
23 +** Check if messages pass through the model by verifying a critical message flow in external systems.
24 +