R14 - Non-services affecting
Non service affecting intermediate template to use the R14 double lane release. This is the first of two steps for your upgrade to the new R14 template.
Steps:
- Use this intermediate template (non service affecting) (duration: 4 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: 4 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 the runtime dashboard
- Check if all flows have been installed according to the active release
- Check if messages pass through the bus by verifying a critical message flow in external systems
Features R14 release:
- Move to Python 3.9 version for cloudslot orchestration
- Better control the unattended updates of instance packages
- Use new point release of Ubuntu with latest security patches
R14 - Services affecting
Service affecting final template to use the R14 double lane release.
Process: To use the new R14 release of our cloud template we upgrade in two steps, with only the second step being service affecting. Below is the remaining step.
Steps:
- Use the final R14 template (service affecting) (duration: 4 minutes)
User actions after applying the final template: - Check if all ".01" runtimes are reachable by the runtime dashboard - Check if all flows have been installed according to the active release - Check if messages pass through the bus by verifying a critical message flow in external systems
Features R14 release:
- Move to Python 3.9 version for cloudslot orchestration
- Better control the unattended updates of instance packages
- Use new point release of Ubuntu with latest security patches