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 12.1
edited by Erik Bakker
on 2023/06/19 14:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R19 Docker - Double Lane
1 +R9 Docker - Double lane
Content
... ... @@ -1,15 +1,27 @@
1 -**Non-service-affecting** final template to use the **R19** single lane release.
1 +Service affecting R9 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture.
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 R9 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 +It improves the ease with which Static IP Addresses can be gathered and distributed by a user while at the same time improving the security and auto-healing functionality.
9 9  
9 +**Updates**
10 +* Ability to fetch Static IP Addresses
11 +* New ubuntu version with new security patches.
12 +* Disable IPv6 on startup
13 +* Enable new Out of Memory killer to protect instance becoming unhealthy
14 +* Improved Cloud instance status check and auto repair
15 +
10 10  **Update Steps**
11 -* Use the final R19 template (non-service affecting)(duration: < 5 minutes)
17 +* Use the intermediate template (non-service affecting) (duration: 10 minutes)
18 +** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot.
19 +** The network drive containing the Artemis queue store and your Elastic IPs will remain.
20 +* Use the final template (service affecting) (duration: 10 minutes)
21 +** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
22 +** The runtimes on the machines will be restored using the active release in the eMagiz portal.
23 +* User actions after applying the final template:
24 +** Check if all runtimes are reachable by Deploy Architecture.
25 +** Check if all flows have been installed according to the active release.
26 +** 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