Skip to Content

Changes for page R20 Docker - Single Lane

Last modified by Erik Bakker on 2026/06/29 09:44
From version 43.1
edited by Erik Bakker
on 2026/06/29 09:44
Change comment: There is no comment for this version
To version 30.1
edited by Erik Bakker
on 2025/04/07 10:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R20 Docker - Single Lane
1 +R14 Docker - Single Lane
Content
... ... @@ -1,20 +1,19 @@
1 -{{info}}This environment template needs to be applied on all environments of all (your) models before August 29th, 2026{{/info}}
1 +**Service affecting** template to use the R14 single lane release.
2 2  
3 -**Non-Service affecting** final template to use the **R20** single lane release. This upgrade is non-service-affecting.
4 -
5 5  **Process**
6 -We upgrade in one step to use the new **R20** release of the cloud template. This step is non-service affecting.
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.
7 7  
8 8  **Overview**
9 -* Improve internal monitoring and alerting capabilities
10 -* Improve management of users and permissions
7 +* Stability improvements to your **Production** model.
8 +* More control on resource management
11 11  
12 12  **Update Steps**
13 -* Use the final **R20** template (non-service affecting) (duration: 10 minutes)
14 -** None of the runtimes will be touched.
15 -** Authorization servers will perform a rolling update.
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.
14 +
16 16  * User actions after applying the final template:
17 -** Check if all runtimes are reachable by Deploy Architecture.
18 -** Check if all flows have been installed according to the active release.
19 -** Check if messages pass through the model by verifying a critical message flow in external systems.
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
20 20