R13 Docker - Double Lane

Service affecting template that introduces faster machine boot up and improved auto-healing.

Process
We upgrade in two steps to use the new R13 release of the cloud template. Of these two steps, the intermediate step is non-service affecting, and the final step is service affecting.

Overview
This version contains performance improvements for auto-healing and machine boot up time.

Updates

• Ubuntu version update including latest security patches.
• This upgrade is service-affecting, as all instances have to be recreated.

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.