Skip to Content

Changes for page R20 - Double lane

Last modified by Carlijn Kokkeler on 2024/01/18 11:42
From version 11.1
edited by Erik Bakker
on 2023/06/19 14:31
Change comment: There is no comment for this version
To version 7.1
edited by Erik Bakker
on 2023/05/09 14:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R18 - Double lane
1 +R17 - Double lane
Content
... ... @@ -1,25 +1,17 @@
1 -Service affecting R18 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture.
1 +Non service affecting final template to use the R17 double lane release.
2 +Process: To use the new R17 release of our cloud template we upgrade in one steps, the update is non service affecting.
2 2  
3 -**Process**
4 -We upgrade in two steps to use the new R18 release of the cloud template. Of these two steps, the intermediate step is nonservice affecting, and the final step is service affecting.
4 +Overview
5 +This update improves the security and enhances the auto-healing functionality on our 3rd generation runtimes.
5 5  
6 -**Overview**
7 -It improves the ease with which Static IP Addresses can be gathered and distributed by a user while at the same time improving the security and auto-healing functionality.
7 +Updates
8 8  
9 -**Updates**
10 -* Ability to fetch Static IP Addresses
11 -* New Ubuntu version with new security patches.
12 -* Improved Cloud instance status check and auto repair
9 +Improve Locking mitigation in the Artemis server (autohealing).
10 +Improve security by disabling SSH access to cloud machines.
11 +Update Steps
13 13  
14 -**Update Steps**
15 -* Use the intermediate template (non-service affecting) (duration: 4 minutes)
16 -** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot.
17 -** The network drive containing the Artemis queue store and your Elastic IPs will remain.
18 -* Use the final template (service affecting) (duration: 4 minutes)
19 -** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
20 -** The runtimes on the machines will be restored using the active release in the eMagiz portal.
21 -* User actions after applying the final template:
22 -** Check if all runtimes are reachable by Deploy Architecture.
23 -** Check if all flows have been installed according to the active release.
24 -** Check if messages pass through the model by verifying a critical message flow in external systems.
25 -
13 +Use the final R17 template (non service affecting) (duration: 4 minutes)
14 +User actions after applying the final template:
15 +Check if all runtimes are reachable by Deploy Architecture.
16 +Check if all images 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.