Changes for page R22 - Double lane
Last modified by Erik Bakker on 2025/10/09 10:14
From version 7.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 20.1
edited by Erik Bakker
on 2025/10/09 10:14
on 2025/10/09 10:14
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -R 17- Double lane1 +R22 - Double lane - Content
-
... ... @@ -1,17 +1,19 @@ 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. 1 +**Non-service-affecting** final template to use the **R22** double lane release. 3 3 4 - Overview5 -T hisupdateimprovesthe securityand enhancestheauto-healingfunctionalityonour3rdgenerationruntimes.3 +**Process** 4 +To use the new R22 release of our cloud template we upgrade in one step. This step is non-service-affecting. 6 6 7 -Updates 6 +**Overview** 7 +* Update versions of dependencies. 8 8 9 -Improve Locking mitigation in the Artemis server (autohealing). 10 -Improve security by disabling SSH access to cloud machines. 11 -Update Steps 9 +**Update Steps** 10 +* Use the final R22 template (non-service affecting)(duration: < 5 minutes) 12 12 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. 12 +* User actions after applying the final template: 13 +** Check if all runtimes are up via the runtime overview or Deploy Architecture 14 +** Check if all runtimes have been installed according to the active release 15 +** Check if messages pass through the bus by verifying a critical message flow in external systems 16 + 17 +**Remarks** 18 + 19 +Deadline is December 14th, 2025