Skip to Content

Changes for page R16 Docker - Double Lane

Last modified by Erik Bakker on 2025/04/07 10:15
From version 21.1
edited by Carlijn Kokkeler
on 2024/04/23 11:18
Change comment: There is no comment for this version
To version 25.1
edited by Erik Bakker
on 2025/04/07 10:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R15 Docker - Double Lane
1 +R16 Docker - Double Lane
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,19 +1,19 @@
1 -Non-service affecting final template to use the R15 double 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 R15 template on your environment, we upgrade the agent of external machines. This update is not 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-affecting template that updates the on-premise machine agents.
8 -* The cloud-environment for this template does not contain any changes compared to the R14 template.
7 +* Security improvements to the eMagiz infrastructure.
8 +* Update control agent version.
9 9  
10 -**Updates**
11 -* This upgrade updates the machine agent to version 2.18.4.
12 -* This upgrade is non-service affecting.
13 -
14 14  **Update Steps**
15 -* Use the final R15 template (non-service affecting) (duration: approx. 1 minute per machine).
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.
14 +
16 16  * User actions after applying the final template:
17 -** Check if all on-premise runtimes are reachable by the runtime overview.
18 -** Check if messages pass through the bus by verifying a critical message flow in external systems.
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
19 19