Changes for page R21 Docker - Double Lane
Last modified by Erik Bakker on 2026/06/16 11:56
From version 22.1
edited by Erik Bakker
on 2025/01/13 09:24
on 2025/01/13 09:24
Change comment:
There is no comment for this version
To version 34.1
edited by Erik Bakker
on 2026/06/16 11:56
on 2026/06/16 11:56
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 +R21 Docker - Double Lane - Content
-
... ... @@ -1,23 +1,21 @@ 1 - Service affectingfinaltemplate tousetheR15doublelane release.1 +{{info}}This environment template needs to be applied on all environments of all (your) models before August 15th, 2026{{/info}} 2 2 3 +**Non-service affecting** final template to use the **R21** double lane release. This is the only step for your upgrade to the new **R21** template. 4 + 3 3 **Process** 4 - To use the new R15release ofourcloud templatewe upgradeintwosteps,withonly the secondstep being service affecting.The goal of this update is to increase the security of the disks related to your machine by encrypting them and to update the control agent version to 2.21.4.6 +We upgrade in one step to use the new **R21** release of the cloud template. This step is non-service affecting. 5 5 6 6 **Overview** 7 -* SecurityimprovementstotheeMagizinfrastructure.8 -* Update controlagentversion.9 +* Upgrade cloud environment to prepare for IP address migration. 10 +* Update authorization server to enable future certificate rotations. 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 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 13 +* Use the final **R21** template (non-service affecting) (duration: 10 minutes) 14 +** None of the runtimes will be touched. 15 +** The network drive containing the Artemis queue store and your Elastic IPs will remain. 16 +** Authorization servers will perform a rolling update. 17 +* User actions after applying the intermediate template: 18 +** Check if all runtimes are reachable by the runtime dashboard 19 +** Check if all flows have been installed according to the active release 22 22 ** Check if messages pass through the bus by verifying a critical message flow in external systems 23 23