Help Center/ ServiceStage/ Best Practices/ Using ServiceStage to Migrate Components Across AZs and Upgrade Components in Sequence Based on Release Management/ Using a Release Task to Migrate Components Across AZs
Updated on 2025-07-09 GMT+08:00
View PDF
Share

Using a Release Task to Migrate Components Across AZs

This section describes how to use batch clone of ServiceStage release management to migrate the components that have been deployed in cce-az1 in az1 when Deploying a Component to a CCE Cluster to cce-az2 in az2.

Procedure

  1. Log in to ServiceStage.
  2. Choose Release Management.

    • If the Release Management page of the old version is displayed by default, go to 4.

    • If the Release Management page of the new version is displayed by default, go to 3.

  3. Click Old Edition to switch to the Release Management page of the old version.
  4. Click Create Release Task.
  5. Enter a release task name, for example, release-clone.
  6. Select Bulk Clone for Operation Type.
  7. Click Add Component.
  8. Select the component that has been successfully deployed in Deploying a Component to a CCE Cluster and click OK.
  9. Modify the component configuration information by referring to the following table.

    Parameter

    Description

    Component Name

    Enter a component name.

    It is recommended that the component name should contain the AZ information of the CCE cluster where the component is located, for example, test-comp-az2.

    Cluster

    Select a CCE cluster (for example, cce-az2) that is in a different AZ from the cluster in Deploying a Component to a CCE Cluster.

  10. Click Complete and Execute and wait until the release task is executed.

    After the release task is executed, the component is cloned and deployed in another cluster.