Changes for page R15 - Double lane

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,29 +27,3 @@
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		-
8		-This step will upgrade the backup machines hosted in the second Availability Zone in your cloudslot
9		-The network drive containing the Artemis queue store and your Elastic IPs will remain.
10		-Use the final template (service affecting) (duration: 4 minutes)
11		-
12		-This step will upgrade the primary machines in the first Availability Zone in your cloudslot
13		-The runtimes on the machines will be restored using the active release in the eMagiz portal
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		-Features R14 release:
20		-
21		-Move to Python 3.9 version for cloudslot orchestration
22		-Better control the unattended updates of instance packages
23		-Use new point release of Ubuntu with latest security patches
24		-
25		-
26		-===R14 - Services affecting ===
27	27	Service affecting final template to use the R14 double lane release.
28	28
29	29	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.