Wiki source code of R14 - Double lane
Last modified by eMagiz on 2022/07/08 12:36
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
2.1 | 1 | ===R14 - Non-services affecting === |
| 2 | Non service affecting intermediate template to use the R14 double lane release. This is the first of two steps for your upgrade to the new R14 template. | ||
| 3 | |||
| 4 | Steps: | ||
| 5 | |||
| |
3.1 | 6 | * Use this intermediate template (non service affecting) (duration: 4 minutes) |
| 7 | ** This step will upgrade the backup machines hosted in the second Availability Zone in your cloudslot | ||
| 8 | ** The network drive containing the Artemis queue store and your Elastic IPs will remain. | ||
| |
2.1 | 9 | |
| |
5.1 | 10 | * Use the final template (service affecting) (duration: 4 minutes) |
| |
6.1 | 11 | ** This step will upgrade the primary machines in the first Availability Zone in your cloudslot |
| 12 | ** The runtimes on the machines will be restored using the active release in the eMagiz portal | ||
| |
5.1 | 13 | |
| |
2.1 | 14 | User actions after applying the final template: |
| 15 | |||
| |
5.1 | 16 | * Check if all runtimes are reachable by the runtime dashboard |
| 17 | * Check if all flows have been installed according to the active release | ||
| 18 | * Check if messages pass through the bus by verifying a critical message flow in external systems | ||
| 19 | |||
| |
2.1 | 20 | ===R14 - Services affecting === |
| |
1.1 | 21 | Service affecting final template to use the R14 double lane release. |
| 22 | |||
| 23 | Process: To use the new R14 release of our cloud template we upgrade in two steps, with only the second step being service affecting. Below is the remaining step. | ||
| 24 | |||
| 25 | Steps: | ||
| 26 | |||
| |
7.1 | 27 | * Use the final R14 template (service affecting) (duration: 4 minutes) |
| |
1.1 | 28 | |
| |
7.1 | 29 | User actions after applying the final template: |
| 30 | * Check if all ".01" runtimes are reachable by the runtime dashboard | ||
| 31 | * Check if all flows have been installed according to the active release | ||
| 32 | * Check if messages pass through the bus by verifying a critical message flow in external systems | ||
| |
1.1 | 33 | |
| 34 | Features R14 release: | ||
| 35 | |||
| 36 | 1. Move to Python 3.9 version for cloudslot orchestration | ||
| 37 | 1. Better control the unattended updates of instance packages | ||
| 38 | 1. Use new point release of Ubuntu with latest security patches |