Wiki source code of R19 Docker - Single Lane
Last modified by Erik Bakker on 2026/03/22 21:42
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
40.1 | 1 | **Service affecting** final template to use the **R19** single lane release. This upgrade is service-affecting, as all instances have to be recreated. |
| |
1.1 | 2 | |
| |
14.1 | 3 | **Process** |
| |
40.1 | 4 | We upgrade in one step to use the new **R19** release of the cloud template. This step is service affecting. |
| |
14.1 | 5 | |
| |
4.1 | 6 | **Overview** |
| |
40.1 | 7 | * Remove need for recycling underlying instance when adding containers to machine |
| |
1.1 | 8 | |
| |
28.1 | 9 | **Update Steps** |
| |
40.1 | 10 | * Use the final **R19** template (service affecting) (duration: 15 minutes) |
| |
37.1 | 11 | * User actions after applying the final template: |
| 12 | ** Check if all runtimes are reachable by Deploy Architecture. | ||
| 13 | ** Check if all flows have been installed according to the active release. | ||
| 14 | ** Check if messages pass through the model by verifying a critical message flow in external systems. | ||
| |
38.1 | 15 | |
| 16 | **Remarks** | ||
| |
40.1 | 17 | Adding/moving/deleting containers from machines will now not replace the underlying instances. This was only the case for singlelanes. Doublelanes do not have this behaviour and are not affected. |