Changes for page R19 Docker - Double Lane
Last modified by Erik Bakker on 2025/10/23 08:47
From version 23.1
edited by Erik Bakker
on 2025/01/13 09:26
on 2025/01/13 09:26
Change comment:
There is no comment for this version
To version 30.1
edited by Erik Bakker
on 2025/10/23 08:47
on 2025/10/23 08:47
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -R1 5Docker - Double Lane1 +R19 Docker - Double Lane - Content
-
... ... @@ -1,23 +1,15 @@ 1 - Serviceaffecting final template to use the R15double lane release.1 +**Non-service-affecting** final template to use the **R19** single lane release. 2 2 3 3 **Process** 4 -To use the new R1 5release of our cloud template we upgrade intwosteps, with only the second stepbeing service affecting. The goal of thisupdateisto increasethe securityof the disksrelatedto yourmachine by encrypting themand toupdate the control agent versionto 2.21.4 for **all** machines.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. 5 5 6 6 **Overview** 7 -* Securityimprovementsto theeMagizinfrastructure.8 -* Update controlagentversion.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. 9 9 10 10 **Update Steps** 11 -* Use this intermediate template (non service affecting)(duration: 10 minutes) 12 -** This step will upgrade the backup machines hosted in the second Availability Zone in your cloudslot 13 -*** The network drive containing the Artemis queue store and your Elastic IPs will remain. 14 -* Use the final template (service affecting)(duration: 10 minutes) 15 -** This step will upgrade the primary machines in the first Availability Zone in your cloudslot 16 -** This step will upgrade the control agent version on **all** machines (cloud and on-premise) to version 2.21.4 17 -*** The runtimes on the machines will be restored using the active release in the eMagiz portal 11 +* Use the final R19 template (non-service affecting)(duration: < 5 minutes) 18 18 19 -* User actions after applying the final template: 20 -** Check if all runtimes are up via the runtime overview 21 -** Check if all runtimes have been installed according to the active release 22 -** Check if messages pass through the bus by verifying a critical message flow in external systems 13 +**Remarks** 23 23 15 +Deadline of December 14th, 2025