Skip to Content

Changes for page R14 Docker - Double Lane

Last modified by Carlijn Kokkeler on 2024/03/29 13:47
From version 18.1
edited by Carlijn Kokkeler
on 2024/03/25 14:49
Change comment: There is no comment for this version
To version 16.1
edited by Carlijn Kokkeler
on 2023/11/21 11:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R14 Docker - Double Lane
1 +R13 Docker - Double Lane
Content
... ... @@ -1,19 +1,24 @@
1 -Non-service affecting final template to use the R14 double lane release.
1 +Service affecting template that introduces faster machine boot up and improved auto-healing.
2 2  
3 3  **Process**
4 -To use the new R14 release of our cloud template we upgrade in one step. The update is non-service affecting.
4 +We upgrade in two steps to use the new R13 release of the cloud template. Of these two steps, the intermediate step is non-service affecting, and the final step is service affecting.
5 5  
6 6  **Overview**
7 -This version contains the ability to clean H2 infra databases from the portal.
7 +This version contains performance improvements for auto-healing and machine boot up time.
8 8  
9 9  **Updates**
10 -* This upgrade contains the ability to clean H2 infra databases from the portal.
11 -* This upgrade is non-service affecting, as all instances have to be recreated.
10 +* Ubuntu version update including latest security patches.
11 +* This upgrade is service-affecting, as all instances have to be recreated.
12 12  
13 13  **Update Steps**
14 -* Use the final R14 template (non-service affecting) (duration: 3 minutes)
14 +* Use the intermediate template (non-service affecting) (duration: 10 minutes)
15 +** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot.
16 +** The network drive containing the Artemis queue store and your Elastic IPs will remain.
17 +* Use the final template (service affecting) (duration: 10 minutes)
18 +** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
19 +** The runtimes on the machines will be restored using the active release in the eMagiz portal.
15 15  * User actions after applying the final template:
16 -** Check if all ".01" runtimes are reachable by the runtime dashboard.
21 +** Check if all runtimes are reachable by Deploy Architecture.
17 17  ** Check if all flows have been installed according to the active release.
18 -** Check if messages pass through the bus by verifying a critical message flow in external systems.
23 +** Check if messages pass through the model by verifying a critical message flow in external systems.
19 19