Skip to Content

Changes for page R19 Docker - Double Lane

Last modified by Erik Bakker on 2025/10/23 08:47
From version 16.1
edited by Carlijn Kokkeler
on 2023/11/21 11:51
Change comment: There is no comment for this version
To version 28.1
edited by Erik Bakker
on 2025/10/09 10:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R13 Docker - Double Lane
1 +R18 Docker - Double Lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,24 +1,19 @@
1 -Service affecting template that introduces faster machine boot up and improved auto-healing.
1 +**Non-service-affecting** final template to use the *R18* double lane release.
2 2  
3 3  **Process**
4 -We upgrade in two steps to use the new R13 release of the cloud template. Of these two steps, the intermediate step is non-service affecting, and the final step is service affecting.
4 +To use the new R18 release of our cloud template we upgrade in one step. This step is non-service-affecting.
5 5  
6 6  **Overview**
7 -This version contains performance improvements for auto-healing and machine boot up time.
7 +* Update versions of dependencies.
8 8  
9 -**Updates**
10 -* Ubuntu version update including latest security patches.
11 -* This upgrade is service-affecting, as all instances have to be recreated.
12 -
13 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.
10 +* Use the final R*18* template (non-service affecting)(duration: < 5 minutes)
11 +
20 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.
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
24 24  
17 +**Remarks**
18 +
19 +Deadline of December 14th, 2025