Overview

Updated on 2025-02-08 GMT+08:00

View PDF

Through basic resource management, CodeArts Deploy hosts your applications to be deployed. It deploys your artifacts (application software packages to be deployed) on an environment consisting of one or more VMs (target hosts).

Target Host

Final object for host deployment. CodeArts Deploy deploys your resources such as artifacts to target hosts in an environment.

Proxy Host

Provides access channels for other target hosts that do not have public IP addresses. In CodeArts Deploy, proxy hosts are basically ECSs bound to public IP addresses unless otherwise specified.

Host Connection Mode

In the host deployment scenario, the execution host of CodeArts Deploy communicates with the target host through SSH/WSMan to deploy applications. An execution host is also called a resource pool where the deployment is physically executed. In addition to the official resource pool, CodeArts Deploy allows you to connect your own hosts to form a self-hosted resource pool. It supports host connection mode and proxy mode to connect resource pools to target hosts. Before deploying an application, ensure that the resource pool can communicate with target hosts. This process is called host connectivity verification.

NOTE:

Only specific users at the Mexico site can use self-hosted resource pools.

Direct Connection

Direct Connection is suitable when EIP resources are abundant or only a few EIPs are required for project demo verification.

NOTE:

To ensure successful host connectivity verification, configure target hosts and enable the corresponding port.

EIPs are bound to servers for connecting official resource pools with the target hosts, as shown in the following figure.

Click to enlarge

Proxy

Proxy is suitable when there are no sufficient EIP resources and deployment on ECSs without EIPs is required.

NOTE:

To ensure successful host connectivity verification, configure target hosts and proxy hosts, and enable the corresponding port.

Linux proxy:
Use an ECS bound with an EIP as a proxy. During the deployment, the executed commands will be delivered to the proxy and forwarded to each target host through SSH. The hosts will be deployed in batches.

When executing a deployment application, the target host accesses the NAT gateway to pull the software package, as shown in the following figure.
NOTE:
- Red indicates the process of delivering deployment commands.
- Green indicates the process of pulling software packages.
Windows proxy:
Use an ECS bound with an EIP as a proxy. During the deployment, the executed commands will be delivered to the proxy and forwarded to each target host through ports. The hosts will be deployed in batches.

Parent topic: Creating a Host Cluster for CodeArts Deploy

Previous topic: Creating a Host Cluster for CodeArts Deploy

Next topic: Creating and Editing a Host Cluster

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot