Help Center/ CodeArts Deploy/ User Guide/ Configuring the Host Cluster of CodeArts Deploy/ Creating a Host Cluster for CodeArts Deploy/ Creating a Host Cluster: Overview of Host Connection Modes
Updated on 2024-09-04 GMT+08:00
View PDF
Share

Creating a Host Cluster: Overview of Host Connection Modes

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

A target host is the final deployment object. CodeArts Deploy deploys your resources such as artifacts to the target host in the environment.

A proxy server is a computer used to provide access channels for other target hosts without public IP addresses. In CodeArts Deploy, proxy hosts are usually referred to as ECSs bound to public IP addresses unless otherwise specified.

Overview of Host Connection Modes

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 an official resource pool, CodeArts Deploy allows you to connect your host to the platform to form a self-hosted resource pool. This service supports direct host connection and proxy mode to connect the resource pool to the target host. Before executing an application, ensure that the resource pool can communicate with target hosts. This process is called host connectivity verification.

Direct Host Connection

Direct host 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 the target host 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.

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 the target host and proxy host 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.

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

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