Skip to Content

Changes for page R10 Docker - Double lane

Last modified by Erik Bakker on 2023/08/03 16:16
From version 12.1
edited by Erik Bakker
on 2023/06/19 14:30
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 -R9 Docker - Double lane
1 +R6 Docker - Double lane
Content
... ... @@ -1,27 +1,17 @@
1 -Service affecting R9 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture.
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 R9 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 -It improves the ease with which Static IP Addresses can be gathered and distributed by a user while at the same time improving the security and auto-healing functionality.
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 -* Ability to fetch Static IP Addresses
11 -* New ubuntu version with new security patches.
12 -* Disable IPv6 on startup
13 -* Enable new Out of Memory killer to protect instance becoming unhealthy
14 -* Improved Cloud instance status check and auto repair
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"]]
15 15  
16 16  **Update Steps**
17 -* Use the intermediate template (non-service affecting) (duration: 10 minutes)
18 -** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot.
19 -** The network drive containing the Artemis queue store and your Elastic IPs will remain.
20 -* Use the final template (service affecting) (duration: 10 minutes)
21 -** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
22 -** The runtimes on the machines will be restored using the active release in the eMagiz portal.
13 +* Use the final R6 template (non service affecting) (duration: 4 minutes)
23 23  * User actions after applying the final template:
24 -** Check if all runtimes are reachable by Deploy Architecture.
15 +** Check if all runtimes are reachable by the runtime dashboard.
25 25  ** Check if all flows have been installed according to the active release.
26 -** Check if messages pass through the model by verifying a critical message flow in external systems.
27 -
17 +** Check if messages pass through the bus by verifying a critical message flow in external systems.