Changes for page R17 Docker - Single Lane
Last modified by Erik Bakker on 2025/10/23 08:46
From version 36.1
edited by Erik Bakker
on 2025/10/23 08:46
on 2025/10/23 08:46
Change comment:
There is no comment for this version
To version 30.1
edited by Erik Bakker
on 2025/04/07 10:12
on 2025/04/07 10:12
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 7Docker - Single Lane1 +R14 Docker - Single Lane - Content
-
... ... @@ -1,15 +1,19 @@ 1 -** Non-service-affecting**finaltemplate to use the**R17**single lane release.1 +**Service affecting** template to use the R14 single lane release. 2 2 3 3 **Process** 4 -To use the new R1 7release ofourcloudtemplateweupgrade in onestep.Thisisa rolling update,making it non-service affecting.4 +To use the new R14 template on your environment, we replace all your machines with new ones to activate the new configuration. This update is service affecting and aims to increase the stability of models running in Production. 5 5 6 6 **Overview** 7 -* Non-service-affecting templateto upgrade tothe latestversion of theauthorizationserver. Applyingthis templateonlyaffects customersrunningonDSH Event Streaming.8 -* Updatethe versionof authorizationserver aspreparation fortheAPI-Gateway MAM migration.7 +* Stability improvements to your **Production** model. 8 +* More control on resource management 9 9 10 10 **Update Steps** 11 -* Use the final R17 template (non-service affecting)(duration: < 5 minutes) 11 +* Use the final template (service affecting)(duration: 10 minutes) 12 +** This step will upgrade the machines in your cloud slot 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 model by verifying a critical message flow in external systems 14 14 15 -Deadline of December 14th, 2025