Overview

Resource replication scenario

To replicate a collection of resources and their dependencies, create a resource replication scenario. This scenario replicates all resources within the specified scope and generates a new collection with the same architecture. For more information, see Resource replication scenarios.

You can specify the resource scope by source tag, resource group, or individual resource. When you create a resource replication scenario, ROS adds the required resources, including their types and properties, to generate a new node. ROS then creates a stack based on the new node to replicate resources with the same architecture as the source node.

Resource management scenario

To import existing resources into a stack for centralized management, create a resource management scenario. For more information, see Resource management scenarios.

You can specify the resource scope by source tag, resource group, or individual resource. ROS imports the resources from the source node and generates a stack, enabling centralized management.

You can also generate a template from a resource management scenario and use the template to deploy multiple resources at a time. For more information, see Generate a template from a resource scenario.

Resource migration scenario

To migrate a collection of resources and their dependencies, create a resource migration scenario. During migration, ROS generates a stack. You can view the migration progress on the Stacks tab of the resource scenario details page. After migration, you can delete the source resources. For more information, see Resource migration scenario.

You can specify the resource scope by source tag, resource group, or individual resource. When you create a resource migration scenario, ROS adds the required resources, including their types and properties, to generate a new node. ROS then creates a stack based on the new node to replicate the resource architecture from the source node. After migration, you can delete the source resources. Before deletion, ROS generates a resource management stack.

Resource detection scenario

If the relationships between resources are complex, you can create a resource detection scenario to preview the overall resource architecture or the architecture of a specific resource. For more information, see Resource detection scenario.

You can specify the resource scope by source tag, resource group, individual resource, or all resources. After you create a resource detection scenario, you can view the resource architecture. ROS retrieves the latest resource data from Resource Center and renders the resource architecture diagram on the resource scenario details page.

Terms

Term	Description
source node	When you create a resource scenario, ROS filters resources within the specified scope and generates a source node. The source node contains information about the resources, such as the resource architecture and properties. In a resource replication scenario, the source node stores information about existing resources, such as resource IDs, types, and properties. In a resource management scenario, ROS imports the resources from the source node and generates a stack for centralized management.
new node	When you create a resource replication scenario, ROS adds the required resources and generates a new node based on the source node. The new node contains information about the resources to replicate, such as resource types and properties. The properties and number of resources on the new node may differ from those on the source node. ROS may generate new resource properties suited to the scenario, such as specifications and CIDR blocks, and determines the type and number of resources based on resource dependencies and attributes. Example 1: A source node contains Elastic Compute Service (ECS) instance specifications of ecs.sn1ne.large, 2 vCPUs, and 4 GB memory. If these specifications are out of stock, ROS uses similar ECS instance specifications to generate the new node. Example 2: A source node contains only an elastic IP address (EIP) and the resources required to associate the EIP with an instance. Because an instance can be associated with only one EIP, the new node contains only the EIP and cannot contain the associated resources.

Resource types supported by resource scenarios

For more information, see Resource types that support the resource scenario feature.