Creating a Batch Upgrade Release Task

Prerequisites

You have created and deployed the components to be upgraded in batches. For details, see Creating and Deploying a Component.

Creating a Batch Upgrade Release Task

1. Log in to ServiceStage.
2. Choose Release Management > Create Release Task.
3. Configure the release task by referring to the following table. Parameters marked with an asterisk (*) are mandatory.

   Parameter	Description
   *Release Task	Name of a release task. Enter 2 to 64 characters. Start with a letter and end with a letter or digit. Only use letters, digits, underscores (_), and hyphens (-).
   Description	Description of a release task. Enter up to 128 characters.

4. Select Bulk Upgrade for Operation Type.
5. Set Best Effort Policy.

   Click to enable Best Effort Policy. If a component fails to be released, continue to release other components.

6. Click Add Component.
7. Select the components to be added to the release task and click OK.
   

   • A maximum of 64 components can be added to a batch upgrade release task.
   • Only container-deployed components whose status is Running, Not ready, Stopped, Unknown, or Abnormal can be selected.

8. Reset the version configurations of each component by referring to the following table.

   Parameter	Description
   Component Version	Version number of a component. By default, the version number is the time when you finish 7. The format is yyyy.mmdd.hhmms, where s is the ones place of the second in the timestamp. For example, if the timestamp is 2022.0803.104321, the version number is 2022.0803.10431. You can also customize the version number in the format of A.B.C, or A.B.C.D. A. B, C, and D are natural numbers, for example, 1.0.0 or 1.0.0.0. NOTICE: The customized version number must be unique and cannot be the same as any historical version number of the component. Otherwise, the current deployment record will overwrite the historical deployment record of the same version.
   Image Package	Click . Select the component source again. For details, see Component Source. You can customize a container name. The name contains 1 to 63 characters starting with a lowercase letter and ending with a lowercase letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed.
   Deployment Batch	Number of batches in which component instances are upgraded. The value range is [1, Total number of instances]. Total number of instances refers to the number of running instances of the component. For example, if there are 4 component instances and Deployment Batch is set to 2, these component instances are upgraded in two batches, and each batch involves two component instances.
   Deployment Sequence	Set the deployment sequence of all components to be added to the release task. If the selected components depend on each other, for example, the startup of a component depends on other components, set Deployment Sequence so that the depended components are deployed first. For example, for components A, B, and C to be added to the release task, the startup of component A depends on components B and C. Therefore, set Deployment Sequence of components B and C to 1, and set Deployment Sequence of component A to 2. If the components do not depend on each other, retain the default value of Deployment Sequence. All components will be deployed in the same batch.

9. Click Advanced Settings in the Operation column of the target component, set the following parameters, and click OK.
   • Set Cloud Service Settings by referring to Managing Cloud Service Settings of a Container-Deployed Component.
   • Set Container Settings by referring to Managing Container Settings of a Container-Deployed Component.
   • Set Advanced Settings by referring to Managing Advanced Settings of a Container-Deployed Component.

10. Perform subsequent operations based on whether to release the release task by referring to the following table.

    Release or Not	Operation
    Yes	Click Complete and Execute. The system automatically checks whether the advanced settings of each component are correct. If an error is reported, perform the following operations and then continue: In the displayed dialog box, confirm the information and click OK. Click Advanced Settings in the Operation column of the component for which the error is reported. Reset the advanced settings of the component based on the error information by referring to Managing Cloud Service Settings of a Container-Deployed Component to Managing Advanced Settings of a Container-Deployed Component. If the advanced settings pass the pre-check, the components in the release task will be deployed in batches as configured. You can view the release records and release task information, and Rolling Back a Released Batch Upgrade Release Task, Cloning a Batch Upgrade Release Task, and Deleting a Release Task.
    No	Click Finish. The system automatically checks whether the advanced settings of each component are correct. If an error is reported, perform the following operations and then continue: In the displayed dialog box, confirm the information and click OK. Click Advanced Settings in the Operation column of the component for which the error is reported. Reset the advanced settings of the component based on the error information by referring to Managing Cloud Service Settings of a Container-Deployed Component to Managing Advanced Settings of a Container-Deployed Component. If the advanced settings pass the pre-check, a release task in the To release state will be generated. On the Release Management page, you can view release task information, and Releasing a Release Task, Cloning a Batch Upgrade Release Task, Editing a Batch Upgrade Release Task, and Deleting a Release Task.