Skip to Content

Changes for page R18 Docker - Single Lane

Last modified by Erik Bakker on 2026/02/10 10:59
From version 21.1
edited by CarlijnKokkeler
on 2024/03/25 14:49
Change comment: There is no comment for this version
To version 38.1
edited by Erik Bakker
on 2026/02/10 10:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R12 Docker - Single Lane
1 +R18 Docker - Single Lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,19 +1,21 @@
1 -Non-service affecting template to use the R12 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 R12 release of our cloud template we upgrade in one step. The update is non-service affecting.
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 -This version contains the ability to clean H2 infra databases from the portal.
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)
8 8  
9 -**Updates**
10 -* This upgrade contains the ability to clean H2 infra databases from the portal.
11 -* This upgrade is non-service affecting, as all instances have to be recreated.
12 -
13 13  **Update Steps**
14 -* Use the final R12 template (non-service affecting) (duration: 3 minutes)
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 reachable by the runtime dashboard.
16 +** Check if all runtimes are reachable by Deploy Architecture.
17 17  ** Check if all flows have been installed according to the active release.
18 -** Check if messages pass through the bus by verifying a critical message flow in external systems.
18 +** Check if messages pass through the model by verifying a critical message flow in external systems.
19 19  
20 +**Remarks**
21 +In case your model running fully on-premise you need to upgrade your agents by upgrading to the next available template (R3).