Wiki source code of R9 Docker - Double lane
Last modified by Erik Bakker on 2023/07/10 15:13
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
10.1 | 1 | Service affecting R9 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture. |
| |
1.1 | 2 | |
| |
10.1 | 3 | **Process** |
| 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 | |||
| |
1.1 | 6 | **Overview** |
| |
12.1 | 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. |
| |
1.1 | 8 | |
| 9 | **Updates** | ||
| |
10.1 | 10 | * Ability to fetch Static IP Addresses |
| |
11.1 | 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 | * Improved Cloud instance status check and auto repair | ||
| |
13.1 | 15 | * Added new version of the deployment agent, solving a known portainer bug where all containers are replaced instead of one. |
| |
1.1 | 16 | |
| |
8.1 | 17 | **Update Steps** |
| |
10.1 | 18 | * Use the intermediate template (non-service affecting) (duration: 10 minutes) |
| 19 | ** This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot. | ||
| 20 | ** The network drive containing the Artemis queue store and your Elastic IPs will remain. | ||
| 21 | * Use the final template (service affecting) (duration: 10 minutes) | ||
| 22 | ** This step will upgrade the primary machines in the first Availability Zone in your Cloudslot. | ||
| 23 | ** The runtimes on the machines will be restored using the active release in the eMagiz portal. | ||
| |
8.1 | 24 | * User actions after applying the final template: |
| |
9.1 | 25 | ** Check if all runtimes are reachable by Deploy Architecture. |
| |
10.1 | 26 | ** Check if all flows have been installed according to the active release. |
| 27 | ** Check if messages pass through the model by verifying a critical message flow in external systems. | ||
| 28 |