R9 Docker - Double lane

Service affecting R9 template that improves security and allows for the retrieval of Static IP addresses from Deploy Architecture.

Process
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.

Overview
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.

Updates

• Ability to fetch Static IP Addresses
• New ubuntu version with new security patches.
• Disable IPv6 on startup
• Enable new Out of Memory killer to protect instance becoming unhealthy
• Improved Cloud instance status check and auto repair
• Added new version of the deployment agent, solving a known portainer bug where all containers are replaced instead of one.

Update Steps

• Use the intermediate template (non-service affecting) (duration: 10 minutes)
  • This step will upgrade the backup machines hosted in the second Availability Zone in your Cloudslot.
  • The network drive containing the Artemis queue store and your Elastic IPs will remain.
• Use the final template (service affecting) (duration: 10 minutes)
  • This step will upgrade the primary machines in the first Availability Zone in your Cloudslot.
  • The runtimes on the machines will be restored using the active release in the eMagiz portal.
• User actions after applying the final template:
  • Check if all runtimes are reachable by Deploy Architecture.
  • Check if all flows have been installed according to the active release.
  • Check if messages pass through the model by verifying a critical message flow in external systems.