Skip to Content

Changes for page R14 Docker - Single Lane

Last modified by Erik Bakker on 2025/04/07 10:12
From version 19.1
edited by Carlijn Kokkeler
on 2023/11/21 11:47
Change comment: There is no comment for this version
To version 27.1
edited by Carlijn Kokkeler
on 2024/04/23 11:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R11 Docker - Single Lane
1 +R13 Docker - Single Lane
Content
... ... @@ -1,21 +1,19 @@
1 -Service affecting template that introduces faster machine boot up and improved auto-healing.
1 +Non-service affecting template to use the R13 single lane release.
2 2  
3 3  **Process**
4 -We upgrade in one step to use the new R11 release of the cloud template. This step is service affecting.
4 +To use the new R13 template on your environment, we upgrade the agent of external machines. This update is not service affecting.
5 5  
6 6  **Overview**
7 -This version contains performance improvements for auto-healing and machine boot up time.
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.
8 8  
9 9  **Updates**
10 -* Ubuntu version update including latest security patches.
11 -* This upgrade is service-affecting, as all instances have to be recreated.
11 +* This upgrade updates the machine agent to version 2.18.4.
12 +* This upgrade is non-service affecting.
12 12  
13 13  **Update Steps**
14 -* Use the final template (service affecting) (duration: 10 minutes)
15 -** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
16 -** The runtimes on the machines will be restored using the active release in the eMagiz portal.
15 +* Use the final R13 template (non-service affecting) (duration: approx. 1 minute per machine).
17 17  * User actions after applying the final template:
18 -** Check if all runtimes are reachable by Deploy Architecture.
19 -** Check if all flows have been installed according to the active release.
20 -** Check if messages pass through the model by verifying a critical message flow in external systems.
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.
21 21