Skip to Content

Changes for page R12 Docker - Single Lane

Last modified by Carlijn Kokkeler on 2024/03/29 13:47
From version 12.2
edited by Erik Bakker
on 2023/03/03 11:29
Change comment: Update document after refactoring.
To version 18.1
edited by Erik Bakker
on 2023/09/13 07:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R6 - Docker Single lane
1 +R9 Docker - Single lane
Content
... ... @@ -1,17 +1,22 @@
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.
1 +Service affecting R9 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 one step to use the new R9 release of the cloud template. This step is service affecting.
5 +
4 4  **Overview**
5 -This update changes the Cloud port check, coordination faled and clean store 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 -* 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"]]
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.
11 11  
12 12  **Update Steps**
13 -* Use the final R6 template (non service affecting) (duration: 4 minutes)
15 +* Use the final template (service affecting) (duration: 10 minutes)
16 +** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
17 +** The runtimes on the machines will be restored using the active release in the eMagiz portal.
14 14  * User actions after applying the final template:
15 -** Check if all runtimes are reachable by the runtime dashboard.
19 +** Check if all runtimes are reachable by Deploy Architecture.
16 16  ** Check if all flows have been installed according to the active release.
17 -** Check if messages pass through the bus by verifying a critical message flow in external systems.
21 +** Check if messages pass through the model by verifying a critical message flow in external systems.
22 +