Skip to Content

Changes for page R13 Docker - Double Lane

Last modified by Carlijn Kokkeler on 2023/11/21 11:51
From version 16.1
edited by Carlijn Kokkeler
on 2023/11/21 11: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 -R13 Docker - Double Lane
1 +R11 Docker - Double lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,12 +1,13 @@
1 -Service affecting template that introduces faster machine boot up and improved auto-healing.
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 -We upgrade in two steps to use the new R13 release of the cloud template. Of these two steps, the intermediate step is non-service affecting, and the final step is 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 -This version contains performance improvements for auto-healing and machine boot up time.
7 +It improves the stability of the AWS EFS mounts in running instances when a reconnect to EFS is triggered.
8 8  
9 9  **Updates**
10 +* Updated mount configurations of EFS to adhere to provider's standards.
10 10  * Ubuntu version update including latest security patches.
11 11  * This upgrade is service-affecting, as all instances have to be recreated.
12 12  
... ... @@ -14,9 +14,8 @@
14 14  * Use the intermediate template (non-service affecting) (duration: 10 minutes)
15 15  ** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot.
16 16  ** The network drive containing the Artemis queue store and your Elastic IPs will remain.
17 -* Use the final template (service affecting) (duration: 10 minutes)
18 -** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
19 -** The runtimes on the machines will be restored using the active release in the eMagiz portal.
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.
20 20  * User actions after applying the final template:
21 21  ** Check if all runtimes are reachable by Deploy Architecture.
22 22  ** Check if all flows have been installed according to the active release.