Skip to Content

Changes for page R18 Docker - Single Lane

Last modified by Erik Bakker on 2026/02/10 10:59
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 37.1
edited by Erik Bakker
on 2026/02/10 10:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R14 Docker - Single Lane
1 +R18 Docker - Single Lane
Content
... ... @@ -1,19 +1,18 @@
1 -**Service affecting** template to use the R14 single lane release.
1 +**Service affecting** final template to use the **R18** single lane release. This upgrade is service-affecting, as all instances have to be recreated.
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 +We upgrade in one step to use the new **R18** release of the cloud template. This step is service affecting.
5 5  
6 6  **Overview**
7 -* Stability improvements to your **Production** model.
8 -* More control on resource management
7 +* Security improvements to the eMagiz infrastructure
8 +* Update Ubuntu version
9 +* Update Docker version
10 +* Update control agent version
11 +* Update Authorization Server (if applicable)
9 9  
10 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.
14 -
14 +* Use the final **R18** template (service affecting) (duration: 15 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
19 -
16 +** Check if all runtimes are reachable by Deploy Architecture.
17 +** Check if all flows 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.