Automated task
|
Category |
Feature |
Description |
References |
|
O&M template |
Create an O&M template |
CloudOps Orchestration Service (OOS) uses templates to define the O&M operations that require orchestration. The templates are classified into public templates and custom templates. You can use the OOS process configuration editor to create templates. The template content uses the YAML or JSON format. |
|
|
Create an execution |
You can execute a public or custom template in multiple execution modes. |
||
|
Manage executions |
You can view, clone, cancel, or delete a created execution. |
||
|
Deliver execution records |
OOS allows you to use the execution record delivery feature to deliver execution records in OOS to Object Storage Service (OSS) or Simple Log Service for persistent storage. This way, you can query the execution records to perform operations such as behavior analysis, security analysis, resource change tracking, and compliance auditing. |
Deliver execution records | |
|
Common O&M scenarios |
Scheduled O&M task |
If you want to perform O&M operations at a specific point in time, you can use the Scheduled O&M feature of OOS. OOS allows you to run a scheduled O&M task once at the specified time or periodically. |
Perform scheduled O&M |
|
Alert O&M task |
OOS supports O&M tasks for threshold-triggered alerts based on metrics of cloud services. An alert O&M task executes the specified template when the specified metric of a monitored cloud service reaches the threshold. An alert O&M task keeps running to listen to the specified alert until you cancel the task. For example, you can configure an alert O&M task to automatically clear the log directory when the disk usage exceeds 80%. |
Create an alert O&M task | |
|
Event-triggered O&M task |
Cloud service events indicate status changes of cloud service resources. For example, a cloud service event is generated if an Elastic Compute Service (ECS) instance is restarted abnormally or released, a snapshot is created for an ECS instance, or O&M operations are to be performed on an ECS instance. OOS supports O&M tasks triggered by cloud service events. In an event-triggered O&M task, you can specify the template that is to be executed when the specified event occurs. An event-triggered O&M task keeps running to listen to the specified cloud service event until you cancel the task. |
Create an event-trigger O&M task |
Parameter store
|
Category |
Feature |
Description |
References |
|
Common parameter |
Create or delete a common parameter |
When you use Alibaba Cloud services, you can store common parameters and the parameter values without the need for encryption. You can create, search for, and update common parameters in the parameter store of OOS. |
Common parameters |
|
Encrypted parameter |
Create or delete an encrypted parameter |
In addition to common parameters, OOS also supports encrypted parameters. The values stored in such parameters are encrypted by using Key Management Service (KMS). You can create, search for, and update encrypted parameters in the parameter store of OOS. |
Encrypted parameters |
|
Public parameter |
Use a public parameter |
You can use public parameters to store the public information about the basic configurations of cloud services, such as the ID of the latest image in an ECS image family. |
Best practices for common parameters |
|
Parameter usage |
Use a parameter |
You can use common parameters and encrypted parameters in OOS, Resource Orchestration Service (ROS), and Cloud Assistant commands. |
Server management
|
Category |
Feature |
Description |
References |
|
Patch management |
Patch baseline |
The patch management feature predefines a default patch baseline for each operating system. You can create a patch baseline to specify custom rules of scanning and installing patches for an operating system. A patch baseline specifies the rules of installing patches on your instance. You can specify the following items for a patch baseline: operating system type, patch categories, patch severities, and conditions for automatic approval. |
|
|
Patch-based fix |
You can use the patch management feature of OOS to scan for or install patches with ease. The patch management feature supports the following modes: immediate fix and scheduled fix. |
||
|
Configuration list management |
Create a configuration list |
You can use the configuration list feature of OOS to collect and manage the metadata of ECS instances in the Alibaba Cloud computing environment. The metadata includes application information, network configuration, services, file system data, Windows-specific data, and instance details. |
Create a configuration list |
|
Process the collected data of a configuration list |
After a configuration list is created, you can use the aggregate feature to view a summary of the collected data. For example, you collect the application information of 100 instances. You can use the aggregate feature to view the number of applications that are installed on each instance. You can also specify application properties to filter the collected data. For example, if you set the Name property to curl, the instances that contain the application named curl are returned. |
Aggregate or filter the collected data of a configuration list | |
|
Extension |
Install or uninstall an extension |
In OOS, you can develop custom extensions based on your needs and specific scenarios, and publish custom extensions as public extensions for others to use. After you create an extension, you can create an extension task in OOS to install or uninstall the extension on one or more ECS instances. |
- |
|
Create a custom extension |
OOS allows you to develop custom extensions based on your requirements and specific scenarios. After you create an extension, you can create an extension task in OOS to install the extension. |
- |
|
|
Update a custom extension |
OOS allows you to modify the information of a custom extension. |
- |
|
|
Publish a custom extension as a public extension |
When you publish a custom extension as a public extension, you must specify which version of the custom extension is to be published as a public extension. When you publish a custom extension as a public extension for the first time, the system automatically creates the v1 version of the public extension. Later versions are generated when you publish the custom extension as a public extension again. |
- |
Application management
|
Category |
Feature |
Description |
References |
|
Application configurations |
Create or delete an application |
You can create or delete an application. An application can be created based on new or existing resources imported by using tags or resource groups. You can deploy an application by using the following methods: use an application template to deploy an application, deploy a third-party application from the application market, use an ROS template to deploy a custom application. |
- |
|
Update an application |
You can modify the advanced settings and description of an application. |
- |
|
|
Application group configurations |
Create or delete an application group |
You can create multiple application groups based on your business requirements. For example, you can create and deploy application groups for the test environment, staging environment, and production environment. You can create applications groups in different regions. |
- |
|
Update an application group |
You can modify the name of an application group. |
- |
Open source tools
|
Category |
Feature |
Description |
References |
|
Terraform |
Terraform |
Terraform is an open source tool that you can use to preview, configure, and manage the infrastructure and resources of cloud services in a secure and efficient manner. You can use Terraform to manage and configure the cloud resources of OOS in an efficient manner. |
Use Terraform to manage OOS |