El contenido no se encuentra disponible en el idioma seleccionado. Estamos trabajando continuamente para agregar más idiomas. Gracias por su apoyo.
- 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 ECS
Purchasing and Configuring an ECS
This section uses Elastic Cloud Server (ECS). You can also use your own Linux host that runs Ubuntu 16.04 OS.
- Buy an ECS.
The following table lists mandatory configurations. You can also select other configurations as necessary.
Table 1 Configuring an ECS purchase Category
Configuration Item
Suggestion
Configure Basic Settings
Billing Mode
Select Pay-per-use.
Instance
CPU Architecture
Select x86.
Specifications
Select 2 vCPUs and 8 GiB memory or higher.
OS
Image
Choose Public image > Ubuntu > Ubuntu 16.04 server 64bit.
Public Network Access
EIP
Select Auto assign.
Billed By
Select Bandwidth.
Instance Management
Login Mode
Select Password.
Password
Enter a custom password.
- Configure security group rules.
Use ports 5000 and 5001 to verify the sample project. Therefore, add an inbound rule that allows access over ports 5000 and 5001.
The procedure is as follows:
- Log in to the ECS list page, locate the ECS purchased in step 1, and click the ECS name.
- Click the Security Groups tab, and add an inbound rule with Protocol set to TCP and Port Range set to 5000-5001 by referring to Configuring Security Group Rules.
Adding a Target Host to the Project
Before deploying applications to ECSs, add the target hosts to the basic resources of the project.
- Go to the Phoenix Mall project and choose Settings > General > Basic Resources from the navigation pane.
- Click Create Host Cluster, configure the following information, and click Save.
Table 2 Creating a host cluster Parameter
Suggestion
Cluster Name
Enter host-group.
OS
Select Linux.
Host Connection Mode
Select Direct Connection.
Execution Resource Pool
Select Official.
- Click Add Host, configure the following information, and click OK.
Table 3 Adding a host Configuration Item
Suggestion
Add Hosts by
Select Adding IP.
Host Name
Keep this name same as the name of the purchased ECS.
IP
Enter the EIP generated when buying the ECS.
Authorization
Select Password.
Username
Enter root.
Password
Enter the password set when buying the ECS.
SSH Port
Enter 22.
- A host record is displayed on the page. If Succeed is displayed in the Verification Result column, the host is added successfully.
If the host fails to be added, check the host configuration based on the failure details.
Installing Dependency Tools on ECS
The sample program depends on Docker and Docker-Compose, which must be installed on the target ECS.
- Go to the Phoenix Mall project, choose CICD > Deploy, and find the phoenix-sample-predeploy application in the list.
- Click
and choose Edit from the drop-down list.
- Click the Environment Management tab and configure the host environment.
- Click Create Environment, configure the following information, and click Save.
Table 4 Creating an environment Parameter
Value
Environment
Enter phoenix-env.
Resource Type
Select Host.
OS
Select Linux.
NOTE:
If you do not have permission to create environments, contact the administrator to grant you permissions on the permission management page of the application.
- Click Import Host. In the displayed dialog box, select the configured host cluster and host and click Import.
- When a message indicating that the import is successful is displayed, close the window.
- Click Create Environment, configure the following information, and click Save.
- On the Deployment Actions tab page, edit the actions of the application.
In action Install Docker, select phoenix-env from the Environment drop-down list. If a dialog box is displayed, asking you to confirm whether you want to change the environment to phoenix-env for the subsequent actions, click OK.
- Click Save & Deploy to start the deployment task.
If a message is displayed indicating successful deployment, the task is successfully executed.
- Log in to the ECS and check whether the dependency tools are successfully installed:
- Run the docker -v command to check the Docker image version.
- Run the docker-compose -v command to check the Docker-Compose version.
If the command output similar to Figure 1 is displayed, the installation is successful.
Configuring and Executing an Application
During deployment, configure the ECS in the environment list of the application and set the build task phoenix-sample-ci as the deployment source.
- Go to the Phoenix Mall project, choose CICD > Deploy, and find the phoenix-sample-standalone application in the list.
- Click
and choose Edit from the drop-down list.
- Click the Environment Management tab and configure the host environment.
- Click Create Environment, configure the following information, and click Save.
Table 5 Creating an environment Parameter
Value
Environment
Enter phoenix-env.
Resource Type
Select Host.
OS
Select Linux.
- Click Import Host. In the displayed dialog box, select the configured host cluster and host and click Import.
- When a message indicating that the import is successful is displayed, close the window.
- Click Create Environment, configure the following information, and click Save.
- On the Deployment Actions tab page, edit the actions of the application.
- Click Select a Deployment Source. Set the deployment source by referring to Table 6.
Table 6 Configuring the deployment source Configuration Item
Suggestion
Source
Select Build task.
Build Task
Select phoenix-sample-ci.
Environment
Select phoenix-env.
If a dialog box is displayed, asking you to confirm whether you want to change the environment to phoenix-env for the subsequent actions, click OK.
- Retain the default settings in actions Decompress Files and Run Shell Commands.
- Click Select a Deployment Source. Set the deployment source by referring to Table 6.
- Click the Parameters tab and set parameters based on the SWR login command.
Obtain the login command from the console.
- Click Save & Deploy to start deployment.
If a message is displayed indicating that the deployment is successful, continue with the next step. If the deployment fails, rectify the fault based on the failed action and the error information in logs.
- Verify the deployment result.
- Open a browser, enter http://IP:5000 in the address box, and press Enter. IP indicates the elastic IP address of the ECS. The Phoenix Mall homepage is displayed.
- Enter http://IP:5001 and press Enter. IP indicates the elastic IP address of the ECS. The Phoenix Mall dashboard is displayed.
Releasing Resources
To avoid unnecessary fees, delete the ECS after the practice.
If you need to create a pipeline after the deployment, you can delete the ECS after completing the pipeline practice.
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