Skip to Content

Changes for page R15 Docker - Double Lane

Last modified by Erik Bakker on 2025/01/20 07:40
From version 21.1
edited by Carlijn Kokkeler
on 2024/04/23 11:18
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 -R15 Docker - Double Lane
1 +R11 Docker - Double lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,19 +1,24 @@
1 -Non-service affecting final template to use the R15 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 -To use the new R15 template on your environment, we upgrade the agent of external machines. This update is not service affecting.
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 -* Non service-affecting template that updates the on-premise machine agents.
8 -* The cloud-environment for this template does not contain any changes compared to the R14 template.
7 +It improves the stability of the AWS EFS mounts in running instances when a reconnect to EFS is triggered.
9 9  
10 10  **Updates**
11 -* This upgrade updates the machine agent to version 2.18.4.
12 -* This upgrade is non-service affecting.
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 13  
14 14  **Update Steps**
15 -* Use the final R15 template (non-service affecting) (duration: approx. 1 minute per machine).
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.
16 16  * User actions after applying the final template:
17 -** Check if all on-premise runtimes are reachable by the runtime overview.
18 -** 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.
19 19