Application Orchestration Service for Containers

With Application Orchestration Service (AOS), users can deploy applications in the cloud by writing templates (declarations of resources that make up stacks), and create stacks from the templates. AOS also provides application lifecycle management features, such as starting, changing, and deleting. 

Functions

Template creation

A template is a text file that uses AOS syntax to describe application attributes, cloud service configurations, and dependencies between applications and cloud services. Users can write templates from scratch in JSON or YAML format. In addition to writing templates on the web UI, users can also write it on a local host and then upload it to AOS.

Flexible alarm function

Users can flexibly set alarm rules on any of the monitoring metrics, configure alarm thresholds, as well as enable or disable the alarm function.

• When adding an alarm rule, users can select multiple monitored objects for a single metric to add monitored objects in batches
• Users can modify the parameters of the alarm rule, such as the alarm threshold. The modified alarm rule will take effect at the start of the next monitoring period.
• If the monitored object of the alarm rule is not used temporarily, users can disable the alarm rule, and then enable the alarm rule if the object is used again.
• If the monitored object of the alarm rule is no longer used or has been deleted, users can manually delete the alarm rule.

Real-time notification

Users can configure alarm notification to receive emails when alarms are generated.

• If the alarm status is changed, for example, when an alarm is generated, if the data becomes insufficient (beyond the validity), or if the alarm is cleared, the system sends emails to the email box configured when users register on the website.
• If an alarm is not cleared for a long period of time, the system only sends a notification to users when the alarm was generated.

Stack creation

A stack is a collection of applications and cloud service resources. The applications or cloud services in a stack are treated as a unit when being created or deleted. Users can create stacks from templates.