Skip to Content

Changes for page R16 Docker - Double Lane

Last modified by Erik Bakker on 2025/04/07 10:15
From version 15.1
edited by Erik Bakker
on 2023/09/13 07:27
Change comment: There is no comment for this version
To version 25.1
edited by Erik Bakker
on 2025/04/07 10:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R11 Docker - Double lane
1 +R16 Docker - Double Lane
Content
... ... @@ -1,24 +1,19 @@
1 -Service affecting R11 template that improves stability of AWS EFS mounts in running instances when a reconnect to EFS is triggered.
1 +**Non-service affecting** final template to use the R16 double lane release.
2 2  
3 3  **Process**
4 -We upgrade in two steps to use the new R11 release of the cloud template. Of these two steps, the intermediate step is non-service affecting, and the final step is service affecting.
4 +To use the new R16 release of our cloud template we upgrade in one steps, the update is non service affecting. This update aims to increase the stability of models running in Production.
5 5  
6 6  **Overview**
7 -It improves the stability of the AWS EFS mounts in running instances when a reconnect to EFS is triggered.
7 +* Security improvements to the eMagiz infrastructure.
8 +* Update control agent version.
8 8  
9 -**Updates**
10 -* Updated mount configurations of EFS to adhere to provider's standards.
11 -* Ubuntu version update including latest security patches.
12 -* This upgrade is service-affecting, as all instances have to be recreated.
13 -
14 14  **Update Steps**
15 -* Use the intermediate template (non-service affecting) (duration: 10 minutes)
16 -** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot.
17 -** The network drive containing the Artemis queue store and your Elastic IPs will remain.
18 -* Use the final template (non-service affecting) (duration: 10 minutes)
19 -** This step will update your cloud slot configuration to allow an MQTT broker with failover settings.
11 +* Use the final template (non service affecting)(duration: 3 minutes)
12 +** This step will upgrade the machines in your cloudslot
13 +*** The network drive containing the Artemis queue store and your Elastic IPs will remain.
14 +
20 20  * User actions after applying the final template:
21 -** Check if all runtimes are reachable by Deploy Architecture.
22 -** Check if all flows have been installed according to the active release.
23 -** Check if messages pass through the model by verifying a critical message flow in external systems.
16 +** Check if all runtimes are up via the runtime overview
17 +** Check if all runtimes have been installed according to the active release
18 +** Check if messages pass through the bus by verifying a critical message flow in external systems
24 24