Skip to Content

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 8.1
edited by Erik Bakker
on 2022/08/01 12:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R14 - Double lane
1 +R15 - Double lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.ebakker
Content
... ... @@ -1,16 +1,13 @@
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.
1 +Non service affecting final template to use the R15 double lane release.
3 3  
4 -Steps:
3 +Process:
5 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.
5 +* To use the new R15 release of our cloud template we upgrade in one steps, the update is non service affecting.
9 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
7 +Steps:
13 13  
9 +* Use the final R15 template (non service affecting) (duration: 4 minutes)
10 +
14 14  User actions after applying the final template:
15 15  
16 16  * Check if all runtimes are reachable by the runtime dashboard
... ... @@ -17,22 +17,6 @@
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 -===R14 - Services affecting ===
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 -
27 -* Use the final R14 template (service affecting) (duration: 4 minutes)
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
33 -
34 34  Features R14 release:
35 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
19 +1. Move to Python 3.9 version for auto healing functionality