Changes for page R19 Docker - Double Lane
                  Last modified by Erik Bakker on 2025/10/23 08:47
              
      
      From version  14.1 
    
    
              edited by Erik Bakker
        
on 2023/08/03 16:16
     on 2023/08/03 16:16
      Change comment:
              There is no comment for this version
          
         
      To version  26.1 
    
    
              edited by Erik Bakker
        
on 2025/06/30 09:51
     on 2025/06/30 09:51
      Change comment:
              There is no comment for this version
          
         Summary
- 
          Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
- 
      - Title
-   ... ... @@ -1,1 +1,1 @@ 1 -R1 0Docker - Doublelane1 +R17 Docker - Double Lane 
- Content
-   ... ... @@ -1,19 +1,17 @@ 1 - Non-service affectingR10template thatunlocks thepossibilityof running a failoverconfigurationon an MQTT Broker.1 +**Service affecting** final template to use the R16 double lane release. 2 2 3 3 **Process** 4 - WeupgradeinonestepsetheR10release ofthe cloud template. Thisstepisnon-service affecting.4 +o use the new R17 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 - Itadds thepossibilityof hostinganMQTT brokerinafailoveretting.7 +* New connections to a **new** carwash. 8 8 9 -**Updates** 10 -* Run an MQTT broker in a failover setting 11 - 12 12 **Update Steps** 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. 10 +* Use the final template (non 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 reachablebyDeploy Architecture.17 -** Check if all flows have been installed according to the active release.18 -** Check if messages pass through the modelby verifying a critical message flow in external systems.14 +** Check if all runtimes are up via the runtime overview or Deploy Architecture 15 +** Check if all runtimes have been installed according to the active release 16 +** Check if messages pass through the bus by verifying a critical message flow in external systems 19 19 
 
