Upgrading Components in Batches

After components are created and deployed, you can reconfigure and deploy multiple Running and Not ready components of the same application in rolling release mode. In rolling release mode, only one or more instances are upgraded at a time. After the upgrade is complete, the instances are added to the production environment. This process will be repeated until all old versions are upgraded to the new version. During the upgrade, services are not interrupted.

For details about how to upgrade the version configuration of a single component, see Upgrading a Single Component.

Procedure

Log in to ServiceStage.
Choose Application Management.
Click the application where the target component is located. The Overview page of the application is displayed.
Select the components to be upgraded in batches in Component List and click Bulk Upgrade.

Set the version configuration information of the components to be upgraded by referring to the following table.

Parameter	Description
Target Version	Target version of the upgraded component. Automatically-generated: Click Generate. By default, the version number is the timestamp when you click Generate. 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.1214.172318, the version number is 2022.1214.17238. 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.
Software Package/Image Package/Source Code Repository	Click and select the software package or image packagesource code repository again. For details, see Component Source.
Deployment Batches	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 Batches is set to 2, these component instances are upgraded in two batches, and each batch involves two component instances.

Parameter

Description

Target Version

Target version of the upgraded component.

Automatically-generated: Click Generate. By default, the version number is the timestamp when you click Generate. 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.1214.172318, the version number is 2022.1214.17238.
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.

Software Package/Image Package/Source Code Repository

Click and select the software package or image packagesource code repository again. For details, see Component Source.

Deployment Batches

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 Batches is set to 2, these component instances are upgraded in two batches, and each batch involves two component instances.

Click in the Operation column of a component to deselect the component to be upgraded.

Click OK.
Wait until the component status changes from Upgrading/Rolling back to Running, indicating that the component version configuration is successfully upgraded.

Follow-Up Operations

Operation	Description
Roll back a component	After the version configuration of all component instances is upgraded to the new version, if you need to roll back the component to the source version, see Rolling Back a Component.
Redeploy a component	You can select a historical version configuration from the deployment record list and use the version configuration as a template to redeploy components. For details, see Redeploying a Component.