When you release a new version of an application deployed in an Enterprise Distributed Application Service (EDAS) Elastic Compute Service (ECS) cluster, you can use the regular release mode to roll out the update in a single batch or multiple batches. This approach lets you control the rollout pace and reduce risk by updating instance groups incrementally.
Prerequisites
Before you begin, make sure that you have:
An application deployed in an ECS cluster on EDAS
The deployment package (JAR or WAR) for the new version, or a URL where the package is hosted (such as Object Storage Service (OSS))
The deployment method is locked to the package type used during the first deployment. For example, if you deployed with a JAR package initially, you can only use JAR packages for subsequent updates.
Update an application by using regular release
Log on to the EDAS console.
In the left-side navigation pane, choose Application Management > Applications.
On the Applications page, select a region and a microservices namespace, and then set the Cluster Type drop-down list to ECS Clusters.
Click the name of the application that you want to update.
On the Basic Information page, click Deploy in the upper-right corner.
On the Select Deployment Mode page, find the Regular Release (Single-batch/Multi-batch) section and click Start Deployment.
On the Regular Release (Single-batch/Multi-batch) page, configure the deployment package and release policy, and then click OK.
Deployment package parameters
| Parameter | Description |
|---|---|
| Deployment Method | The package type for deployment, determined during the initial deployment. This setting cannot be changed. To roll back to a previous version, select Historical Versions. For more information, see Use the EDAS console to roll back applications deployed in ECS clusters. |
| File Uploading Method | Specifies how to provide the new deployment package. The available options depend on the package type:
|
| Version | The version number for this release. Enter a version number manually or click Use Timestamp as Version Number to generate one automatically. |
| Description | A description for this version. |
Release policy parameters
| Parameter | Description |
|---|---|
| Group | The instance group to update.
|
| Batches per Group | The number of batches to roll out the update within each group. Set this to 1 Batches for a single-batch release. For multi-batch releases, set a higher value to update instances incrementally. |
| Batch Mode | The execution mode for multi-batch releases. When Batches per Group is set to 1 Batches, this defaults to Automatic. |
| Java Environment | The Java runtime for the application. Valid values: Open JDK 8, Open JDK 7, and Dragonwell 8. |
After the release starts, the Change Details page opens and displays the release progress and status. For more information, see View application changes.
Verify the result
After the release completes, verify the update by checking the change records and instance status.
Check change records
On the application details page, click Change Records in the left-side navigation pane.
In the Change Status column, check the status of the release:
Success: The application was updated.
Execute failed: The update failed. Click View in the Actions column to see the change details and troubleshoot the issue.
Check the deployment package and instance status
On the application details page, click Basic Information in the left-side navigation pane.
On the Basic Information tab, find the Application Information section and confirm that the Deployment Package field shows the latest package.
Click the Instance Information tab and confirm that the Running Status of each instance in the target group is Normal.
Roll back to a previous version
If the update causes issues, you can roll back by selecting Historical Versions as the Deployment Method and redeploying. For the full rollback procedure, see Use the EDAS console to roll back applications deployed in ECS clusters.