Skip to Content

Changes for page R17 Docker - Double Lane

Last modified by Erik Bakker on 2025/06/30 09:51
From version 22.1
edited by Erik Bakker
on 2025/01/13 09:24
Change comment: There is no comment for this version
To version 26.1
edited by Erik Bakker
on 2025/06/30 09:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R15 Docker - Double Lane
1 +R17 Docker - Double Lane
Content
... ... @@ -1,23 +1,17 @@
1 -Service affecting final template to use the R15 double lane release.
1 +**Service affecting** final template to use the R16 double lane release.
2 2  
3 3  **Process**
4 -To use the new R15 release of our cloud template we upgrade in two steps, with only the second step being 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 +o use the new R17 template on your environment, we replace all connections to activate the new configuration. This update is service affecting and aims to enable data traffic via our new carwash.
5 5  
6 6  **Overview**
7 -* Security improvements to the eMagiz infrastructure.
8 -* Update control agent version.
7 +* New connections to a **new** carwash.
9 9  
10 10  **Update Steps**
11 -* Use this intermediate template (non service affecting)(duration: 10 minutes)
12 -** This step will upgrade the backup machines hosted in the second Availability Zone in your cloudslot
13 -*** The network drive containing the Artemis queue store and your Elastic IPs will remain.
14 -* Use the final template (service affecting)(duration: 10 minutes)
15 -** This step will upgrade the primary machines in the first Availability Zone in your cloudslot
16 -** This step will upgrade the control agent version on **all** machines (cloud and on-premise) to version 2.21.4
17 -*** The runtimes on the machines will be restored using the active release in the eMagiz portal
10 +* Use the final template (non service affecting)(duration: < 10 minutes)
11 +** This step will replace all connections.
18 18  
19 19  * User actions after applying the final template:
20 -** Check if all runtimes are up via the runtime overview
14 +** Check if all runtimes are up via the runtime overview or Deploy Architecture
21 21  ** Check if all runtimes have been installed according to the active release
22 22  ** Check if messages pass through the bus by verifying a critical message flow in external systems
23 23