Changes for page R20 Docker - Single Lane
Last modified by Erik Bakker on 2026/06/29 09:44
From version 43.1
edited by Erik Bakker
on 2026/06/29 09:44
on 2026/06/29 09:44
Change comment:
There is no comment for this version
To version 19.1
edited by CarlijnKokkeler
on 2023/11/21 11:47
on 2023/11/21 11:47
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -R 20Docker - Single Lane1 +R11 Docker - Single Lane - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,18 +1,19 @@ 1 - {{info}}Thisenvironment template needs to be appliedon all environmentsofall(your)modelsbefore August29th, 2026{{/info}}1 +Service affecting template that introduces faster machine boot up and improved auto-healing. 2 2 3 -**Non-Service affecting** final template to use the **R20** single lane release. This upgrade is non-service-affecting. 4 - 5 5 **Process** 6 -We upgrade in one step to use the new **R20**release of the cloud template. This step isnon-service affecting.4 +We upgrade in one step to use the new R11 release of the cloud template. This step is service affecting. 7 7 8 8 **Overview** 9 -* Improve internal monitoring and alerting capabilities 10 -* Improve management of users and permissions 7 +This version contains performance improvements for auto-healing and machine boot up time. 11 11 9 +**Updates** 10 +* Ubuntu version update including latest security patches. 11 +* This upgrade is service-affecting, as all instances have to be recreated. 12 + 12 12 **Update Steps** 13 -* Use the final **R20**template (non-service affecting) (duration: 10 minutes)14 -** Noneofthe runtimeswillbetouched.15 -** Authorizationservers willperforma rollingupdate.14 +* Use the final template (service affecting) (duration: 10 minutes) 15 +** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot. 16 +** The runtimes on the machines will be restored using the active release in the eMagiz portal. 16 16 * User actions after applying the final template: 17 17 ** Check if all runtimes are reachable by Deploy Architecture. 18 18 ** Check if all flows have been installed according to the active release.