Changes for page R15 Docker - Double Lane
Last modified by Erik Bakker on 2025/01/20 07:40
From version 20.1
edited by Carlijn Kokkeler
on 2024/03/29 13:47
on 2024/03/29 13:47
Change comment:
There is no comment for this version
To version 22.1
edited by Erik Bakker
on 2025/01/13 09:24
on 2025/01/13 09:24
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -R1 4Docker - Double Lane1 +R15 Docker - Double Lane - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,19 +1,23 @@ 1 - Non-service affecting final template to use the R14double lane release.1 +Service affecting final template to use the R15 double lane release. 2 2 3 3 **Process** 4 -To use the new R1 4release of our cloud template we upgrade in one step. The update isnon-service affecting.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. 5 5 6 6 **Overview** 7 -This version contains the ability to clean H2 infra databases from the portal. 7 +* Security improvements to the eMagiz infrastructure. 8 +* Update control agent version. 8 8 9 -**Updates** 10 -* This upgrade contains the ability to clean H2 infra databases from the portal. 11 -* This upgrade is non-service affecting. 12 - 13 13 **Update Steps** 14 -* Use the final R14 template (non-service affecting) (duration: 3 minutes) 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 18 + 15 15 * User actions after applying the final template: 16 -** Check if all ".01"runtimes arereachablebythe runtime overview.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 .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 19 19