هذه الصفحة غير متوفرة حاليًا بلغتك المحلية. نحن نعمل جاهدين على إضافة المزيد من اللغات. شاكرين تفهمك ودعمك المستمر لنا.
- Service Overview
- Billing
- Getting Started
-
User Guide
- Overview
- Permissions Management
- Environment Management
- Application Management
- Component Management
- Instance Management
- Component Configurations
- Component O&M
- System Settings
- Key Operations Recorded by CTS
-
Best Practices
- CAE Best Practices
- Using CAE to Host Nginx Static File Servers
- Interconnecting GitLab with Jenkins for Automatic Build and Deployment on CAE
- Deploying Components Based on the Dependency Sequence Using the Jenkins Pipeline
- Deploying Spring Cloud Applications to CAE to Automatically Connect to the Nacos Engine
- Graceful Startup of a Spring Cloud Application
- Health Check
- Lifecycle Management
- Sending Event Alarms to WeCom
-
Connecting to the CodeArts Pipeline to Automatically Upgrade CAE Components
- Overview
- Upgrading a CAE Component After Uploading a Software Package Built Using the Pipeline to a CodeArts Release Repo
- Upgrading a CAE Component After Uploading a Software Package Built Using the Pipeline to the OBS Bucket
- Upgrading a CAE Component After Uploading an Image Built Using the Pipeline to the SWR Image Repository
- Configuring PromQL to Implement Custom Auto Scaling
- Configuring the Interconnection Between CAE and DEW to Help Applications Obtain Encrypted Secrets from DEW
- Deploying ASP.NET Core Applications to CAE
- Connecting the Network Through Enterprise Routes
- API Reference
-
FAQs
- Component Management FAQs
- Environment Management
-
Component Configuration FAQs
- Is Manual Scaling Still Effective When a Scaling Policy Is Configured?
- Can Components Be Scaled Without a Scaling Policy?
- Why Is My Instance Abnormal After Cloud Storage Is Configured?
- What Do I Do If a Component Becomes Not Ready?
- How Does CAE Support Dark Launch?
- How Do I Provide Prometheus Metrics for a Java Application?
- System Configuration FAQs
- Service Resources FAQs
- General Reference
Copied.
Installing KooCLI
KooCLI is used to call CAE APIs to upgrade components.
Install and initialize KooCLI to use it.
- Install KooCLI by Method 1: Online Installation or Method 2: Using Software Package
- Initializing KooCLI
Method 1: Online Installation
- Log in to the VM where Jenkins is located.
- Run the following command:
curl -sSL https://hwcloudcli.obs.cn-north-1.myhuaweicloud.com/cli/latest/hcloud_install.sh -o ./hcloud_install.sh && bash ./hcloud_install.sh -y
NOTE:
By default, KooCLI is downloaded to the /usr/local/hcloud/ directory. A symbolic link is created for KooCLI in the /usr/local/bin/ directory.
Method 2: Using Software Package
- Log in to the VM where Jenkins is located and run the following command to check the OS to be installed:
echo $HOSTTYPE
- If the command output is x86_64, download the AMD 64-bit OS.
- If the command output is aarch64, download the Arm 64-bit OS.
- Run the following command to download the software package:
- AMD
wget "https://hwcloudcli.obs.cn-north-1.myhuaweicloud.com/cli/latest/huaweicloud-cli-linux-amd64.tar.gz" -O huaweicloud-cli-linux-amd64.tar.gz
- ARM
wget "https://hwcloudcli.obs.cn-north-1.myhuaweicloud.com/cli/latest/huaweicloud-cli-linux-arm64.tar.gz" -O huaweicloud-cli-linux-arm64.tar.gz
- AMD
- Run the following command to decompress the software package:
- AMD
tar -zxvf huaweicloud-cli-linux-amd64.tar.gz
- ARM
tar -zxvf huaweicloud-cli-linux-arm64.tar.gz
- AMD
- Run the following command in the decompressed directory to create a soft link to the /usr/local/bin directory:
ln -s $(pwd)/hcloud /usr/local/bin/
- Run the following command to check whether the installation is successful:
hcloud version
If information similar to "KooCLI version: 3.4.1.1" is displayed, the installation is successful.
Verifying the Installation
- After KooCLI is installed, run the hcloud CAE command to check whether the CAE service is supported.
- If "Unsupported service: CAE" is displayed, change the language of KooCLI to Chinese.
hcloud configure set --cli-lang=cn
- Run the hcloud CAE command again.
- If no "ERROR" is displayed, KooCLI supports the CAE service.
Initializing KooCLI
- Log in to the Linux VM where Jenkins is located.
- Enter the command and press Enter to enter the interactive mode, and set the parameters as prompted. For details, see Table 1.
hcloud configure init
Table 1 Initial configurations Parameter
Description
Access Key ID
Mandatory. For details, see Access Keys.
Secret Access Key
Mandatory. For details, see Access Keys.
Region
Optional. Region where CAE is deployed. For details, see Regions and Endpoints.
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