Changes for page R16 Docker - Double Lane
Last modified by Erik Bakker on 2025/04/07 10:15
From version 25.1
edited by Erik Bakker
on 2025/04/07 10:15
on 2025/04/07 10:15
Change comment:
There is no comment for this version
To version 9.1
edited by Erik Bakker
on 2023/04/28 08:36
on 2023/04/28 08:36
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 16Docker - DoubleLane1 +R8 Docker - Double lane - Content
-
... ... @@ -1,19 +1,16 @@ 1 -**Non-service affecting** final template to use the R16 double lane release. 1 +Non service affecting final template to use the R8 double lane release. 2 +Process: To use the new R8 release of our cloud template we upgrade in one steps, the update is non service affecting. 2 2 3 -**Process** 4 -To use the new R16 release of our cloud template we upgrade in one steps, the update is non service affecting. This update aims to increase the stability of models running in Production. 5 - 6 6 **Overview** 7 -* Security improvements to the eMagiz infrastructure. 8 -* Update control agent version. 5 +This update improves the security and enhances the auto-healing functionality on our 3rd generation runtimes. 9 9 10 -**Update Steps** 11 -* Use the final template (non service affecting)(duration: 3 minutes) 12 -** This step will upgrade the machines in your cloudslot 13 -*** The network drive containing the Artemis queue store and your Elastic IPs will remain. 7 +**Updates** 8 +* Improve Locking mitigation in the Artemis server (autohealing). 9 +* Improve security by disabling SSH access to cloud machines. 14 14 11 +**Update Steps** 12 +* Use the final R8 template (non service affecting) (duration: 4 minutes) 15 15 * User actions after applying the final template: 16 -** Check if all runtimes are up via the runtime overview 17 -** Check if all runtimes have been installed according to the active release 18 -** Check if messages pass through the bus by verifying a critical message flow in external systems 19 - 14 +** Check if all runtimes are reachable by Deploy Architecture. 15 +** Check if all images have been installed according to the active release. 16 +** Check if messages pass through the bus by verifying a critical message flow in external systems.