- What's New
- Function Overview
- Service Overview
- Getting Started
-
User Guide
- CodeArts Deploy Overview
- Purchasing and Authorizing CodeArts Deploy
- Accessing CodeArts Deploy Homepage
- Configuring the Host Cluster of CodeArts Deploy
-
Creating and Deploying an Application with a Blank Template
- Creating an Application with a Blank Template
-
Configuring Deployment Actions for an CodeArts Deploy Application
- Configuring Deployment Actions for Software Installation
-
Configuring Deployment Actions for Containers
- Deploying on Kubernetes
- Deploying an Application in Kubernetes (CCE Cluster) Using Manifest
- Deploying an Application in Kubernetes (CCE Cluster) Quickly
- Deploying an Application with a Custom Kubernetes Cluster
- Kubernetes Nginx-Ingress Grayscale Deployment (CCE Cluster)
- Deploying with Helm3
- Deploying an Application on ServiceStage 2.0
- Rolling Back ServiceStage Components
- Configure Deployment Actions for Starting or Stopping a Service
- Configuring Deployment Actions for File Operations
- Configuring Deployment Actions for Running Commands
- Configuring Other Deployment Actions
- Editing the Deployment Actions of the CodeArts Deploy Application
- Configuring Parameters of an Application
- Configuring an Environment
- Configuring Permissions for Different Roles
- Deploying an Application and Viewing the Result
- Configuring System Notifications
-
Creating and Deploying an Application Using a Preset Template
- Introduction to CodeArts Deploy Templates
- Creating and Deploying an Application Using ServiceStage
- Creating and Deploying an Application Using a Kubernetes Template
- Creating and Deploying an Application Using the Function Deployment Template
- Creating and Deploying an Application Using the Tomcat Template
- Creating and Deploying an Application Using the Spring Boot Deployment Template
- Creating and Deploying an Application Using the Docker Deployment Template (Linux)
- Creating and Deploying an Application Using the Django Template
- Creating and Deploying an Application Using the Node.js Template
- Creating and Deploying a Common Application by Running the Shell Script
- Creating and Deploying an Application Using the Go Application Deployment Template
- Creating and Deploying an Application Using the Vue Deployment Template
- Creating and Deploying an Application Using the Custom Template
- Querying Audit Logs (Optional)
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
APIs
-
Managing Host Clusters
- Creating a Host Cluster
- Querying a Host Cluster List
- Deleting a Host Cluster
- Querying a Host Cluster
- Modifying a Host Cluster
- Creating a Host Cluster (Recommended)
- Querying a Host Cluster List (Recommended)
- Querying a Host Cluster (Recommended)
- Editing a Host Cluster
- Deleting a Host Cluster (Recommended)
- Querying Information About the Environment Associated with a Host Cluster
- Querying the Basic Environment Information List of an Application
-
Managing Hosts
- Creating a Host
- Querying a Host List
- Querying Host Details
- Modifying a Host
- Deleting a Host
- Creating a Host (Recommended)
- Querying a Host List (Recommended)
- Querying Host Details (Recommended)
- Editing Host Information in a Host Cluster
- Deleting a Host from a Host Cluster
- Cloning Hosts to the Target Host Cluster in Batches
- Deleting Hosts from a Host Cluster in Batches
-
Managing Applications
- Obtaining an Application List
- Creating an Application Using a Template
- Deploying an Application
- Obtaining the Details of an Application
- Deleting an Application
- Querying the Historical Deployment Records of a Specified Application in a Project by the Start Time and End Time
- Obtaining an Application List (Recommended)
- Creating an Application (Recommended)
- Updating an Application
- Obtaining Application Details (Recommended)
- Deleting an Application (Recommended)
- Querying the Execution Parameters of a Deployment Record
- Cloning an Application
- Deleting Applications from a Project in Batches
- Checking Whether an Application with the Same Name Exists in a Project
- Disabling and Enabling an Application
- Managing Application Groups
- Managing Application Permissions
- Measuring Deployment Record
-
Managing Environments
- Creating an Environment for an Application
- Querying an Environment List of an Application
- Editing an Environment in an Application
- Deleting an Environment from an Application
- Querying Environment Details
- Importing a Host to an Environment
- Deleting a Host from an Environment
- Querying a Host List in an Environment
- Managing Host Cluster Permissions
- Managing Environment Permissions
-
Managing Host Clusters
- Application Examples
- Appendixes
-
FAQs
-
Hosts
- What Are the Troubleshooting Methods for Host and Proxy Connectivity Verification Failures
- What Should I Do If Application Deployment Fails with "tomcat | Download War in url path" Displayed in Logs?
- Why Does a Task Fail on an Ubuntu Host After Being Successfully Run on a CentOS Host?
- What Should I Do If the No Host or Environment Whose Connectivity Has Been Verified?
- What Are Possible Causes of a Host verification failure?
-
Application Deployment
- What Should I Do If a Draft Application Cannot Be Deployed?
- What Are Error Messages Displayed During Application Deployment?
- How Do I Find the Cause of an Application Deployment Error in Logs?
- What Should I Do If Error 403 Displayed During Application Deployment That Requires CCE Resources, Indicating Insufficient Permission?
- How Do I Roll Back a Deployed Version?
- What Should I Do If an Application Deployment Times Out?
- Does CodeArts Deploy Provide Batch and Incremental Deployment Policies?
- Do I Need to Upload a Software Package to CodeArts Artifact Before Deployment?
- Can I Deploy Web Pages Written in HTML or JS?
- How Do I Upload an Image for Container Deployment?
-
Common FAQs
- Can I Use a Host to Deploy Multiple Projects?
- Do I Need to Install a Running Environment (Tomcat, Python, etc.) on the Target Host Before Deploying an Application?
- What Should I Do If Application Deployment Fails, with the Message "AnsibleUndefinedVariable: 'xxxx' is undefined" Displayed?
- What Should I Do If Application Deployment Succeeds But the Application Verification URL Cannot Be Accessed?
- What Should I Do If Application Deployment Fails Due to a DNS Resolution Error?
- What Should I Do If a Draft Application Cannot Be Deployed?
- What Should I Do If JDK Has Been Installed and Environment Variables Have Been Configured, But Application Deployment Fails with the Error Message "please configure JDK environment variables" Displayed?
- What Should I Do If the Log Indicates Insufficient Permissions?
- What Should I Do If the Path Is Invalid?
- What Should I Do If the System Displays a Message Indicating That No Hosts Are Found in the Environment?
- What Should I Do If an Error Is Reported When the Sudo Permission Is Used?
- What Should I Do If the File or File Path Does Not Exist?
- What Should I Do If I Have Insufficient Permissions?
- What Should I Do If the File Path Does Not Exist?
- What Should I Do If the Action "Create and Start Container" Fails on Ubuntu 22 OS When Using Template "Deploy a Docker Application for Linux"?
- What Should I Do If the Connection Times Out Occasionally During a Deployment on a Windows Host?
-
Custom Application Actions
-
Health Test via URLs
- Incorrect URL
- URL Does Not Exist
- Invalid URL
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Selecting Deployment Sources
- Software Package Not Found in CodeArts Artifact
- No Software Package Available for a Build Task
- URL Domain Name Resolution Failure
- File Download Times Out
- Inconsistent SHA256 Values in a File
- Inconsistent MD5 Values in a File
- Error "More than 100 build files"
- "HTTP Error 403" Is Displayed When the CodeArts Artifact Software Package Is Downloaded
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Stopping a Service
- Incorrect Port Number
- Action Stop Service Deployed Successfully, But the Service Is Still in Started State
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Copying a File
- File to Be Copied Does Not Exist
- Invalid File Path
- File or File Path Does Not Exist
- Action Copy Files Deployed Successfully, But the Expected Result Is Not Achieved
- Insufficient Permissions
- Log Contains "copy File Failed" When Copying Files Between Linux Environment
- Log Contains "Windows does not support copying files between hosts" When Copying Files Between Windows Environment
- Log Contains "Hosts using secret key credit do not support copying files between" When Copying Files Between Environment
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Deleting a File
- Cannot Delete Files on a Linux Host
- File Path Does Not Exist on a Windows Host
- Incorrect File Path on a Windows Host
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Decompressing a File
- File to Be Decompressed Does Not Exist
- Backslashes (\) Are Used as Path Separators in the Native Command Compress-Archive
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Modifying a Configuration File
- File Path Does Not Exist
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Starting or Stopping Tomcat
- Invalid Tomcat Path
- Stopping Failed
- Startup Failed
- Environment Variables Are Not Configured
- Service Is Not Started Despite Successful Action Deployment
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Starting/Stopping Go Service
- The Go Service Path Is Incorrect
- Startup Failed
- Environment Variables Are Not Configured
- Deployment Is Successful, But the Service Is Not Started
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Starting or Stopping Spring Boot
- Start/Stop Spring Boot
- Invalid Spring Boot Path
- Startup Failed
- Environment Variables Are Not Configured
- Service Is Not Started Despite Successful Action Deployment
- Spring Boot Can Still Be Detected After Being Stopped (on Windows)
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Starting or Stopping Nginx
- Nginx Gets Restarted Repeatedly
- Invalid Windows Host Path
- Deploying the Command for Stopping Nginx When Nginx Is Not Started
- Incorrect Format of the Nginx Configuration File
- Configuration File Backup Path Does Not Exist
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Deployment Blocked by Third-Party Antivirus Software
- Starting or Stopping IIS
-
Starting or Stopping Node.js
- Node.js Fails to Be Started or Stopped on a Linux Host
- Node.js Fails to Be Started or Stopped on a Windows Host
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Running Shell Commands
- A Message Indicating an Operation Failure Is Displayed During Action Run Shell Commands Deployment
- Service Is Not Started But the Log Shows That Shell Commands Are Successfully Executed
- Unidentified Shell Commands Are Used
- Shell Command References a File or Folder That Does Not Exist
- How Does a Shell Command Reference Parameters?
- Deployment of the Action Run Shell Commands Times Out
- Interactive Shell Commands Are Used
- Shell Command Deployment Times Out After the su Command Is Executed to Switch the User
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
- Other FAQs
-
Running Shell Scripts
- Running Shell Scripts Failed
- Deployment Is Successful But Does Not Achieve the Expected Result
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Running PowerShell Commands
- Deployment of the Action Run PowerShell Commands Times Out
- Unidentified PowerShell Commands Are Used
- PowerShell Command References a File or Folder That Does Not Exist
- How Does a PowerShell Command Reference Parameters?
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
-
Running PowerShell Scripts
- Running PowerShell Scripts Failed
- Deployment Is Successful But Does Not Achieve the Expected Result
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
-
Running Docker Commands
- Docker Not Installed
- Docker Command Parameter Error
- No Deployment Permissions
- Image Does Not Exist
- login Command Execution Failed
- build Command Execution Failed
- tag Command Execution Failed
- push Command Execution Failed
- run Command Execution Failed
- start, restart, stop, or rm Command Execution Failed
- rmi Command Execution Failed
- pull Command Execution Failed
- rm Command Execution Failed
- Connection Timed Out
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Pending Execution
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
- FAQs About ServiceStage
-
FAQs About Kubernetes Deployment Tasks
- Parameter Referenced by {{}} in the Manifest File Is Not Defined in the Application
- Target File Does Not Exist in CodeArts Artifact
- Path of the Manifest File in CodeArts Artifact Is Incorrect
- kubeconfig File Is Incorrectly Configured
- kubectl Command Fails to Be Deployed
- Failed to Deploy Applications on Kubernetes
- Log Contains "Too many files to unzip" When CodeArts Repo Is Selected as the Manifest File Source During Kubernetes Deployment
- Error Message "File is too large" Displayed During Manifest File Source Selection for Kubernetes Deployment
-
Ansible
- Invalid Entry File Path
- Entry File Not Found
- Copy Module Error
- JSON Parameter Parsing Error
- Service Module in Playbook Scripts Fails to Start or Stop Services
- Ansible Application Deployment Fails
- What Should I Do When the "Do not use the delegate_to, connection, hosts command in the Ansible PlayBook script for executing the local computer" message Is displayed When Running Ansible?
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Creating an IIS Site
- Incorrect Port Number
- Physical Path of an Application Does Not Exist
- IIS Not Installed on the Host
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- How Do I Check the IIS Function on the Local Host?
- Installing IIS
-
Installing JDK
- A JDK of the Same Version Already Exists on the Target Host
- Java Not Installed on the Target Host
- JDK Decompression Failed
- Cannot Install OpenJDK 8 on Ubuntu 14 or Earlier Versions
- The Deployment Result Is "Openjdk does not support arm"
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Software Version Detected on Windows Host Does Not Match the Installed Version
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Installing Tomcat
- Deployment Failed
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Installing Nginx
- No sudo Permissions
- No Permission to Access the Path
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Software Version Detected on Windows Host Does Not Match the Installed Version
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Installing Go
- Invalid Installation Path
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Software Version Detected on Windows Host Does Not Match the Installed Version
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Installing PHP
- Error Returned When Installing PHP as a Common User
- Some Dependency Packages Do Not Exist in the CentOS Yum Repository
- Download Fails Due to Network Disconnection from the CentOS Yum Source
- Download Fails Because Some Software Dependency Packages Are Missing for apt-get in Ubuntu
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Software Version Detected on Windows Host Does Not Match the Installed Version
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Installing Node.js
- Cannot Decompress Node Packages
- Installation Path Fails to Be Created
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Software Version Detected on Windows Host Does Not Match the Installed Version
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Installing Python
- No sudo Permissions
- No Permission to Access the Path
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Software Version Detected on Windows Host Does Not Match the Installed Version
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
-
Installing/Uninstalling Docker
- Error Returned During the Deployment of the Action for Installing or Uninstalling Docker as a Common User
- Error Returned Even Though the Action for Installing or Uninstalling Docker Is Successfully Deployed
- Application Deployment Interruption
- Insufficient Permissions
- Parameters Contain Backslashes (\)
- No Host Exists in the Environment
- Environment Does Not Exist
- Failed to Deploy an Application on a Windows Host
- Error Occurs During Application Deployment with the sudo Privileges
- Deployment Blocked by Third-Party Antivirus Software
- Invalid Path
- A Network Error Occurs During Software Installation on CentOS
- A Network Error Occurs During Software Installation on Ubuntu OS
- Windows Path Not Allowed on a Linux Host
- Grayscale Release with Istio
-
Health Test via URLs
-
Hosts
- Videos
- General Reference
Copied.
Deploying an Application on an Intranet Host Using a Proxy Host
Application Scenario
Deploy applications on the intranet through proxy hosts to effectively control intranet and extranet communication, enhance data security and network performance, and meet compliance requirements. This policy is widely used in various key scenarios, such as resource access control, secure communication between data centers, content cache acceleration, environment isolation, security audit, and sensitive data processing.
Solution Architecture
The Internet forward proxy function of Squid is used to specify the IP address and port of the target host on the proxy, enabling the target host to access the public network.
For more information about Squid, go to Squid official website. The following procedure uses a Linux host as an example.
Prerequisites
- A host (Proxy-B) bound to a public IP address is available. If no proxy host is available, see Applying for an ECS.
- A host (Host-A) not bound to a public IP address is available.
- Proxy-B and Host-A can access each other through the intranet.
Process
This section describes how to deploy an application on an intranet host or server using a proxy host.

