Skip to Content

Changes for page R14 Docker - Single Lane

Last modified by Erik Bakker on 2025/04/07 10:12
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 30.1
edited by Erik Bakker
on 2025/04/07 10:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R13 Docker - Single Lane
1 +R14 Docker - Single Lane
Content
... ... @@ -1,20 +1,19 @@
1 -Service affecting template to use the R13 single lane release.
1 +**Service affecting** template to use the R14 single 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 R14 template on your environment, we replace all your machines with new ones to activate the new configuration. This update is service affecting and aims to increase the stability of models running in Production.
5 5  
6 6  **Overview**
7 -* Security improvements to the eMagiz infrastructure.
8 -* Update control agent version.
7 +* Stability improvements to your **Production** model.
8 +* More control on resource management
9 9  
10 10  **Update Steps**
11 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
12 +** This step will upgrade the machines in your cloud slot
13 +*** The network drive containing the Artemis queue store and your Elastic IPs will remain.
15 15  
16 16  * User actions after applying the final template:
17 17  ** Check if all runtimes are up via the runtime overview
18 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
18 +** Check if messages pass through the model by verifying a critical message flow in external systems
20 20