Skip to Content

Changes for page R14 Docker - Single Lane

Last modified by Erik Bakker on 2025/04/07 10:12
From version 30.1
edited by Erik Bakker
on 2025/04/07 10:12
Change comment: There is no comment for this version
To version 18.1
edited by Erik Bakker
on 2023/09/13 07:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R14 Docker - Single Lane
1 +R9 Docker - Single lane
Content
... ... @@ -1,19 +1,22 @@
1 -**Service affecting** template to use the R14 single lane release.
1 +Service affecting R9 template that improves stability of AWS EFS mounts in running instances when a reconnect to EFS is triggered.
2 2  
3 3  **Process**
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.
4 +We upgrade in one step to use the new R9 release of the cloud template. This step is service affecting.
5 5  
6 6  **Overview**
7 -* Stability improvements to your **Production** model.
8 -* More control on resource management
7 +It improves the stability of the AWS EFS mounts in running instances when a reconnect to EFS is triggered.
9 9  
10 -**Update Steps**
11 -* Use the final template (service affecting)(duration: 10 minutes)
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.
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.
14 14  
14 +**Update Steps**
15 +* Use the final template (service affecting) (duration: 10 minutes)
16 +** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
17 +** The runtimes on the machines will be restored using the active release in the eMagiz portal.
15 15  * User actions after applying the final template:
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 model by verifying a critical message flow in external systems
19 +** Check if all runtimes are reachable by Deploy Architecture.
20 +** Check if all flows have been installed according to the active release.
21 +** Check if messages pass through the model by verifying a critical message flow in external systems.
19 19