Resource Orchestration Service (ROS) allows you to create scenarios. When you create a scenario, you can specify the scope of a collection of resources on a visualized interface and perform operations such as replication, management, or migration on the resources in a simplified manner.

Terms

Term Description
resource replication If you want to replicate a collection of resources and dependencies between the resources, you can create a resource replication scenario. This type of scenario allows you to replicate all existing resources within the specified scope and generates a collection of resources that have the same architecture as the existing resources.

For more information, see Use a scenario to replicate resources.

resource management If you want to import a collection of existing resources to a stack and manage the resources in a centralized manner, you can create a resource management scenario.

For more information, see Use a scenario to manage resources.

resource migration If you want to migrate a collection of resources and dependencies between the resources, you can create a resource migration scenario. When you migrate the resources, ROS generates a stack. You can view the migration progress on the Stacks tab of the scenario management page. After you migrate the resources, you can delete source resources.

For more information, see Use a scenario to migrate resources.

source node After you create a scenario, ROS filters resources within the specified scope and generates a source node. The source node contains the information about the resources, such as the resource architecture and properties.
  • In a resource replication scenario, ROS uses the source node to store the information about existing resources, such as the resource IDs, types, and properties.
  • In a resource management scenario, ROS imports the resources on the source node and generates a stack based on the imported resources. This way, you can manage the resources in a centralized manner.
new node After you create a resource replication scenario, ROS adds resources that are required for the scenario and generates a new node based on the content on the source node. The new node contains the information about the resources that you want to replicate, such as the resource types and properties.

The properties and number of resources on the new node may be different from the properties and number of resources on the source node. When ROS generates a scenario, ROS may generate new resource properties that are suitable for the scenario, such as the properties that are related to specifications and CIDR blocks. ROS determines the type and number of resources on the new node based on the dependencies between and the attributes of the resources.

  • Example 1: A source node contains an Elastic Compute Service (ECS) instance whose specifications are ecs.sn1ne.large, 2 vCPUs, and 4 GB memory. If the preceding specifications are out of stock when ROS generates a scenario based on the source node, ROS uses another ECS instance that has similar specifications to generates a new node.
  • Example 2: A source node contains only an elastic IP address (EIP) and resources that are required to associate the EIP with an instance. You can associate an instance with only one EIP. Therefore, when ROS generates a scenario based on the source node, the new node contains only the EIP. The new node cannot contain the required resources.

How a scenario works

The following figure shows how a scenario works.

001
When you create a scenario, you can select a scenario type, and specify a resource scope by tag, resource group, or resource. If you specify the resource scope by resource, you must configure the resource type and the resource ID. ROS filters resources within the specified scope and generates a source node. The source node contains the information about the resources, such as the resource architecture and properties.
  • Resource replication scenario

    ROS adds resources that are required for the scenario and generates a new node. The new node contains the information about resources that you want to replicate, such as the resource types and properties. After you create a resource replication scenario, you can replicate resources. ROS generates a stack based on the content on the new node. This way, ROS replicates a collection of resources that have the same architecture as the resources on the source node. You can view the stack on the Stacks tab of the scenario management page.

  • Resource management scenario

    After you create a resource management scenario, you can manage the resources. ROS imports resources on the source node and generates a stack based on the imported resources. This way, you can manage the resources in a centralized manner. You can view the stack on the Stacks tab of the scenario management page.

  • Resource migration scenario

    ROS adds resources that are required for the scenario and generates a new node. The new node contains the information about resources that you want to migrate, such as the resource types and properties. After you create a resource migration scenario, you can migrate resources. ROS generates a stack based on the content on the new node. This way, ROS replicates a collection of resources that have the same architecture as the resources on the source node. You can view the stack on the Stacks tab of the scenario management page. After you migrate the resources, you can delete the resources on the source node. Before you can delete the resources, ROS generates a stack of the resource management type.

Resource types that support the scenario feature

The scenario feature is supported for specific resource types. For more information, see Resource types supported by scenarios.

Generate a template based on a scenario

You can use a template that is automatically generated based on a resource management scenario to deploy multiple resources at a time. For more information, see Generate a template based on a scenario with one click.