Skip to Content

Changes for page R17 Docker - Single Lane

Last modified by Erik Bakker on 2025/10/23 08:46
From version 29.1
edited by Erik Bakker
on 2025/01/20 07:40
Change comment: There is no comment for this version
To version 34.1
edited by Erik Bakker
on 2025/10/09 10:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R13 Docker - Single Lane
1 +R16 Docker - Single Lane
Content
... ... @@ -1,21 +1,19 @@
1 -Service affecting template to use the R13 single lane release.
1 +**Non-service-affecting** final template to use the **R16** double lane release.
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 +To use the new R16 release of our cloud template we upgrade in one step. This step is non-service-affecting.
5 5  
6 6  **Overview**
7 -* Security improvements to the eMagiz infrastructure.
8 -* Update control agent version.
7 +* Update versions of dependencies.
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 -*** 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
10 +* Use the final R16 template (non-service affecting)(duration: < 5 minutes)
16 16  
17 17  * User actions after applying the final template:
18 -** Check if all runtimes are up via the runtime overview
13 +** Check if all runtimes are up via the runtime overview or Deploy Architecture
19 19  ** Check if all runtimes have been installed according to the active release
20 20  ** Check if messages pass through the bus by verifying a critical message flow in external systems
21 21  
17 +**Remarks**
18 +
19 +Deadline of December 14th, 2025