Skip to Content

Changes for page R20 Docker - Double Lane

Last modified by Erik Bakker on 2026/02/10 10:51
From version 20.1
edited by CarlijnKokkeler
on 2024/03/29 13:47
Change comment: There is no comment for this version
To version 32.1
edited by Erik Bakker
on 2026/02/10 10:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R14 Docker - Double Lane
1 +R20 Docker - Double Lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,19 +1,50 @@
1 -Non-service affecting final template to use the R14 double lane release.
1 +=== Intermediate Template - Release Notes ===
2 2  
3 +**Non-service affecting** intermediate template to use the R20 double lane release. This is the first of two steps for your upgrade to the new R20 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 +To use the new R20 release of our cloud template we upgrade in two steps, with only the second step being service affecting. Below is the first step.
5 5  
6 6  **Overview**
7 -This version contains the ability to clean H2 infra databases from the portal.
9 +* Security improvements to the eMagiz infrastructure
10 +* Update Ubuntu version
11 +* Update Docker version
12 +* Update control agent version
13 +* Update Authorization Server (if applicable)
8 8  
9 -**Updates**
10 -* This upgrade contains the ability to clean H2 infra databases from the portal.
11 -* This upgrade is non-service affecting.
15 +**Update Steps**
16 +* Use this intermediate R20 template (non-service affecting)(duration: 15 minutes)
17 +** This step will upgrade the backup machines hosted in the second Availability Zone in your cloudslot.
18 +** The network drive containing the Artemis queue store and your Elastic IPs will remain.
19 +** The runtimes on the machines will be restored using the active release in the eMagiz portal
20 +* User actions after applying the intermediate template:
21 +** Check if all ".02" runtimes are reachable by the runtime dashboard
22 +** Check if all flows have been installed according to the active release
23 +** Check if messages pass through the bus by verifying a critical message flow in external systems
12 12  
25 +**Remarks**
26 +
27 +To allow the user to have more control of the upgrade process we now allow to upgrade to the intermediate template as a seperate step. This gives you the option to wait longer before updating the **service affecting** final template. In this time you can do additional verifications on your model.
28 +
29 +=== Final Template - Release Notes ===
30 +
31 +**Service affecting** final template to use the R20 double lane release.
32 +
33 +**Process**
34 +To use the new R20 release of our cloud template we upgrade in two steps, with only the second step being service affecting. Below is the remaining step.
35 +
36 +**Overview**
37 +* Security improvements to the eMagiz infrastructure
38 +* Update Ubuntu version
39 +* Update Docker version
40 +* Update control agent version
41 +* Update Authorization Server (if applicable)
42 +
13 13  **Update Steps**
14 -* Use the final R14 template (non-service affecting) (duration: 3 minutes)
44 +* Use the final R20 template (non-service affecting)(duration: 15 minutes)
45 +** This step will upgrade the primary machines in the first Availability Zone in your cloudslot.
46 +** The runtimes on the machines will be restored using the active release in the eMagiz portal.
15 15  * User actions after applying the final template:
16 -** Check if all ".01" runtimes are reachable by the runtime overview.
17 -** Check if all flows have been installed according to the active release.
18 -** Check if messages pass through the bus by verifying a critical message flow in external systems.
19 -
48 +** Check if all ".01" runtimes are reachable by the runtime dashboard
49 +** Check if all flows have been installed according to the active release
50 +** Check if messages pass through the bus by verifying a critical message flow in external systems