Quick Deployment

This section helps users efficiently deploy the "Quick Deployment of Hermes Agent" solution. By following the steps and instructions in this section to deploy the solution with one click, you can complete the rapid deployment.

1. Log in to Huawei Cloud Quick-Start Guides and choose Deploying Hermes Agents. Click Deploy.
   Figure 1 Selecting a solution
   

2. On the Select Template page, click Next.
   Figure 2 Selecting a solution
   

3. On the Configure Parameters page, enter a stack name, configure parameters based on Table1 Parameter description, and click Next.
   Figure 3 Configuring parameters
   

   Table 1 Parameter descriptions (single-cloud server deployment)

   Parameter	Type	Mandatory	Description	Default Value
   solution_name	String	Mandatory	Solution name, value range: 4-24 characters, supports lowercase letters, numbers, and hyphens (-). Must start with a lowercase letter. Cannot start with a hyphen (-).	deploying-hermes-agent-demo
   ecs_flavor	String	Mandatory	Cloud server instance specifications, supporting Elastic Cloud Server (ECS) and Huawei Cloud Flexus X instances. Flexus X instance specification IDs follow the naming pattern x1.?u.?g, for example, x1.2u.4g for 2vCPUs4GiB. For specific Huawei Cloud Flexus X instance specifications, please refer to the console. For ECS specifications, refer to the deployment guide configuration. see A Summary List of x86 ECS Specifications.	x1.2u.4g
   ecs_password	String	Mandatory	Cloud server password, with a length of 8-26 characters, must contain at least three of the following: uppercase letters, lowercase letters, digits, and special characters (!@$%^-_=+[{}]:,./?). The default administrator account is root.	Empty
   system_disk_size	Number	Mandatory	Cloud server system disk size, disk type defaults to High IO, unit: GB, value range is 40-1,024, shrinking the disk is not supported.	100
   bandwidth_size	Number	Mandatory	Elastic public network bandwidth size, billing mode for this template is pay-by-traffic. Unit: Mbit/s, value range: 1-300 Mbit/s.	300
   charging_mode	String	Mandatory	Billing mode, default automatic payment. Optional values: postPaid (pay-as-you-go), prePaid (yearly/monthly subscription).	postPaid
   charging_unit	String	Mandatory	Subscription period type, effective only when charging_mode is prePaid (yearly/monthly subscription). This parameter becomes mandatory in this case. Optional values: month (monthly), year (yearly).	month
   charging_period	Number	Mandatory	Subscription period, effective only when charging_mode is prePaid (yearly/monthly subscription). This parameter becomes mandatory in this case. When charging_unit=month (monthly cycle type), value range: 1-9; when charging_unit=year (yearly cycle type), value range: 1-3.	1

4. On the Configure Stack page, select rf_admin_trust from the Agency drop-down list and click Next. This step is optional if you use an account (HUAWEI ID) or use an IAM user in the admin user group.
   Figure 4 Configuring a stack
   

5. On the Confirm Configurations page, confirm the configurations and click Create Execution Plan.
   Figure 5 Confirming the configurations
   

6. In the displayed Create Execution Plan dialog box, enter an execution plan name and click OK.
   Figure 6 Creating an execution plan
   

7. Wait until the status of the execution plan changes to Available and then click Deploy in the Operation column. In the displayed dialog box, click Execute.
   Figure 7 Execution plan page
   
   Figure 8 Confirming the execution plan
   

8. (Optional) If you select the yearly/monthly billing mode and your account balance is insufficient, log in to the Billing Center to manually pay for the order. You can refer to Table2 Resource planning costs (yearly/monthly) to see the total price.
9. Click the Events tab and check whether the message "Apply required resource success." is displayed in the Description column. If it is, the solution is successfully deployed. Deployment of BISHENG platform script started execution. Wait for approximately 5 to 10 minutes (affected by network fluctuations).
   Figure 9 Solution deployed
   
   Figure 10 Access description