Changes for page R15 Docker - Single Lane
Last modified by Erik Bakker on 2025/06/30 09:51
From version 12.2
edited by Erik Bakker
on 2023/03/03 11:29
on 2023/03/03 11:29
Change comment:
Update document after refactoring.
To version 31.1
edited by Erik Bakker
on 2025/06/30 09:49
on 2025/06/30 09:49
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 6-Docker Singlelane1 +R15 Docker - Single Lane - Content
-
... ... @@ -1,17 +1,16 @@ 1 -Non service affecting final template to use the R6 double lane release. 2 -Process: To use the new R6 release of our cloud template we upgrade in one steps, the update is non service affecting. 1 +**Service affecting** template to use the R15 single lane release. 3 3 3 +**Process** 4 +To use the new R15 template on your environment, we replace all connections to activate the new configuration. This update is service affecting and aims to enable data traffic via our new carwash. 5 + 4 4 **Overview** 5 - Thisupdate changes the Cloud portcheck, coordinationfaledandcleanstorefunctionality on our3rd generation runtimes.7 +* New connections to a **new** carwash. 6 6 7 -**Updates** 8 -* Cloud Port check: When the software does not expose the right ports, it will be restarted 9 -* Coordnation failed: When the runtimes failes to startup due to a corrupted startup order, the runtime will restart freshly to remove the corrupted state. 10 -* Clean store: The functionality to clean a store is added for generation 3 runtimes. See [[this link>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.eMagiz Cloud Management.expert-emagiz-cloud-management-clean-store||target="blank"]] 11 - 12 12 **Update Steps** 13 -* Use the final R6 template (non service affecting) (duration: 4 minutes) 10 +* Use the final template (service affecting)(duration: < 10 minutes) 11 +** This step will replace all connections. 12 + 14 14 * User actions after applying the final template: 15 -** Check if all runtimes are reachablebythe runtimedashboard.16 -** Check if all flows have been installed according to the active release.17 -** Check if messages pass through the busby verifying a critical message flow in external systems.14 +** Check if all runtimes are up via the runtime overview 15 +** Check if all runtimes have been installed according to the active release 16 +** Check if messages pass through the model by verifying a critical message flow in external systems