Skip to Content

Changes for page R19 Docker - Double Lane

Last modified by Erik Bakker on 2025/10/23 08:47
From version 26.1
edited by Erik Bakker
on 2025/06/30 09:51
Change comment: There is no comment for this version
To version 10.1
edited by Erik Bakker
on 2023/06/06 08:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R17 Docker - Double Lane
1 +R9 Docker - Double lane
Content
... ... @@ -1,17 +1,24 @@
1 -**Service affecting** final template to use the R16 double lane release.
1 +Service affecting R9 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture.
2 2  
3 3  **Process**
4 -o use the new R17 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 two steps to use the new R9 release of the cloud template. Of these two steps, the intermediate step is non-service affecting, and the final step is service affecting.
5 5  
6 6  **Overview**
7 -* New connections to a **new** carwash.
7 +It improves the ease with which Static IP Addresses can be gathered and distributed by a user while at the same thing improving the security by upgrading the Ubuntu version.
8 8  
9 -**Update Steps**
10 -* Use the final template (non service affecting)(duration: < 10 minutes)
11 -** This step will replace all connections.
9 +**Updates**
10 +* Ability to fetch Static IP Addresses
11 +* New Ubuntu version with new security patches.
12 12  
13 +**Update Steps**
14 +* Use the intermediate template (non-service affecting) (duration: 10 minutes)
15 +** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot.
16 +** The network drive containing the Artemis queue store and your Elastic IPs will remain.
17 +* Use the final template (service affecting) (duration: 10 minutes)
18 +** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
19 +** The runtimes on the machines will be restored using the active release in the eMagiz portal.
13 13  * User actions after applying the final template:
14 -** Check if all runtimes are up via the runtime overview or Deploy Architecture
15 -** Check if all runtimes have been installed according to the active release
16 -** Check if messages pass through the bus by verifying a critical message flow in external systems
21 +** Check if all runtimes are reachable by Deploy Architecture.
22 +** Check if all flows have been installed according to the active release.
23 +** Check if messages pass through the model by verifying a critical message flow in external systems.
17 17