Changes for page R17 Docker - Single Lane
                  Last modified by Erik Bakker on 2025/10/23 08:46
              
      
      From version  19.1 
    
    
              edited by Carlijn Kokkeler
        
on 2023/11/21 11:47
     on 2023/11/21 11:47
      Change comment:
              There is no comment for this version
          
         
      To version  34.1 
    
    
              edited by Erik Bakker
        
on 2025/10/09 10:13
     on 2025/10/09 10:13
      Change comment:
              There is no comment for this version
          
         Summary
- 
          Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
- 
      - Title
-   ... ... @@ -1,1 +1,1 @@ 1 -R1 1Docker - Single Lane1 +R16 Docker - Single Lane 
- Author
-   ... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker 
- Content
-   ... ... @@ -1,21 +1,19 @@ 1 - Servicehat introducesfastermachinebootupandimproved auto-healing.1 +**Non-service-affecting** final template to use the **R16** double lane release. 2 2 3 3 **Process** 4 - We upgrade inonestep touse the new R11release ofthecloud template. This step is service4 +To use the new R16 release of our cloud template we upgrade in one step. This step is non-service-affecting. 5 5 6 6 **Overview** 7 - Thisversioncontainsperformanceimprovements for auto-healing and machineboot up time.7 +* Update versions of dependencies. 8 8 9 -**Updates** 10 -* Ubuntu version update including latest security patches. 11 -* This upgrade is service-affecting, as all instances have to be recreated. 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. 10 +* Use the final R16 template (non-service affecting)(duration: < 5 minutes) 11 + 17 17 * User actions after applying the final template: 18 -** Check if all runtimes are reachablebyDeploy Architecture.19 -** Check if all flows have been installed according to the active release.20 -** Check if messages pass through the modelby verifying a critical message flow in external systems.13 +** Check if all runtimes are up via the runtime overview or Deploy Architecture 14 +** Check if all runtimes have been installed according to the active release 15 +** Check if messages pass through the bus by verifying a critical message flow in external systems 21 21 17 +**Remarks** 18 + 19 +Deadline of December 14th, 2025 
 
