Skip to Content

Changes for page R14 Docker - Single Lane

Last modified by Erik Bakker on 2025/04/07 10:12
From version 28.1
edited by Erik Bakker
on 2025/01/13 09:26
Change comment: There is no comment for this version
To version 20.1
edited by Carlijn Kokkeler
on 2024/03/25 11:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R13 Docker - Single Lane
1 +R12 Docker - Single Lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,20 +1,20 @@
1 -Service affecting template to use the R13 single lane release.
1 +Non-service affecting template to use the R12 single lane release.
2 2  
3 3  **Process**
4 -To use the new R13 template on your environment, we upgrade the control agent of **all** machines and disk encryption on **cloud** machines. This update is 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.
4 + To use the new R12 release of our cloud template we upgrade in one step. The update is non-service affecting.
5 5  
6 6  **Overview**
7 -* Security improvements to the eMagiz infrastructure.
8 -* Update control agent version.
7 +This version contains the ability to clean H2 infra databases from the portal.
9 9  
10 -**Update Steps**
11 -* Use the final template (service affecting)(duration: 10 minutes)
12 -** This step will upgrade the primary machines in the first Availability Zone in your cloudslot
13 -** This step will upgrade the control agent version on **all** machines (cloud and on-premise) to version 2.21.4
14 -*** The runtimes on the machines will be restored using the active release in the eMagiz portal
9 +**Updates**
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.
15 15  
14 +**Update Steps**
15 +* Use the final R12 template (non-service affecting) (duration: 3 minutes)
16 16  * User actions after applying the final template:
17 -** Check if all runtimes are up via the runtime overview
18 -** Check if all runtimes have been installed according to the active release
19 -** Check if messages pass through the bus by verifying a critical message flow in external systems
17 +** Check if all runtimes are reachable by the runtime dashboard.
18 +** Check if all flows have been installed according to the active release.
19 +** Check if messages pass through the bus by verifying a critical message flow in external systems.
20 20