Skip to Content

Changes for page R18 Docker - Single Lane

Last modified by Erik Bakker on 2026/02/10 10:59
From version 28.1
edited by Erik Bakker
on 2025/01/13 09:26
Change comment: There is no comment for this version
To version 39.1
edited by Erik Bakker
on 2026/02/10 10:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R13 Docker - Single Lane
1 +R18 Docker - Single Lane
Content
... ... @@ -1,20 +1,21 @@
1 -Service affecting template to use the R13 single lane release.
1 +**Service affecting** final template to use the **R18** single lane release. This upgrade is service-affecting, as all instances have to be recreated.
2 2  
3 3  **Process**
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.
4 +We upgrade in one step to use the new **R18** release of the cloud template. This step is service affecting.
5 5  
6 6  **Overview**
7 -* Security improvements to the eMagiz infrastructure.
8 -* Update control agent version.
7 +* Security improvements to the eMagiz infrastructure
8 +* Update Ubuntu version
9 +* Update Docker version
10 +* Update control agent version
11 +* Update Authorization Server (if applicable)
9 9  
10 10  **Update Steps**
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 -** This step will upgrade the control agent version on **all** machines (cloud and on-premise) to version 2.21.4
14 -*** The runtimes on the machines will be restored using the active release in the eMagiz portal
15 -
14 +* Use the final **R18** template (service affecting) (duration: 15 minutes)
16 16  * User actions after applying the final template:
17 -** Check if all runtimes are up via the runtime overview
18 -** Check if all runtimes 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
16 +** Check if all runtimes are reachable by Deploy Architecture.
17 +** Check if all flows have been installed according to the active release.
18 +** Check if messages pass through the model by verifying a critical message flow in external systems.
20 20  
20 +**Remarks**
21 +In case your model is running fully on-premise you need to upgrade your agents by upgrading to the next available template (R3).