Skip to Content

Changes for page R17 Docker - Double Lane

Last modified by Erik Bakker on 2025/06/30 09:51
From version 26.1
edited by Erik Bakker
on 2025/06/30 09:51
Change comment: There is no comment for this version
To version 15.1
edited by Erik Bakker
on 2023/09/13 07:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R17 Docker - Double Lane
1 +R11 Docker - Double lane
Content
... ... @@ -1,17 +1,24 @@
1 -**Service affecting** final template to use the R16 double lane release.
1 +Service affecting R11 template that improves stability of AWS EFS mounts in running instances when a reconnect to EFS is triggered.
2 2  
3 3  **Process**
4 -o use the new R17 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.
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.
5 5  
6 6  **Overview**
7 -* New connections to a **new** carwash.
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 template (non service affecting)(duration: < 10 minutes)
11 -** This step will replace all connections.
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.
12 12  
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.
13 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 bus by verifying a critical message flow in external systems
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.
17 17