Creating a Batch Upgrade Release Task

Create a batch upgrade release task to upgrade the version configurations of multiple components at the same time.

Prerequisites

You have created and deployed the components to be added to the batch upgrade release task. For details, see Creating and Deploying a Component.

Creating a Batch Upgrade Release Task

Log in to ServiceStage.
Choose Release Management.
- If the Release Management page of the old version is displayed by default, go to 4.
  Overview describes release management of the old version.
- If the Release Management page of the new version is displayed by default, go to 3.
  Overview describes release management of the new version.
Click Old Edition to switch to the Release Management page of the old version.

The data of the old and new versions are isolated. Switching them will not cause release task data loss.
Click Create Release Task.

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.

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.

Select Bulk Upgrade for Operation Type.
Set Best Effort Policy.
- Enable it to continue releasing other components when a component fails to be released.
- If it is disabled, the release task fails when a component fails to be released.
Click Add Component.
Select the components to be added to the release task and click OK.

A batch upgrade release task supports up to 64 components in the Running, Not ready, Unknown, or Abnormal state. For details about how to check the component status, see Viewing Component Details.

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 9. 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. 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.
Software Package/Image Package/Source Code Repository	Click and select another package type. For details, see Component Source. If you select an image package for a container-deployed component: If Multi-container is selected in Creating and Deploying a Component, select a container and click to specify it as the initialization container for installing tools or scripts before the service container starts. At least one container must be specified as the service container (non-initialization container). For details about container initialization, see Init Containers. You can customize the container name. The name contains 1 to 63 characters, including lowercase letters, digits, and hyphens (-), and must start with a lowercase letter and end with a lowercase letter or digit. Click in the upper right corner of the selected container to change the container image package source. If you select a software package for a container-deployed component, you can customize the container name. The name contains 1 to 63 characters, including lowercase letters, digits, and hyphens (-), and must start with a lowercase letter and end with a lowercase letter or digit. If the package type is software package and you need to use JFrog (example) as the software package repository, you can select Custom file address. Enter the HTTP/HTTPS custom file address where the software package is located. Determine whether to enable authentication. If authentication is disabled, any user can download the software package in the custom file address by default. Click to enable authentication. Only authenticated users can download the software package in the custom file address. Authentication mode can be User name and password authentication or User-defined Header Authentication. The authentication mode and the corresponding authentication parameters are determined by the authentication mode supported by the server where the custom file directory is located. Set Image Access Credential. You can select up to 16 image access credentials. Click Create Secret to create an image access credential. Secret Type must be kubernetes.io/dockerconfigjson. For details, see Creating a Secret. An image access credential is a secret, which is used to store the authentication information required for pulling images from a private repository. For a public repository image, you can retain the default settings or do not set this parameter. For a private repository image, this parameter is mandatory. Otherwise, the image fails to be pulled.
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. For container-deployed components, you can reset this parameter when Configuring a Component Upgrade Policy in 11.
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.

Click Advanced Settings in the Operation column of the target component, set advanced settings, and click OK.
- Select a component technology stack and version. For details, see Technology Stack.
- For container-deployed components, set other parameters by referring to Managing Cloud Service Settings of a Component to Managing Advanced Settings of a Container-Deployed Component.
- For VM-deployed components:
  - Set other parameters by referring to Managing Cloud Service Settings of a Component and Managing VM-Deployed Component Configurations.
  - Select Upgrade Policy and set Pause Before Stop.
    The Rx traffic will be processed during this period of time. The unit is second and the value ranges from 0 to 600.

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 abnormal component and set the parameter by referring to 11. If the advanced settings pass the pre-check, the components in the release task will be deployed in batches as configured. During the release task release, if the component configuration is incorrect, you can click Suspend to stop the release. Then, click Clone, reconfigure the component, and release the release task again by referring to Cloning a Batch Upgrade Release Task. 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 abnormal component and set the parameter by referring to 11. 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.

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:
1. In the displayed dialog box, confirm the information and click OK.
2. Click Advanced Settings in the Operation column of the abnormal component and set the parameter by referring to 11.
If the advanced settings pass the pre-check, the components in the release task will be deployed in batches as configured.
- During the release task release, if the component configuration is incorrect, you can click Suspend to stop the release. Then, click Clone, reconfigure the component, and release the release task again by referring to Cloning a Batch Upgrade Release Task.
- 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.

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:
1. In the displayed dialog box, confirm the information and click OK.
2. Click Advanced Settings in the Operation column of the abnormal component and set the parameter by referring to 11.
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.