Changes for page R28 - Single lane

Last modified by Erik Bakker on 2025/06/30 09:55

From version 12.1
edited by Erik Bakker
on 2025/06/30 09:55
Change comment: There is no comment for this version
To version 11.1
edited by Carlijn Kokkeler
on 2024/01/18 11:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R28 - Single lane
1 +R27 - Single lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,17 +1,19 @@
1 -**Service affecting** template to use the R28 single lane release.
1 +Non-service affecting R27 template that improves auto healing. More information on what auto healing involves can be found [[here>>https://docs.emagiz.com/bin/view/Main/eMagiz%20Academy/Fundamentals/fundamental-emagiz-cloud-inner-workings||target="blank"]].
2 2  
3 3  **Process**
4 -To use the new R28 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.
4 +We upgrade in one step to use the new R27 release of the cloud template. This step is non-service affecting.
5 5  
6 6  **Overview**
7 -* New connections to a **new** carwash.
7 +This version contains auto healing performance improvements.
8 8  
9 -**Update Steps**
10 -* Use the final template (service affecting)(duration: < 10 minutes)
11 -** This step will replace all connections.
9 +**Updates**
10 +* Version update including auto healing performance improvements.
11 +* This upgrade is non-service affecting.
12 12  
13 +**Update Steps**
14 +* Use the final template (non-service affecting)
13 13  * User actions after applying the final template:
14 -** Check if all runtimes are up via the runtime dashboard or Deploy Architecture
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
16 +** Check if all runtimes are reachable by Deploy Architecture.
17 +** Check if all flows 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.
17 17