Skip to Content

Changes for page R13 Docker - Double Lane

Last modified by Carlijn Kokkeler on 2023/11/21 11:51
From version 9.1
edited by Erik Bakker
on 2023/04/28 08:36
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 -R8 Docker - Double lane
1 +R11 Docker - Double lane
Content
... ... @@ -1,16 +1,24 @@
1 -Non service affecting final template to use the R8 double lane release.
2 -Process: To use the new R8 release of our cloud template we upgrade in one steps, the update is non service affecting.
1 +Service affecting R11 template that improves stability of AWS EFS mounts in running instances when a reconnect to EFS is triggered.
3 3  
3 +**Process**
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 +
4 4  **Overview**
5 -This update improves the security and enhances the auto-healing functionality on our 3rd generation runtimes.
7 +It improves the stability of the AWS EFS mounts in running instances when a reconnect to EFS is triggered.
6 6  
7 7  **Updates**
8 -* Improve Locking mitigation in the Artemis server (autohealing).
9 -* Improve security by disabling SSH access to cloud machines.
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.
10 10  
11 11  **Update Steps**
12 -* Use the final R8 template (non service affecting) (duration: 4 minutes)
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 14  ** Check if all runtimes are reachable by Deploy Architecture.
15 -** Check if all images 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.
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.
24 +