Wiki source code of R14 - Double lane
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 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 | |||
| 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. | ||
| 9 | ** Use the final template (service affecting) (duration: 4 minutes) | ||
| 10 | |||
| 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 | ||
| 13 | User actions after applying the final template: | ||
| 14 | |||
| 15 | Check if all runtimes are reachable by the runtime dashboard | ||
| 16 | Check if all flows have been installed according to the active release | ||
| 17 | Check if messages pass through the bus by verifying a critical message flow in external systems | ||
| 18 | Features R14 release: | ||
| 19 | |||
| 20 | Move to Python 3.9 version for cloudslot orchestration | ||
| 21 | Better control the unattended updates of instance packages | ||
| 22 | Use new point release of Ubuntu with latest security patches | ||
| 23 | |||
| 24 | |||
| 25 | ===R14 - Services affecting === | ||
| 26 | Service affecting final template to use the R14 double lane release. | ||
| 27 | |||
| 28 | 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. | ||
| 29 | |||
| 30 | Steps: | ||
| 31 | |||
| 32 | 1. Use the final R14 template (service affecting) (duration: 4 minutes) | ||
| 33 | |||
| 34 | User actions after applying the final template: - Check if all ".01" runtimes are reachable by the runtime dashboard - Check if all flows have been installed according to the active release - Check if messages pass through the bus by verifying a critical message flow in external systems | ||
| 35 | |||
| 36 | Features R14 release: | ||
| 37 | |||
| 38 | 1. Move to Python 3.9 version for cloudslot orchestration | ||
| 39 | 1. Better control the unattended updates of instance packages | ||
| 40 | 1. Use new point release of Ubuntu with latest security patches |