Skip to Content

Changes for page R14 Docker - Single Lane

Last modified by Erik Bakker on 2025/04/07 10:12
From version 30.1
edited by Erik Bakker
on 2025/04/07 10:12
Change comment: There is no comment for this version
To version 22.1
edited by Carlijn Kokkeler
on 2024/03/27 10:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R14 Docker - Single Lane
1 +R12 Docker - Single Lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,19 +1,19 @@
1 -**Service affecting** template to use the R14 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 R14 template on your environment, we replace all your machines with new ones to activate the new configuration. This update is service affecting and aims to increase the stability of models running in Production.
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 -* Stability improvements to your **Production** model.
8 -* More control on resource management
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 machines in your cloud slot
13 -*** The network drive containing the Artemis queue store and your Elastic IPs will remain.
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.
14 14  
13 +**Update Steps**
14 +* Use the final R12 template (non-service affecting) (duration: 3 minutes)
15 15  * User actions after applying the final template:
16 -** Check if all runtimes are up via the runtime overview
17 -** Check if all runtimes have been installed according to the active release
18 -** Check if messages pass through the model by verifying a critical message flow in external systems
16 +** Check if all runtimes are reachable by the 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.
19 19