Changes for page R13 Docker - Double Lane
Last modified by Carlijn Kokkeler on 2023/11/21 11:51
From version 15.1
edited by Erik Bakker
on 2023/09/13 07:27
on 2023/09/13 07:27
Change comment:
There is no comment for this version
To version 8.1
edited by Erik Bakker
on 2023/03/03 11:30
on 2023/03/03 11:30
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -R 11Docker - Double lane1 +R6 Docker - Double lane - Content
-
... ... @@ -1,24 +1,17 @@ 1 -Service affecting R11 template that improves stability of AWS EFS mounts in running instances when a reconnect to EFS is triggered. 1 +Non service affecting final template to use the R6 double lane release. 2 +Process: To use the new R6 release of our cloud template we upgrade in one steps, the update is non service affecting. 2 2 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 - 6 6 **Overview** 7 - Itimproves thestabilityoftheAWS EFS mountsinrunninginstances whenareconnecttoEFSistriggered.5 +This update changes the Cloud port check, coordination faled and clean store functionality on our 3rd generation runtimes. 8 8 9 9 **Updates** 10 -* Updatedmountconfigurations of EFStoadheretoprovider'sstandards.11 -* Ubuntuversionupdateincludinglatestsecuritypatches.12 -* Th isupgradeisservice-affecting,asallinstanceshavetobereated.8 +* Cloud Port check: When the software does not expose the right ports, it will be restarted 9 +* Coordnation failed: When the runtimes failes to startup due to a corrupted startup order, the runtime will restart freshly to remove the corrupted state. 10 +* Clean store: The functionality to clean a store is added for generation 3 runtimes. See [[this link>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.eMagiz Cloud Management.expert-emagiz-cloud-management-clean-store||target="blank"]] 13 13 14 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 +* Use the final R6 template (non service affecting) (duration: 4 minutes) 20 20 * User actions after applying the final template: 21 -** Check if all runtimes are reachable by DeployArchitecture.15 +** Check if all runtimes are reachable by the runtime dashboard. 22 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 - 17 +** Check if messages pass through the bus by verifying a critical message flow in external systems.