Step 6: Deploying an Application (CCE)

Updated on 2024-11-18 GMT+08:00

View PDF

CodeArts Deploy provides visualized and automated deployment. Various deployment actions are provided to help you formulate a standard deployment process, reducing deployment costs and improving release efficiency.

To deliver software more quickly and stably, the development team needs some self-service deployment service capabilities to reduce subsequent maintenance workload.

This section describes how Chris deploys a release package on CCE. For details about ECS-based deployment, see Step 6: Deploying an Application (ECS).

Preset Applications

There are three deployment applications preset in the sample project.

**Table 1** Preset applications
Preset Application	Description
phoenix-cd-cce	Application deployed on CCE
phoenix-sample-standalone	Application deployed on ECS
phoenix-sample-predeploy	Application for which you install dependency tools on ECS

This section uses the phoenix-cd-cce application as an example.

Buying and Configuring CCE

This section uses Cloud Container Engine (CCE) for deployment.

Buy a CCE cluster on the console.

For details about the mandatory configurations of clusters and nodes, see Table 2 and Table 3. You can select the configurations that are not listed in the table based on the site requirements.

**Table 2** Buying a CCE cluster
Category	Configuration Item	Suggestion
Basic Settings	Type	Select CCE Standard Cluster.
	Billing Mode	Select Pay-per-use.
	Cluster Name	Enter a name.
	Cluster Version	Select a version as required. You are advised to select the latest version.
Network Settings	Network Model	Select Tunnel network.
	VPC	Select an existing VPC. If no proper VPC is available in the list, click Create VPC.
	Default Node Subnet	Select an existing subnet. If no proper subnet is available in the list, click Create Subnet.
	Container CIDR Block	Click Auto select.

**Table 3** Configuring a node
Category	Configuration Item	Suggestion
Node Configuration	Billing Mode	Select Pay-per-use.
	Node Type	Select Elastic Cloud Server (VM).
	Specifications	Select 2 vCPUs and 8 GiB memory or higher.
	OS	Click Public image and select an Euler image.
	Node Name	Enter a custom name.
	Login Mode	Select Password.
	Password	Enter a password.
Network Settings	Node IP	Select Automatic.
Network Settings	EIP	Select Auto create.

Configuring and Executing an Application

Deploy the .yaml files generated in Step 5: Building an Application in the CCE cluster one by one.

Configure the application.

Go to the Phoenix Mall project and choose CICD > Deploy. The built-in deployment applications of the sample project are displayed on the page.
Find application phoenix-cd-cce. Click and choose Edit.

On the Deployment Actions tab page, complete the following configurations in each action.

**Table 4** Configuring deployment actions
Configuration Item	Suggestion
Cluster Name	Use the cluster name set when buying a CCE cluster.
Namespace	In this document, select default.

Click the Parameters tab and set parameters.

**Table 5** Parameters
Parameter	Example Value
ci_task_name	Enter phoenix-sample-ci.
version	Use the value of version of the phoenix-sample-ci task.

Click Save.

Click Console on the navigation bar, and access CCE from the service list.

Locate the target cluster and click its name to go to the Overview page.

Choose Workloads from the navigation pane, click the Deployments tab, and verify that no record exists in the list.

If there are records in the list, select all records, click Delete, select all resource release options, and click Yes to clear the records in the list.
Return to the application list page, click in the row of the phoenix-cd-cce application, and click OK in the dialog box that is displayed to start deployment.

If is displayed on the page, the deployment is successful. If the deployment fails, rectify the fault based on the failed action and the error information in logs.

Verify the deployment result.

Go to the CCE console.
Locate the target cluster, click its name to go to the Overview page, and click the Deployments tab.
Five records are displayed on the page. All of them are in the Running state.

Click vote to go to the details page. On the Access Mode tab page, choose More > Update.

Set the parameters by referring to Table 6, and click OK.

**Table 6** Updating a service
Parameter	Example Value
Service Affinity	Select Cluster-level.
Load Balancer	Choose Shared > Auto create. Instance Name: Enter phoenix. EIP: Select Auto create. NOTE: If your account already has a load balancer, choose Shared > Use existing and select an existing load balancer.
Port	Container Port: Set it to 80. Service Port: Set it to 5000.

After the update is successful, return to the service list. Hover over the load balancer name of , and copy the public IP address.
Figure 1 Copying the access address
Open a new browser and enter http://IP:5000 in the address box. IP is the public IP address recorded in 4.d. The Phoenix Mall homepage is displayed.
Return to the Deployments page and update result (select phoenix created in 4.c as the load balancer and enter service port 5001) by referring to 4.c.
After the creation is successful, enter http://IP:5001 in a new browser. The dashboard of Phoenix Mall is displayed.