Skip to Content

Changes for page R17 Docker - Single Lane

Last modified by Erik Bakker on 2025/10/23 08:46
From version 33.1
edited by Erik Bakker
on 2025/10/09 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 -R16 Docker - Single Lane
1 +R9 Docker - Single lane
Content
... ... @@ -1,19 +1,22 @@
1 -**Non-service-affecting** final template to use the *R16* double 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 R16 release of our cloud template we upgrade in one step. This step is non-service-affecting.
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 -* Update versions of dependencies.
7 +It improves the stability of the AWS EFS mounts in running instances when a reconnect to EFS is triggered.
8 8  
9 -**Update Steps**
10 -* Use the final R*18* template (non-service affecting)(duration: < 5 minutes)
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.
11 11  
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.
12 12  * User actions after applying the final template:
13 -** Check if all runtimes are up via the runtime overview or Deploy Architecture
14 -** Check if all runtimes have been installed according to the active release
15 -** Check if messages pass through the bus 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.
16 16  
17 -**Remarks**
18 -
19 -Deadline of December 14th, 2025