Resource Orchestration Service (ROS) provides the resource scenario feature that allows you to specify the scope of a collection of resources on a visualized interface and perform operations, such as replication, management, migration, and detection, on the resources. This helps you manage resources in a simplified manner.
Resource replication scenario
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 generate a collection of resources that have the same architecture as the existing resources. For more information, see Resource replication scenario.
You can specify the scope of resources by source tag, resource group, or resource. When you create a resource replication scenario, ROS adds resources that are required for replication, such as the resource types and properties, to generate a new node. 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.
Resource management scenario
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 Resource management scenario.
You can specify the scope of resources by source tag, resource group, or resource. 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 use a resource management scenario to generate a template and deploy multiple resources at a time based on the template. For more information, see Generate a template based on a scenario with one click.
Resource migration scenario
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 details page. After you migrate the resources, you can delete source resources. For more information, see Resource migration scenario.
You can specify the scope of resources by source tag, resource group, or resource. When you create a resource migration scenario, ROS adds resources that are required for migration, such as the resource types and properties, to generate a new node. 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. 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 detection scenario
If the relationships between resources that you want to create are complicated, you can create a resource detection scenario to preview the overall resource architecture or the architecture of a specific resource. This facilitates resource management. For more information, see Resource detection scenario.
You can specify the scope of resources by source tag, resource group, or resource. You can also specify all resources as the scope. After a resource detection scenario is created, you can view the resource architecture. ROS obtains the latest resource data from Resource Center and renders the resource architecture diagram on the scenario details page.
Terms
Term | Description |
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.
|
new node | When 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.
|
Resource types supported by resource scenarios
For more information, see Resource types that support the scenario feature.