Overview

With basic resource management, you can manage the deployment objects of applications to be deployed on hosts. CodeArts Deploy deploys your artifacts (the application software packages to be deployed) to the environment consisting of one or more VMs (that is, target hosts).

Host clusters can be used to host your basic resources such as hosts. You can import the created resources to an application for deployment.

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.

Direct Connection

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

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

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

Proxy

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

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

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.
- 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.