Skip to Content

Changes for page R18 Docker - Single Lane

Last modified by Erik Bakker on 2026/02/10 10:59
From version 37.1
edited by Erik Bakker
on 2026/02/10 10:46
Change comment: There is no comment for this version
To version 31.1
edited by Erik Bakker
on 2025/06/30 09:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R18 Docker - Single Lane
1 +R15 Docker - Single Lane
Content
... ... @@ -1,18 +1,16 @@
1 -**Service affecting** final template to use the **R18** single lane release. This upgrade is service-affecting, as all instances have to be recreated.
1 +**Service affecting** template to use the R15 single lane release.
2 2  
3 3  **Process**
4 -We upgrade in one step to use the new **R18** release of the cloud template. This step is service affecting.
4 +To use the new R15 template on your environment, we replace all connections to activate the new configuration. This update is service affecting and aims to enable data traffic via our new carwash.
5 5  
6 6  **Overview**
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)
7 +* New connections to a **new** carwash.
12 12  
13 13  **Update Steps**
14 -* Use the final **R18** template (service affecting) (duration: 15 minutes)
10 +* Use the final template (service affecting)(duration: < 10 minutes)
11 +** This step will replace all connections.
12 +
15 15  * User actions after applying the final template:
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.
14 +** Check if all runtimes are up via the runtime overview
15 +** Check if all runtimes have been installed according to the active release
16 +** Check if messages pass through the model by verifying a critical message flow in external systems