Wiki source code of R20 Docker - Double Lane
Version 31.1 by Erik Bakker on 2026/02/10 10:43
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
| |
31.1 | 1 | === Intermediate Template - Release Notes === |
| |
1.1 | 2 | |
| |
31.1 | 3 | **Non-service affecting** intermediate template to use the R20 double lane release. This is the first of two steps for your upgrade to the new R20 template. |
| 4 | |||
| |
10.1 | 5 | **Process** |
| |
31.1 | 6 | To use the new R20 release of our cloud template we upgrade in two steps, with only the second step being service affecting. Below is the first step. |
| |
10.1 | 7 | |
| |
1.1 | 8 | **Overview** |
| |
31.1 | 9 | * Security improvements to the eMagiz infrastructure |
| 10 | * Update Ubuntu version | ||
| 11 | * Update Docker version | ||
| 12 | * Update control agent version | ||
| 13 | * Update Authorization Server (if applicable) | ||
| |
1.1 | 14 | |
| |
22.1 | 15 | **Update Steps** |
| |
31.1 | 16 | * Use this intermediate R20 template (non-service affecting)(duration: < 15 minutes) |
| 17 | ** This step will upgrade the backup machines hosted in the second Availability Zone in your cloudslot. | ||
| 18 | ** The network drive containing the Artemis queue store and your Elastic IPs will remain. | ||
| 19 | ** The runtimes on the machines will be restored using the active release in the eMagiz portal | ||
| |
1.1 | 20 | |
| |
31.1 | 21 | User actions after applying the intermediate template: |
| 22 | Check if all ".02" runtimes are reachable by the runtime dashboard | ||
| 23 | Check if all flows have been installed according to the active release | ||
| 24 | Check if messages pass through the bus by verifying a critical message flow in external systems | ||
| 25 | |||
| |
28.1 | 26 | **Remarks** |
| 27 | |||
| |
31.1 | 28 | To allow the user to have more control of the upgrade process we now allow to upgrade to the intermediate template as a seperate step. This gives you the option to wait longer before updating the **service affecting** final template. In this time you can do additional verifications on your model. |
| 29 | |||
| 30 | === Final Template - Release Notes === | ||
| 31 | |||
| 32 | **Service affecting** final template to use the R20 double lane release. | ||
| 33 | |||
| 34 | **Process** | ||
| 35 | To use the new R20 release of our cloud template we upgrade in two steps, with only the second step being service affecting. Below is the remaining step. | ||
| 36 | |||
| 37 | **Overview** | ||
| 38 | * Security improvements to the eMagiz infrastructure | ||
| 39 | * Update Ubuntu version | ||
| 40 | * Update Docker version | ||
| 41 | * Update control agent version | ||
| 42 | * Update Authorization Server (if applicable) | ||
| 43 | |||
| 44 | **Update Steps** | ||
| 45 | * Use the final R20 template (non-service affecting)(duration: < 15 minutes) | ||
| 46 | ** This step will upgrade the primary machines in the first Availability Zone in your cloudslot. | ||
| 47 | ** The runtimes on the machines will be restored using the active release in the eMagiz portal. | ||
| 48 | |||
| 49 | User actions after applying the final template: | ||
| 50 | Check if all ".01" runtimes are reachable by the runtime dashboard | ||
| 51 | Check if all flows have been installed according to the active release | ||
| 52 | Check if messages pass through the bus by verifying a critical message flow in external systems |