Skip to Content

Changes for page R14 Docker - Single Lane

Last modified by Erik Bakker on 2025/04/07 10:12
From version 13.1
edited by Erik Bakker
on 2023/04/28 08:34
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 -R7 - Docker Single lane
1 +R14 Docker - Single Lane
Content
... ... @@ -1,15 +1,19 @@
1 -Non service affecting final template to use the R7 single lane release.
2 -Process: To use the new R7 release of our cloud template we upgrade in one steps, the update is non service affecting.
1 +**Service affecting** template to use the R14 single lane release.
3 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.
5 +
4 4  **Overview**
5 -This update improves the security by disabling SSH access to cloud machines.
7 +* Stability improvements to your **Production** model.
8 +* More control on resource management
6 6  
7 -**Updates**
8 -* Improve security by disabling SSH access to cloud machines.
9 -
10 10  **Update Steps**
11 -* Use the final R7 template (non service affecting) (duration: 4 minutes)
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 +
12 12  * User actions after applying the final template:
13 -** Check if all runtimes are reachable by Deploy Architecture.
14 -** Check if all images have been installed according to the active release.
15 -** 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 +