Skip to Content

Changes for page R21 Docker - Double Lane

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R14 Docker - Double Lane
1 +R21 Docker - Double Lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,20 +1,21 @@
1 -Non-service affecting final template to use the R14 double lane 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 R14 release of our cloud template we upgrade in one step. The update is non-service affecting.
6 +We upgrade in one step to use the new **R19** release of the cloud template. This step is non-service affecting.
5 5  
6 6  **Overview**
7 -This version contains the ability to clean H2 infra databases from the portal.
9 +* Upgrade cloud environment to prepare for IP address migration.
10 +* Update authorization server to enable future certificate rotations.
8 8  
9 -**Updates**
10 -* Ubuntu version update including latest security patches.
11 -* This upgrade is non-service affecting, as all instances have to be recreated.
12 -* This upgrade contains the ability to clean H2 infra databases from the portal.
13 -
14 14  **Update Steps**
15 -* Use the final R14 template (non-service affecting) (duration: 3 minutes)
16 -* User actions after applying the final template:
17 -** Check if all ".01" runtimes are reachable by the runtime dashboard.
18 -** Check if all flows have been installed according to the active release.
19 -** Check if messages pass through the bus by verifying a critical message flow in external systems.
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.
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
17 +* User actions after applying the intermediate template:
18 +** Check if all ".02" runtimes are reachable by the runtime dashboard
19 +** Check if all flows have been installed according to the active release
20 +** Check if messages pass through the bus by verifying a critical message flow in external systems
20 20