Skip to Content

Changes for page R16 Docker - Double Lane

Last modified by Erik Bakker on 2025/04/07 10:15
From version 23.1
edited by Erik Bakker
on 2025/01/13 09:26
Change comment: There is no comment for this version
To version 8.1
edited by Erik Bakker
on 2023/03/03 11:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R15 Docker - Double Lane
1 +R6 Docker - Double lane
Content
... ... @@ -1,23 +1,17 @@
1 -Service affecting final template to use the R15 double lane release.
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 -To use the new R15 release of our cloud template we upgrade in two steps, with only the second step being service affecting. The goal of this update is to increase the security of the disks related to your machine by encrypting them and to update the control agent version to 2.21.4 for **all** machines.
5 -
6 6  **Overview**
7 -* Security improvements to the eMagiz infrastructure.
8 -* Update control agent version.
5 +This update changes the Cloud port check, coordination faled and clean store functionality on our 3rd generation runtimes.
9 9  
10 -**Update Steps**
11 -* Use this intermediate template (non service affecting)(duration: 10 minutes)
12 -** This step will upgrade the backup machines hosted in the second Availability Zone in your cloudslot
13 -*** The network drive containing the Artemis queue store and your Elastic IPs will remain.
14 -* Use the final template (service affecting)(duration: 10 minutes)
15 -** This step will upgrade the primary machines in the first Availability Zone in your cloudslot
16 -** This step will upgrade the control agent version on **all** machines (cloud and on-premise) to version 2.21.4
17 -*** The runtimes on the machines will be restored using the active release in the eMagiz portal
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"]]
18 18  
12 +**Update Steps**
13 +* Use the final R6 template (non service affecting) (duration: 4 minutes)
19 19  * User actions after applying the final template:
20 -** Check if all runtimes are up via the runtime overview
21 -** Check if all runtimes have been installed according to the active release
22 -** Check if messages pass through the bus by verifying a critical message flow in external systems
23 -
15 +** Check if all runtimes are reachable by the runtime dashboard.
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.