Skip to Content

Changes for page R21 Docker - Double Lane

Last modified by Erik Bakker on 2026/06/16 11:56
From version 33.1
edited by Erik Bakker
on 2026/06/15 09:37
Change comment: There is no comment for this version
To version 34.1
edited by Erik Bakker
on 2026/06/16 11:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,7 +3,7 @@
3 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 4  
5 5  **Process**
6 -We upgrade in one step to use the new **R19** release of the cloud template. This step is non-service affecting.
6 +We upgrade in one step to use the new **R21** release of the cloud template. This step is non-service affecting.
7 7  
8 8  **Overview**
9 9  * Upgrade cloud environment to prepare for IP address migration.
... ... @@ -10,12 +10,12 @@
10 10  * Update authorization server to enable future certificate rotations.
11 11  
12 12  **Update Steps**
13 -* Use the final **R19** template (non-service affecting) (duration: 10 minutes)
14 -** This step will upgrade the backup machines hosted in the second Availability Zone in your cloudslot.
13 +* Use the final **R21** template (non-service affecting) (duration: 10 minutes)
14 +** None of the runtimes will be touched.
15 15  ** The network drive containing the Artemis queue store and your Elastic IPs will remain.
16 -** The runtimes on the machines will be restored using the active release in the eMagiz portal
16 +** Authorization servers will perform a rolling update.
17 17  * User actions after applying the intermediate template:
18 -** Check if all ".02" runtimes are reachable by the runtime dashboard
18 +** Check if all runtimes are reachable by the runtime dashboard
19 19  ** Check if all flows have been installed according to the active release
20 20  ** Check if messages pass through the bus by verifying a critical message flow in external systems
21 21