- Install Squid.
Access the command line tool of Proxy-B and run the following command:
yum install squid -y
If Complete is displayed, run the following command:
yum install iptables-services
Enter Y. If Complete is displayed, the installation is complete.
- Edit the Squid configuration file.
- Access the command line tool of Proxy-B and run the following command:
vim /etc/squid/squid.conf
- Add the following command to the position marked in the red box in the preceding figure:
acl local src Internal IP address of the host/24
- Press Esc and enter :wq to save the file and exit.
- Access the command line tool of Proxy-B and run the following command:
- Configure the firewall of Proxy-B.
Access the command line tool of Proxy-B and run the following commands in sequence:
systemctl stop firewalld.service
systemctl disable firewalld.service
yum install iptables-services iptables-devel -y
systemctl enable iptables.service
systemctl start iptables.service
iptables -I INPUT 1 -s Internal IP address of the host/24 -p tcp --dport 3128 -j ACCEPT
iptables -I INPUT 2 -p tcp --dport 3128 -j DROP
NOTE:
The IP address in the last but one line must be set to the internal IP address segment or IP address of Host-A. 3128 is the proxy port of Squid.
- Install OpenSSL.
Access the command line tool of Proxy-B and run the following command:
yum install openssl
If Complete is displayed, the installation is complete.
- Start Squid.
Access the command line tool of Proxy-B and run the following command:
systemctl start squid //Start Squid.
systemctl status squid //Check the status of Squid.
- Configure the forward proxy.
Access the command line tool of Host-A and run the following command:
echo "export http_proxy=http://Internal IP address of the proxy host:3128" >>/etc/profile echo "export https_proxy=http://Internal IP address of the proxy host:3128" >>/etc/profile echo "export http_proxy=http://Internal IP address of the proxy host:3128" >>~/.bashrc echo "export https_proxy=http://Internal IP address of the proxy host:3128" >>~/.bashrc echo "export http_proxy=http://Internal IP address of the proxy host:3128" >>~/.bash_profile echo "export https_proxy=http://Internal IP address of the proxy host:3128" >>~/.bash_profile source /etc/profile source ~/.bashrc source ~/.bash_profile
- Create basic resources.
- Click Homepage to view all created projects, and then go to the target project.
- Choose Settings > General > Basic Resources. The Host Clusters page is displayed by default.
NOTE:
Choose CICD > Deploy. Click Basic Resources. The Host Clusters page is displayed by default.
- Click Create Host Cluster, enter the following information, and click Save.
Parameter
Mandatory
Description
Cluster Name
Yes
Enter a custom name.
OS
Yes
Select Linux based on the OS of the host to be added.
Host Connection Mode
Yes
Select Proxy.
Execution Resource Pool
Yes
A resource pool is a collection of physical environments where commands are executed during software package deployment. In this scenario, select official.
Description
No
Enter a description.
- Click Add Host, select Adding IP for Add hosts by, enter the following information, and click OK. The proxy host is created.
Table 1 Parameters of a Linux proxy host Parameter
Mandatory
Description
Host Name
Yes
Enter a custom name, for example, Proxy-B.
IP
Yes
Enter the public IP address bound to Proxy-B.
OS
Yes
Keep the default value because it is the OS of your host cluster.
Authorization
Yes
In this scenario, the Password is used for authentication. Enter the username and password of Proxy-B.
SSH Port
Yes
Port 22 is recommended.
- Click Add Host, select Adding IP for Add hosts by, enter the following information, and click OK. The target host is created.
Table 2 Parameters of a Linux target host Parameter
Mandatory
Description
Host Name
Yes
Enter a custom name, for example, Host-A.
Proxy Host
Yes
Select Proxy-B as the network proxy for the target host that cannot connect to the public network.
IP
Yes
Enter the private IP address of Host-A.
OS
Yes
Keep the default value because it is the OS of your host cluster.
Authorization
Yes
In this scenario, the Password is used for authentication. Enter the username and password of Host-A.
SSH Port
Yes
Port 22 is recommended.
- Click
in the Operation column of a host to start the host for connectivity verification.
- Create an application.
- Log in to the CodeArts homepage and click the target project name to access the project.
- Choose CICD > Deploy.
- Click Create Application. On the Set Basic Information page, modify the basic information such as Name, Description, and Execution Host as required.
- After editing the basic application information, click Next. On the deployment template selection page, select Blank Template and click OK.
- On the Deployment Actions tab page, find the action list on the right, click Add to add an action to the orchestration area on the left.
- On the Environment Management page, click Create Environment, enter the basic information, and click Save.
- Click Import Host. The system automatically filters all clusters that meet the requirements of the current environment. In the dialog box that is displayed, select the target host cluster and import Proxy-B and Host-A to the environment.
- Deploy the application. For details, see Deploying an Application and Viewing the Result.
- Select the target application in the application list and click
.
- After the deployment is complete, click the application name and click the target deployment record. The application status bar changes to green and the message Successful is displayed, indicating that the application is successfully deployed.
- Select the target application in the application list and click
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot