Resource Management:Use tags for automated O&M

Scenarios

As cloud resources grow, manual O&M no longer scales. OOS applies the operations-as-code approach: you convert manuals such as O&M guides, user guides, and operation guides into reusable templates. Tag your resources by business dimension first so OOS can identify and act on them during automated runs. Together, the Tag service and OOS provide an end-to-end O&M solution.

Benefits

• Perform bulk O&M on multiple resources at once. For example, start, stop, or restart multiple Elastic Compute Service (ECS) instances in a single run.

• Manage tags for multiple resources at once. For example, add or modify tags in bulk.

• Orchestrate operations across different tag dimensions. To include or exclude a resource, update its tags in the Resource Management console instead of modifying orchestration scripts.

Workflow

1. Tag resources by business dimension for centralized management.

2. Create and run an OOS template to automate O&M tasks.

Best practices

Best practices for tag-based automated O&M with OOS:

• Bulk update tag values using OOS

• Use OOS to add tags to multiple ECS instances at a time

• Bulk start tagged ECS instances with OOS

• Use OOS to add multiple tags to resources at a time

• Use OOS to enable topics and groups in a Message Queue for Apache RocketMQ instance to inherit tags from the instance

• Use OOS to inherit tags from ECS instances for the resources of the ECS instances at a time

• Add tagged ECS instances to matching security groups