Skip to Content

Changes for page R19 Docker - Double Lane

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R19 Docker - Double Lane
1 +R13 Docker - 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 **R19** single lane release.
1 +Service affecting template that introduces faster machine boot up and improved auto-healing.
2 2  
3 3  **Process**
4 -To use the new R19 release of our cloud template we upgrade in one step. This is a rolling update, making it non-service affecting.
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.
5 5  
6 6  **Overview**
7 -* Non-service-affecting template to upgrade to the latest version of the authorization server. Applying this template only affects customers running on DSH Event Streaming.
8 -* Update the version of authorization server as preparation for the API-Gateway MAM migration.
7 +This version contains performance improvements for auto-healing and machine boot up time.
9 9  
9 +**Updates**
10 +* Ubuntu version update including latest security patches.
11 +* This upgrade is service-affecting, as all instances have to be recreated.
12 +
10 10  **Update Steps**
11 -* Use the final R19 template (non-service affecting)(duration: < 5 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.
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.
12 12  
13 -**Remarks**
14 -
15 -Deadline of December 14th, 2025