Changes for page R20 - Double lane
Last modified by Carlijn Kokkeler on 2024/01/18 11:42
From version 8.1
edited by Erik Bakker
on 2023/05/09 14:00
on 2023/05/09 14:00
Change comment:
There is no comment for this version
To version 6.1
edited by Erik Bakker
on 2023/04/28 08:41
on 2023/04/28 08:41
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,16 +1,15 @@ 1 -Non service affecting final template to use the R17 double lane release.1 +Non service affecting final template to use the R17 Double lane release. 2 2 Process: To use the new R17 release of our cloud template we upgrade in one steps, the update is non service affecting. 3 3 4 4 **Overview** 5 -This update improves the securityand enhances the auto-healing functionality onour3rdgeneration runtimes.5 +This update improves the auto-healing functionality of our current generation runtime architecture. In this cloud template an earlier bug surrounding the "lock reclaim" auto-healing has been fixed. 6 6 7 7 **Updates** 8 -* Improve Locking mitigation in the Artemis server (autohealing). 9 -* Improve security by disabling SSH access to cloud machines. 8 + * Improve Locking mitigation in the Artemis server (autohealing) 10 10 11 11 **Update Steps** 12 12 * Use the final R17 template (non service affecting) (duration: 4 minutes) 13 13 * User actions after applying the final template: 14 -** Check if all runtimes are reachable by DeployArchitecture.15 -** Check if all images have been installed according to the active release.13 +** Check if all runtimes are reachable by the runtime dashboard. 14 +** Check if all flows have been installed according to the active release. 16 16 ** Check if messages pass through the bus by verifying a critical message flow in external systems.