Changes for page R19 Docker - Double Lane
Last modified by Erik Bakker on 2025/10/23 08:47
From version 30.1
edited by Erik Bakker
on 2025/10/23 08:47
on 2025/10/23 08:47
Change comment:
There is no comment for this version
To 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
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -R1 9Docker - Double Lane1 +R16 Docker - Double Lane - Content
-
... ... @@ -1,15 +1,19 @@ 1 -**Non-service -affecting** final template to use the**R19**single lane release.1 +**Non-service affecting** final template to use the R16 double lane release. 2 2 3 3 **Process** 4 -To use the new R1 9release of our cloud template we upgrade in one step.Thisisarolling update,makingit non-service affecting.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 5 6 6 **Overview** 7 -* Non-service-affectingtemplate to upgrade tothelatestversionofthe authorizationserver. Applying this template only affectscustomers running on DSH EventStreaming.8 -* Update the versionof authorizationserveras preparationfortheAPI-Gateway MAM migration.7 +* Security improvements to the eMagiz infrastructure. 8 +* Update control agent version. 9 9 10 10 **Update Steps** 11 -* Use the final R19 template (non-service affecting)(duration: < 5 minutes) 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. 12 12 13 -**Remarks** 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 14 14 15 -Deadline of December 14th, 2025