Enterprise Distributed Application Service:Release an application in phases in the EDAS console

Log on to the EDAS console.

In the left-side navigation pane, choose Application Management > Applications.

On the Applications page, select a region in the top navigation bar and select a microservices namespace from the Microservices Namespace drop-down list. From the Cluster Type drop-down list, select ECS Clusters. Then, click the name of the application that you want to manage in the application list.

On the Basic Information page, click Deploy in the upper-right corner.

On the Select Deployment Mode page, click Start Deployment in the upper-right corner of the Regular Release (Single-batch/Multi-batch) section.

On the Regular Release (Single-batch/Multi-batch) page, specify the deployment package, configure parameters for the new version of the application, configure a release policy, and then click OK.

1. Specify the deployment package and configure parameters for the new version of the application.

   Parameter	Description
   Deployment Method	The deployment method of the application. The deployment method is selected when the application is deployed for the first time. This method cannot be changed. For example, a JAR package is used when the application is deployed for the first time. You can specify only JAR as the deployment method when you update the application. Note If you set the Deployment Method parameter to Historical Versions, the application can be rolled back to an earlier version. For more information, see Use the EDAS console to roll back applications deployed in ECS clusters.
   File Uploading Method	The method that is used to upload the deployment package of the new version. You can upload a JAR or WAR package, or specify the URL of a JAR or WAR package. The type of the deployment package depends on the deployment package that is used when you deploy the application for the first time. If you select Upload JAR Package or Upload WAR Package, click the box for file upload and upload the deployment package of the new version. If you select JAR Package Address or WAR Package Address, enter the URL of the deployment package in the field below. You must first upload the deployment package to a cloud service, such as Object Storage Service (OSS).
   Version	The new version of the application. You can enter the version number or click Use Timestamp as Version Number.
   Description	The description of the new version.

2. Configure a release policy.

   Parameter	Description
   Group	The instance group in which you want to release the application to the specified instances in phases. If the current application has only one group, select All Groups from the drop-down list. The maximum number of instances of the current application is displayed in the parenthesis next to All Groups. The drop-down list also displays Default Group, which is the same as All Groups. If the current application has multiple groups, select a group as needed. Note If you select All Groups, the application is released to all instances in all groups of the application based on the setting of the Batches per Group parameter.
   Batches per Group	The number of phases in which the application is released to the specified instances in the group. The minimum number of instances in a single phase is 1. The default value is 2 Batches. You can configure this parameter based on your business requirements.
   Batch Mode	The method that is used to perform the release of the next phase. Valid values: Automatic and Manual. Automatic: The application is automatically released in the next phase based on the setting of the Wait Time Before Next Batch parameter. Manual: The application is manually released in the next phase.
   Wait Time Before Next Batch	The interval between the release of two phases. Unit: minutes. You can select an interval from the drop-down list based on your business requirements.
   Java Environment	The Java environment for the new version of the application. Valid values include Open JDK 8, Open JDK 7, and Dragonwell 8. Configure this parameter based on your business requirements.

   Note

   After the release policy is configured, the script of the current release policy is generated in the Generate Maven Plug-in Configuration section. If you use the toolkit-maven-plugin plug-in to release the application to the specified instances in phases, you can directly use the plug-in in the script.

3. Click OK.

   After the release is started, the Change Details page appears. On the Change Details page, you can view the progress and status of the release. For more information, see View application changes.

View change records.

1. On the application details page, click Change Records in the left-side navigation pane.

2. On the Change Records page, check whether the value in the Change Status column is Success.

   • If the value is Success, the application is released.

   • If the value is Execute failed, the application fails to be released. You can click View in the Actions column to view the change details and troubleshoot issues.

View application details.

1. On the application details page, click Basic Information in the left-side navigation pane.

2. On the Basic Information page, click the Basic Information tab. In the Application Information section of the Basic Information tab, check whether the Deployment Package parameter indicates the latest deployment package.

3. On the Basic Information page, click the Instance Information tab. On the Instance Information tab, check whether the value of the Running Status parameter is Normal for each instance in the specified group.