Changes for page R15 - Double lane

Last modified by Erik Bakker on 2022/08/01 12:28

From version 7.1
edited by eMagiz
on 2022/07/08 12:36
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
... ... @@ -8,8 +8,8 @@
8 8  ** The network drive containing the Artemis queue store and your Elastic IPs will remain.
9 9  
10 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
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 13  
14 14  User actions after applying the final template:
15 15  
... ... @@ -17,6 +17,13 @@
17 17  * Check if all flows have been installed according to the active release
18 18  * Check if messages pass through the bus by verifying a critical message flow in external systems
19 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 +
20 20  ===R14 - Services affecting ===
21 21  Service affecting final template to use the R14 double lane release.
22 22  
... ... @@ -24,12 +24,9 @@
24 24  
25 25  Steps:
26 26  
27 -* Use the final R14 template (service affecting) (duration: 4 minutes)
34 +1. Use the final R14 template (service affecting) (duration: 4 minutes)
28 28  
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
36 +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
33 33  
34 34  Features R14 release:
35 35