All Products
Search
Document Center

Resource Orchestration Service:Step 4: (Optional) Create stack instances

Last Updated:Jan 02, 2024

If you want to use the template of an existing stack group to deploy stacks in different regions within specific accounts of your resource directory, you can create stack instances in the stack group. This way, stacks that correspond to the stack instances are automatically deployed in the regions within the accounts. If you specify members in a resource directory and regions when you create a stack group, stack instances are automatically created in the regions within the members in the Resource Orchestration Service (ROS) console.

Procedure

  1. Log on to the ROS console by using the management account or a delegated administrator account in your resource directory.

    Note

    The logon account must be the same as the account within which you create the stack group.

  2. In the left-side navigation pane, click Stack Groups.

  3. In the top navigation bar, select the region where the stack group you want to manage resides from the region drop-down list.

  4. On the Stack Groups page, click the name of the stack group.

  5. In the upper-right corner of the page that appears, choose 1 > Create Stack Instance.

  6. In the Set Deployment Options step, configure the following parameters and click Next.

    Parameter

    Description

    Resource Directories

    The resource directories in which you select folders to deploy stacks within all members in the folders.

    If you select Root, ROS creates stack instances within all members in the resource directory.

    Regions

    The regions where you want to deploy stacks.

    Maximum Number of Concurrent Accounts

    The maximum number of accounts within which stacks are deployed at the same time in each region.

    For more information about how to specify the value, see Overview.

    Fault Tolerance

    The number of accounts within which stack operation failures are allowed in each region. If the value of this parameter is exceeded in a region, ROS stops the operation in the region. If the operation is stopped in one region, the operation is no longer performed in other regions.

    For more information about how to specify the value, see Overview.

    Region Concurrency

    The mode that you want to use to deploy stack instances across regions.

    • Sequential: deploys stack instances in each specified region based on the specified sequence of regions. ROS deploys stack instances in one region at a time.

    • Parallel: deploys stack instances in parallel in all specified regions.

    Whether to Expand Modules in Current Account

    This parameter takes effect only when modules are used in the template. If you want to expand modules within the current account, the modules must exist in the current account. If you want to expand modules within execution accounts, the modules must exist in the execution accounts.

  7. In the Specify Override Settings step, select the parameters that you want to override, use one of the following methods to reset the parameter values, and then click Next.

    • Method 1: Choose Edit Override Value > Override Stack Group Parameter Values to reset the parameter values.

    • Method 2: Choose Edit Override Value > Reset Override Field to reset the parameter values.

    Note

    After the stack instances are created, you can perform the following operations to view the reset parameter values: Log on to the ROS console with the execution account. On the Stacks page, click the ID of the stack for which you want to view the parameter values. On the Parameters tab, view the parameter values.

  8. In the Check and Confirm step, check that the stack instance parameters are valid and click Add.

Check the result

After the stack instances are created, you can perform the following operations to view the status of the stack instances that you create within the members: On the Stack Groups page, click the name of the stack group in which the stack instances are created. On the Instances tab, view the status of the stack instances.

When stacks are being deployed, the stack instances are in the Expired state. After stacks are deployed, the stack instances enter the Current state. In this case, you can log on to the ROS console by using the members to view the stacks in the specified regions. For more information, see Use a member to log on to the Alibaba Cloud Management Console.

References