Skip to Content

Changes for page R14 Docker - Single Lane

Last modified by Erik Bakker on 2025/04/07 10:12
From version 17.2
edited by Erik Bakker
on 2023/09/13 07:20
Change comment: Update document after refactoring.
To version 29.1
edited by Erik Bakker
on 2025/01/20 07:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -R9 Docker - Single lane
1 +R13 Docker - Single Lane
Content
... ... @@ -1,24 +1,21 @@
1 -Service affecting R8 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture.
1 +Service affecting template to use the R13 single lane release.
2 2  
3 3  **Process**
4 -We upgrade in one step to use the new R8 release of the cloud template. This step is service affecting.
4 +To use the new R13 template on your environment, we upgrade the control agent of **all** machines and disk encryption on **cloud** machines. This update is service affecting. The goal of this update is to increase the security of the disks related to your machine by encrypting them and to update the control agent version to 2.21.4.
5 5  
6 6  **Overview**
7 -It improves the ease with which Static IP Addresses can be gathered and distributed by a user while at the same time improving the security and auto-healing functionality.
7 +* Security improvements to the eMagiz infrastructure.
8 +* Update control agent version.
8 8  
9 -**Updates**
10 -* Ability to fetch Static IP Addresses
11 -* New ubuntu version with new security patches.
12 -* Disable IPv6 on startup
13 -* Enable new Out of Memory killer to protect instance becoming unhealthy
14 -* Added new version of the deployment agent, solving a known portainer bug where all containers are replaced instead of one.
15 -
16 16  **Update Steps**
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.
11 +* Use the final template (service affecting)(duration: 10 minutes)
12 +** This step will upgrade the primary machines in the first Availability Zone in your cloudslot
13 +*** The network drive containing the Artemis queue store and your Elastic IPs will remain.
14 +** This step will upgrade the control agent version on **all** machines (cloud and on-premise) to version 2.21.4
15 +*** The runtimes on the machines will be restored using the active release in the eMagiz portal
16 +
20 20  * User actions after applying the final template:
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.
18 +** Check if all runtimes are up via the runtime overview
19 +** Check if all runtimes have been installed according to the active release
20 +** Check if messages pass through the bus by verifying a critical message flow in external systems
24 24