Skip to Content

Changes for page R14 Docker - Double Lane

Last modified by Carlijn Kokkeler on 2024/03/29 13:47
From version 13.1
edited by Erik Bakker
on 2023/07/10 15:13
Change comment: There is no comment for this version
To version 17.1
edited by Carlijn Kokkeler
on 2024/03/25 11:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R9 Docker - Double lane
1 +R14 Docker - Double Lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,28 +1,20 @@
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 R14 double lane release.
2 2  
3 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.
4 +To use the new R14 release of our cloud template we upgrade in one step. The update is non-service affecting.
5 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.
7 +This version contains the ability to clean H2 infra databases from the portal.
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
15 -* Added new version of the deployment agent, solving a known portainer bug where all containers are replaced instead of one.
10 +* Ubuntu version update including latest security patches.
11 +* This upgrade is non-service affecting, as all instances have to be recreated.
12 +* This upgrade contains the ability to clean H2 infra databases from the portal.
16 16  
17 17  **Update Steps**
18 -* Use the intermediate template (non-service affecting) (duration: 10 minutes)
19 -** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot.
20 -** The network drive containing the Artemis queue store and your Elastic IPs will remain.
21 -* Use the final template (service affecting) (duration: 10 minutes)
22 -** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
23 -** The runtimes on the machines will be restored using the active release in the eMagiz portal.
15 +* Use the final R14 template (non-service affecting) (duration: 3 minutes)
24 24  * User actions after applying the final template:
25 -** Check if all runtimes are reachable by Deploy Architecture.
17 +** Check if all ".01" runtimes are reachable by the runtime dashboard.
26 26  ** Check if all flows have been installed according to the active release.
27 -** Check if messages pass through the model by verifying a critical message flow in external systems.
19 +** Check if messages pass through the bus by verifying a critical message flow in external systems.
28 28