Rapid Deployment

This section describes how to efficiently deploy the "Building a Dify-LLM Application Development Platform" solution. You can complete quick deployment by following the steps and instructions in this section.

Log in to Huawei Cloud Solutions, choose Building a Dify-LLM Application Development Platform, select the version to deploy, and click Deploy (HA Deployment in CCE Container) to go to the resource stack creation page.

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

Figure 2 Selecting a template

On the Configure Parameters page, set parameters according to Table 2 and click Next.

Figure 3 Setting parameters

**Table 1** Parameter descriptions (single-cloud server deployment)
Parameter	Type	Mandatory	Description	Default Value
vpc_name	String	Mandatory	The Virtual Private Cloud (VPC) name. This template uses a newly created VPC. The name must be unique. It can contain up to 54 characters. Only letters, numbers, underscores (_), hyphens (-), and periods (.) are allowed.	dify-llm-application-development-platform-demo
secgroup_name	String	Mandatory	The security group name. This template uses a newly created security group. For details about how to configure a security group rule, see (Optional) Modifying Security Group Rules. The group name can contain up to 64 characters. Only letters, numbers, underscores (_), hyphens (-), and periods (.) are allowed.	dify-llm-application-development-platform-demo
ecs_name	String	Mandatory	The name of a cloud server instance. It must be unique and can contain up to 64 characters. Only letters, numbers, underscores (_), hyphens (-), and periods (.) are allowed.	dify-llm-application-development-platform-demo
ecs_flavor	String	Mandatory	The flavor of ECS or FlexusX. The flavor ID format of a FlexusX is x1.?u.?g. For example, the flavor ID of a FlexusX with 2 vCPUs and 4 GiB memory is x1.2u.4g. For details about FlexusX flavors, refer to the console. For details about ECS flavors, see A Summary List of x86 ECS Specifications.	x1.8u.16g
ecs_password	String	Mandatory	The password of the cloud server. The password must contain 8 to 26 characters and include at least three of the following types of characters: uppercase letters, lowercase letters, numbers, and special characters (!@$%^-_=+[{}]:,./?). The password cannot contain the username or the username spelled backwards. Default administrator account: root.	Empty
system_disk_size	Number	Mandatory	The system disk size of a cloud server, in GB. The default disk type is high I/O. Value range: 40–1024. The disk cannot be shrunk.	100
bandwidth_size	Number	Mandatory	The EIP bandwidth, in Mbit/s. EIPs are billed by traffic. Value range: 1–300.	300
charging_mode	String	Mandatory	The cloud server billing mode. Options: postPaid (pay-per-use) and prePaid (yearly/monthly).	postPaid
charging_unit	String	Mandatory	The unit of a cloud server subscription term. This parameter is only mandatory when charging_mode is set to prePaid (yearly/monthly). Options: month and year.	month
charging_period	Number	Mandatory	The cloud server subscription term. This parameter is only mandatory when charging_mode is set to prePaid (yearly/monthly). Value range: 1–9 (charging_unit set to month); 1–3 (charging_unit set to year).	1

