Skip to Content

Changes for page R14 - Double lane

Last modified by eMagiz on 2022/07/08 12:36
From version 1.1
edited by eMagiz
on 2022/07/08 12:32
Change comment: There is no comment for this version
To version 5.1
edited by eMagiz
on 2022/07/08 12:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,3 +1,30 @@
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 +
10 +* Use the final template (service affecting) (duration: 4 minutes)
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 +
14 +User actions after applying the final template:
15 +
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 +
20 +Features R14 release:
21 +
22 +* Move to Python 3.9 version for cloudslot orchestration
23 +* Better control the unattended updates of instance packages
24 +* Use new point release of Ubuntu with latest security patches
25 +
26 +
27 +===R14 - Services affecting ===
1 1  Service affecting final template to use the R14 double lane release.
2 2  
3 3  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.