In service rollout and upgrade scenarios, the stability of the deployment process and application is extremely important. This document describes how to use batch deployment to ensure deployment stability when the application is deployed again.
The batch deployment feature allows you to deploy applications in multiple batches. Each batch updates only a part of the running instances of an application. In addition, you can suspend manual verification and rollback to avoid the impact of faults and the fluctuations in the deployment process.
You have created and deployed an application.
- Log in to the TEM console and click Application Management in the left sidebar to go to the application list page.
- Select the target application and click the application ID to go to the application details page.
- On the application details page, click Deploy to go to the redeployment details page.
- On the deployment details page, configure batch deployment in the Deployment Policy area.
- If your application has more than one running instance, redeployment automatically triggers batch deployment.
- Trial Batch: you can specify a trial batch that contains no more than 50% of the total number of instances. After the execution of the trial batch is completed, you need to manually start the remaining batches.
- Deployment Batches: select the number of batches to launch. Then all instances will be evenly distributed across batches.
- How to trigger: you can choose either to manually or automatically (at an interval of 5 minutes) start the next batch.
- Deployment flowchart: you can expand the flowchart to view the deployment process and batch details.
- Click Deploy to redirect to the Instance List page to start deployment.
- Click View Details in the Status parameter in the Application Overview area. You can view and manage the batch deployment process in the deployment list.
Rollback is to terminate the current deployment process and restore all instances to their previous versions.