Skip to Content

Changes for page R20 Docker - Double Lane

Last modified by Erik Bakker on 2026/02/10 10:51
From version 12.1
edited by Erik Bakker
on 2023/06/19 14:30
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 -R9 Docker - Double lane
1 +R20 Docker - Double Lane
Content
... ... @@ -1,27 +1,50 @@
1 -Service affecting R9 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture.
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 -We upgrade in two steps to use the new R9 release of the cloud template. Of these two steps, the intermediate step is non-service affecting, and the final step is 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 -It improves the ease with which Static IP Addresses can be gathered and distributed by a user while at the same time improving the security and auto-healing functionality.
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 -* Ability to fetch Static IP Addresses
11 -* New ubuntu version with new security patches.
12 -* Disable IPv6 on startup
13 -* Enable new Out of Memory killer to protect instance becoming unhealthy
14 -* Improved Cloud instance status check and auto repair
15 -
16 16  **Update Steps**
17 -* Use the intermediate template (non-service affecting) (duration: 10 minutes)
18 -** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot.
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.
19 19  ** The network drive containing the Artemis queue store and your Elastic IPs will remain.
20 -* Use the final template (service affecting) (duration: 10 minutes)
21 -** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
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
24 +
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 +
43 +**Update Steps**
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.
22 22  ** The runtimes on the machines will be restored using the active release in the eMagiz portal.
23 23  * User actions after applying the final template:
24 -** Check if all runtimes are reachable by Deploy Architecture.
25 -** Check if all flows have been installed according to the active release.
26 -** Check if messages pass through the model by verifying a critical message flow in external systems.
27 -
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