CloudOps Orchestration Service (OOS) is applicable in scenarios such as event-driven O&M, batch operations, image update, O&M application review, scheduled tasks, and cross-region O&M. You can customize a variety of templates based on your actual use.
Perform event-driven O&M tasks
You can use OOS to configure an event to trigger an O&M action. For example, if the CPU usage of an Elastic Cloud Service (ECS) instance reaches 85%, OOS automatically restarts the ECS instance to prevent business interruption. This way, you do not need to manually perform O&M tasks and the O&M tasks can be performed in an efficient manner.
Perform multiple O&M tasks at a time
You can use OOS to perform O&M operations on multiple objects such as ECS instances at a time to maintain the smooth operation and healthy status of your business.
For example, to check the available space of disks in multiple ECS instances, you can perform the following steps: Specify the ECS instances to be checked by name, tag, or resource group, run a Cloud Assistant command to check the available space of disks on the specified ECS instances, and then view the returned result.
Related public templates
Template | Description | References |
ACS-ECS-BulkyDeleteInstances | Releases multiple pay-as-you-go ECS instances at a time. | |
ACS-ECS-BulkyDeleteInstancesWithApproval | Releases multiple pay-as-you-go ECS instances at a time after approval. | |
ACS-ECS-BulkyDeletePrepaidInstances | Releases multiple subscription ECS instances at a time. The ECS instances must be stopped before they are released. | |
ACS-ECS-BulkyInstallLogAgent | Installs a Simple Log Service agent on multiple ECS instances at a time. | |
ACS-ECS-BulkyRebootInstances | Restarts multiple ECS instances at a time. | |
ACS-ECS-BulkyRunCommand | Runs a Cloud Assistant command on multiple ECS instances at a time. | |
ACS-ECS-BulkyStartInstances | Starts multiple ECS instances at a time. | |
ACS-ECS-BulkyStopInstances | Stops multiple ECS instances at a time. | |
ACS-ECS-BulkyTagInstanceByLinuxKernelVersion | Adds the version number of the Linux kernel as a tag value to multiple ECS instances at a time. The ECS instances are specified by instance IDs. | |
ACS-ECS-BulkyTagInstanceByOSType | Adds the type of the operating system as a tag value to multiple ECS instances at a time. The ECS instances are specified by instance IDs. | |
ACS-ECS-BulkyTagInstanceByRunCommandResult | Adds the execution result of a Cloud Assistant command as a tag value to multiple ECS instances at a time. | |
ACS-ECS-BulkyUpgradeInternetBandwidth | Upgrades the public bandwidth of multiple ECS instances at a time. | |
ACS-ECS-CloneInstancesAcrossAZ | Clones multiple ECS instances across zones at a time. | |
ACS-ECS-CloneInstancesAcrossRegion | Clones multiple ECS instances across regions at a time. |
Update images
To ensure a secure runtime environment for ECS instances, you must install the latest patches on the ECS instances or update the components on which the ECS instances depend. OOS allows you to update the images of ECS instances. You can generate a new image from a source image and use the new image for testing and production.
Related public template
Template | Description | References |
ACS-ECS-UpdateImage | Runs commands to update an existing ECS image and create a new ECS image. |
Manage approval requests
In many scenarios, you need to manage approval requests to ensure that only expected O&M operations are performed. You can define an ACS::Approve action in a template. This action ensures that an O&M task is approved before the task is executed and that expected O&M tasks are executed without mistakes.
Related public templates
Template | Description | References |
ACS-ECS-BulkyDeleteInstancesWithApproval | Releases pay-as-you-go ECS instances after approval. | |
ACS-ECS-RunInstancesWithApproval | Creates ECS instances after approval. |
Execute scheduled O&M tasks
OOS allows you to execute O&M tasks at the specified points in time. For example, you can create a template and execute it at 00:00 every day to delete Object Storage Service (OSS) files that are generated by tests within an account on the previous day. This produces a new and clean test environment every day to prevent subsequent test results from being affected.
Related public templates
Template | Description | References |
ACS-ECS-ScheduleToRebootInstances | Restarts ECS instances at the specified point in time. | |
ACS-ECS-ScheduleToStartInstances | Starts ECS instances at the specified point in time. | |
ACS-ECS-ScheduleToStopInstances | Stops ECS instances at the specified point in time. | |
ACS-ECS-ScheduleToUpgradeInternetBandwidth | Upgrades the temporary bandwidth of ECS instances at the specified point in time. |
Perform cross-region O&M tasks
High-availability architectures provide the feature of multi-zone deployment, which leads to increasingly complex O&M tasks. OOS allows you to create templates for O&M operations in different regions to perform O&M tasks across regions.
Related public templates
Template | Description | References |
ACS-ECS-CloneInstancesAcrossAZ | Clones ECS instances across zones. | |
ACS-ECS-CloneInstancesAcrossRegion | Clones ECS instances across regions. |
Perform O&M in multiple regions
If you use resources in multiple regions, synchronization is required for the consistency of resources. For example, you may need to enable the logging feature for OSS buckets in multiple regions at a time.