Skip to Content

Changes for page R22 - Double lane

Last modified by Erik Bakker on 2025/10/09 10:14
From version 19.1
edited by Erik Bakker
on 2025/10/09 10:14
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 -R22 - Double lane
1 +R19 - Double lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,16 +1,24 @@
1 -**Non-service-affecting** final template to use the **R22** double lane release.
1 +Service affecting R19 template that improve NFS performance.
2 2  
3 3  **Process**
4 -To use the new R22 release of our cloud template we upgrade in one step. 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 -* Update versions of dependencies.
7 +This version contains performance improvements for NFS.
8 8  
9 -**Update Steps**
10 -* Use the final R22 template (non-service affecting)(duration: < 5 minutes)
9 +**Updates**
10 +* Ubuntu version update including latest security patches.
11 +* This upgrade is service-affecting, as all instances have to be recreated.
11 11  
13 +**Update Steps**
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 up via the runtime overview or Deploy Architecture
14 -** Check if all runtimes 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
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.
16 16