Skip to Content

Changes for page R15 Docker - Double Lane

Last modified by Erik Bakker on 2025/01/20 07:40
From version 21.1
edited by Carlijn Kokkeler
on 2024/04/23 11:18
Change comment: There is no comment for this version
To version 14.1
edited by Erik Bakker
on 2023/08/03 16:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R15 Docker - Double Lane
1 +R10 Docker - Double lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,19 +1,19 @@
1 -Non-service affecting final template to use the R15 double lane release.
1 +Non-service affecting R10 template that unlocks the possibility of running a failover configuration on an MQTT Broker.
2 2  
3 3  **Process**
4 -To use the new R15 template on your environment, we upgrade the agent of external machines. This update is not service affecting.
4 +We upgrade in one step to use the new R10 release of the cloud template. This step is non-service affecting.
5 5  
6 6  **Overview**
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 R14 template.
7 +It adds the possibility of hosting an MQTT broker in a failover setting.
9 9  
10 10  **Updates**
11 -* This upgrade updates the machine agent to version 2.18.4.
12 -* This upgrade is non-service affecting.
10 +* Run an MQTT broker in a failover setting
13 13  
14 14  **Update Steps**
15 -* Use the final R15 template (non-service affecting) (duration: approx. 1 minute per machine).
13 +* Use the final template (non-service affecting) (duration: 10 minutes)
14 +** This step will update your cloud slot configuration to allow an MQTT broker with failover settings.
16 16  * User actions after applying the final template:
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.
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.
19 19