Skip to Content

Changes for page R15 Docker - Single Lane

Last modified by Erik Bakker on 2025/06/30 09:51
From version 18.1
edited by Erik Bakker
on 2023/09/13 07:23
Change comment: There is no comment for this version
To version 32.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 -R9 Docker - Single lane
1 +R15 Docker - Single Lane
Content
... ... @@ -1,22 +1,16 @@
1 -Service affecting R9 template that improves stability of AWS EFS mounts in running instances when a reconnect to EFS is triggered.
1 +**Service affecting** template to use the R15 single lane release.
2 2  
3 3  **Process**
4 -We upgrade in one step to use the new R9 release of the cloud template. This step is service affecting.
4 +To use the new R15 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 -It improves the stability of the AWS EFS mounts in running instances when a reconnect to EFS is triggered.
7 +* New connections to a **new** carwash.
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 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.
18 -* User actions after applying the final template:
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.
10 +* Use the final template (service affecting)(duration: < 10 minutes)
11 +** This step will replace all connections.
22 22  
13 +* User actions after applying the final template:
14 +** Check if all runtimes are up via the runtime overview or Deploy Architecture
15 +** Check if all runtimes have been installed according to the active release
16 +** Check if messages pass through the model by verifying a critical message flow in external systems