Changes for page R17 Docker - Double Lane

Last modified by Erik Bakker on 2025/06/30 09:51

From version 26.1
edited by Erik Bakker
on 2025/06/30 09:51
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 -R17 Docker - Double Lane
1 +R14 Docker - Double Lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,17 +1,20 @@
1 -**Service affecting** final template to use the R16 double lane release.
1 +Non-service affecting final template to use the R14 double lane release.
2 2  
3 3  **Process**
4 -o use the new R17 template on your environment, we replace all connections to activate the new configuration. This update is service affecting and aims to enable data traffic via our new carwash.
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 -* New connections to a **new** carwash.
7 +This version contains the ability to clean H2 infra databases from the portal.
8 8  
9 -**Update Steps**
10 -* Use the final template (non service affecting)(duration: < 10 minutes)
11 -** This step will replace all connections.
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.
12 12  
14 +**Update Steps**
15 +* Use the final R14 template (non-service affecting) (duration: 3 minutes)
13 13  * User actions after applying the final template:
14 -** Check if all runtimes are up via the runtime overview or Deploy Architecture
15 -** Check if all runtimes have been installed according to the active release
16 -** Check if messages pass through the bus by verifying a critical message flow in external systems
17 +** Check if all ".01" 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.
17 17