Changes for page R14 Docker - Single Lane

Last modified by Erik Bakker on 2025/04/07 10:12

From version 27.1
edited by Carlijn Kokkeler
on 2024/04/23 11:18
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 -R13 Docker - Single Lane
1 +R14 Docker - Single Lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,19 +1,19 @@
1 -Non-service affecting template to use the R13 single lane release.
1 +**Service affecting** template to use the R14 single lane release.
2 2  
3 3  **Process**
4 -To use the new R13 template on your environment, we upgrade the agent of external machines. This update is not 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.
5 5  
6 6  **Overview**
7 -* Non service-affecting template that updates the on-premise machine agents.
8 -* The cloud-environment for this template does not contain any changes compared to the R12 template.
7 +* Stability improvements to your **Production** model.
8 +* More control on resource management
9 9  
10 -**Updates**
11 -* This upgrade updates the machine agent to version 2.18.4.
12 -* This upgrade is non-service affecting.
13 -
14 14  **Update Steps**
15 -* Use the final R13 template (non-service affecting) (duration: approx. 1 minute per machine).
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 on-premise runtimes are reachable by the runtime overview.
18 -** Check if messages pass through the bus 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
19 19