**Table 2** Parameter descriptions (HA deployment in CCE container)
Parameter	Type	Mandatory	Description	Default Value
dify_version	string	Mandatory	Community Edition Dify version. You can choose from 1.7.1, 1.4.1, or 0.15.8. The default is 1.7.1.	1.7.1
resource_name_prefix	String	Mandatory	The resource name prefix. The naming rule is {resource_name_prefix}-Resource name. For example, the CCE cluster name is {resource_name_prefix}-cce. The name can contain 4 to 24 characters, and only lowercase letters, numbers, and hyphens (-) are allowed. It must start with a lowercase letter and cannot start with a hyphen (-).	ha-dify-app
bandwidth_size	String	Mandatory	The EIP bandwidth, in Mbit/s. EIPs are billed by traffic. Value range: 1–300.	300
cce_cluster_flavor	String	Mandatory	The CCE Turbo cluster flavor. It cannot be changed after the cluster is created. Options: cce.s2.small, cce.s2.medium, cce.s2.large, and cce.s2.xlarge. For details, refer to Request parameter flavor required for creating a CCE cluster. The default value is cce.s2.small (small-scale CCE cluster with multiple master nodes and a maximum of 50 worker nodes).	cce.s2.small
cce_node_pool_password	String	Mandatory	The password for logging in to the worker node of the CCE cluster. It must contain 8 to 24 characters and at least one uppercase letter, one lowercase letter, and one number or one of the following special characters: ~!@#$^*-=_+,?
cce_node_pool_flavor	String	Mandatory	The flavor of ECS or FlexusX of the CCE cluster. The flavor ID format of a FlexusX is x1.?u.?g. For example, the flavor ID of a FlexusX with 2 vCPUs and 4 GiB memory is x1.2u.4g. Use FlexusX with 3 vCPUs and 6 GiB memory or higher specifications. For details about FlexusX flavors, refer to the console. For details about ECS flavors, see A Summary List of x86 ECS Specifications.	x1.16u.16g
rds_flavor	String	Mandatory	The flavor of the RDS for PostgreSQL instances. A primary/standby RDS for PostgreSQL instance is created by default. Default value: rds.pg.x1.2xlarge.4.ha (8 vCPUs and 32 GiB memory). For details about other flavors, see RDS for PostgreSQL Instance Classes.	rds.pg.n1.large.2.ha
pgsql_password	String	Mandatory	The administrator password of the PostgreSQL database. It must contain 8 to 24 characters and at least one uppercase letter, one lowercase letter, and one number or one of the following special characters: ~!^*-=_+,
pgsql_user_password	String	Mandatory	The password of the database user of the PostgreSQL database. The value can contain 8 to 24 characters and must contain at least one uppercase letter, one lowercase letter, and one number or special character (~!^*-=_+,). The password cannot be the same as the username or the username spelled backwards.
redis_capacity	Number	Mandatory	The DCS for Redis instance specifications. Value range: 1 GB to 64 GB.	4
redis_password	String	Mandatory	The Redis database password. It must contain 8 to 24 characters and at least one uppercase letter, one lowercase letter, and one number or one of the following special characters: ~!^*-=_+,
obs_bucket	String	Mandatory	The name of an existing OBS bucket. The region the bucket belongs to must be the same as that selected for one-click deployment. The bucket is used to store knowledge base files uploaded on the Dify web UI. For details about how to obtain a bucket name, see Obtaining the OBS Bucket Name.
access_key	String	Mandatory	The access key ID (AK) that will be used to identify the user. It is a 20-character alphanumeric string. It is used to upload knowledge base files to OBS buckets. For details, see Obtaining an AK and SK.
secret_key	String	Mandatory	The secret access key (SK). It is used to sign and verify request data. It is a 40-character alphanumeric string. It is used to upload knowledge base files to OBS buckets. For details, see Obtaining an AK and SK.
embedding_reranker_flavor	String	Optional	(Optional, leave blank to not create)The specifications of the cloud server where embedding and reranker models are deployed, supporting ECS (including GPU servers) and FlexusX. The flavor ID format of a FlexusX is x1.?u.?g. For example, the flavor ID of a FlexusX with 4 vCPUs and 4 GiB memory is x1.4u.4g. You are advised to use FlexusX with 8 vCPUs and 8 GiB memory or higher specifications. For details about FlexusX flavors, refer to the console. For details about ECS flavors, see A Summary List of x86 ECS Specifications. GPU-accelerated ECSs can be used for higher performance. Default :c7n.8xlarge.2.	c7n.4xlarge.2
ecs_password	String	Optional	The password of the cloud server where embedding and reranker models are deployed. The value can contain 8 to 24 characters and must contain at least one uppercase letter, one lowercase letter, and one number or one of the following special characters: ~!@#$^*-=_+,?
charging_mode	String	Mandatory	The billing mode. Options: postPaid (pay-per-use) and prePaid (yearly/monthly). Default value: postPaid.	postPaid
charging_unit	String	Mandatory	The unit of the subscription term. This parameter is only mandatory when charging_mode is set to prePaid (yearly/monthly). Options: month and year.	month
charging_period	Number	Mandatory	The subscription term. This parameter is only mandatory when charging_mode is set to prePaid (yearly/monthly). Value range: 1–9 (charging_unit set to month); 1–3 (charging_unit set to year).	1

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 a master account (HUAWEI ID) or use an IAM user in the admin user group.

Figure 4 Selecting an agency
On the Confirm Configurations page, click Create Execution Plan.

Figure 5 Confirming configurations
In the Create Execution Plan dialog box that appears, enter an execution plan name and click OK.

Figure 6 Creating an execution plan
Click Deploy in the Operation column. In the displayed dialog box, click Execute.

Figure 7 Execution plan created

Figure 8 Deploying the execution plan
(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 pending order. Refer to the corresponding table in Table 4 for the total cost of one-click cloud service deployment under the yearly/monthly billing mode.
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.

Figure 9 Solution deployed
On the Outputs tab, view the access description of the Dify platform. After the stack is successfully deployed, the Dify application setup script starts to execute. Wait for approximately 5 to 10 minutes (affected by network fluctuations).

Figure 10 Access description