Changes for page R18 Docker - Double Lane
Last modified by Erik Bakker on 2025/10/10 09:12
From version 24.1
edited by Erik Bakker
on 2025/01/20 07:40
on 2025/01/20 07:40
Change comment:
There is no comment for this version
To version 27.1
edited by Erik Bakker
on 2025/10/09 10:11
on 2025/10/09 10:11
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 +R18 Docker - Double Lane - Content
-
... ... @@ -1,24 +1,16 @@ 1 - Service5double lane release.1 +**Non-service-affecting** final template to use the *R18* double 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 thisupdate istoincreasethe security of the disks related to your machineby encrypting themand to updatethecontrol agent versionto 2.21.4 for **all** machines.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 -* Security improvements to the eMagiz infrastructure. 8 -* Update control agent version. 7 +* Update versions of dependencies. 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 -*** The network drive containing the Artemis queue store and your Elastic IPs will remain. 17 -** This step will upgrade the control agent version on **all** machines (cloud and on-premise) to version 2.21.4 18 -*** 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) 19 19 20 20 * User actions after applying the final template: 21 -** Check if all runtimes are up via the runtime overview 13 +** Check if all runtimes are up via the runtime overview or Deploy Architecture 22 22 ** Check if all runtimes have been installed according to the active release 23 23 ** Check if messages pass through the bus by verifying a critical message flow in external systems 24 24