Skip to Content

Changes for page R19 Docker - Single Lane

Last modified by Erik Bakker on 2026/03/22 21:42
From version 40.1
edited by Erik Bakker
on 2026/03/22 21:42
Change comment: There is no comment for this version
To version 29.1
edited by Erik Bakker
on 2025/01/20 07:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R19 Docker - Single Lane
1 +R13 Docker - Single Lane
Content
... ... @@ -1,17 +1,21 @@
1 -**Service affecting** final template to use the **R19** single lane release. This upgrade is service-affecting, as all instances have to be recreated.
1 +Service affecting template to use the R13 single lane release.
2 2  
3 3  **Process**
4 -We upgrade in one step to use the new **R19** release of the cloud template. This step is service affecting.
4 +To use the new R13 template on your environment, we upgrade the control agent of **all** machines and disk encryption on **cloud** machines. This update is 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.
5 5  
6 6  **Overview**
7 -* Remove need for recycling underlying instance when adding containers to machine
7 +* Security improvements to the eMagiz infrastructure.
8 +* Update control agent version.
8 8  
9 9  **Update Steps**
10 -* Use the final **R19** template (service affecting) (duration: 15 minutes)
11 +* Use the final template (service affecting)(duration: 10 minutes)
12 +** This step will upgrade the primary machines in the first Availability Zone in your cloudslot
13 +*** The network drive containing the Artemis queue store and your Elastic IPs will remain.
14 +** This step will upgrade the control agent version on **all** machines (cloud and on-premise) to version 2.21.4
15 +*** The runtimes on the machines will be restored using the active release in the eMagiz portal
16 +
11 11  * User actions after applying the final template:
12 -** Check if all runtimes are reachable by Deploy Architecture.
13 -** Check if all flows have been installed according to the active release.
14 -** Check if messages pass through the model by verifying a critical message flow in external systems.
18 +** Check if all runtimes are up via the runtime overview
19 +** Check if all runtimes 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
15 15  
16 -**Remarks**
17 -Adding/moving/deleting containers from machines will now not replace the underlying instances. This was only the case for singlelanes. Doublelanes do not have this behaviour and are not affected.