Rapid Deployment
This section describes how to efficiently deploy the Getting Started with Intelligent Data Insight solution. You can complete quick deployment by following the steps and instructions in this section.
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 57 characters. Only letters, numbers, underscores (_), hyphens (-), and periods (.) are allowed. |
intelligent-data-insight_demo |
secgroup_name |
String |
Mandatory |
The security group name. This template uses a newly created security group. For details, see Modifying Security Group Rules. It can contain up to 64 characters. Only letters, numbers, underscores (_), hyphens (-), and periods (.) are allowed. |
intelligent-data-insight_demo |
rds_name |
String |
Mandatory |
The RDS instance name. It must be unique and contain 4 to 64 characters. It must start with a letter and only letters (case-sensitive), numbers, hyphens (-), and underscores (_) are allowed. |
intelligent-data-insight_demo |
db_type |
String |
Mandatory |
The RDS engine. Options: MySQL and PostgreSQL. |
PostgreSQL |
rds_flavor |
String |
Mandatory |
The flavor of RDS instances. Single-node RDS instances are created by default. Default flavor of RDS for MySQL instances: rds.mysql.n1.large.2 (2U4G); default flavor of RDS for PostgreSQL instances: rds.pg.n1.large.2 (2U4G). For details about other flavors, see: |
rds.pg.n1.large.2 |
rds_port |
number |
Mandatory |
The RDS port. RDS for MySQL instances can use database ports 1024 to 65535, excluding 12017 and 33071, which are reserved for RDS system use. Default value: 3306. RDS for PostgreSQL instances can use database ports 2100 to 9500. Default value: 5432. |
5432 |
rds_volume_size |
number |
Mandatory |
The storage space of an RDS instance. The default storage disk type is SSD. The value ranges from 40 to 4000 and must be a multiple of 10. |
40 |
rds_password |
String |
Mandatory |
The initial password used for logging in to the RDS database. It must contain 8 to 32 characters and only letters, numbers, and the following special characters are allowed: ~!@#%^*-_=+? |
Empty |
db_account_name |
String |
Mandatory |
A user-defined RDS read-only username. It must be unique and contain 4 to 64 characters. It must start with a letter and only letters (case-sensitive), numbers, hyphens (-), and underscores (_) are allowed. |
readonly_user |
db_account_password |
String |
Mandatory |
The login password for a user-defined RDS read-only username. It must contain 8 to 32 characters and at least three of the following types of characters: uppercase letters, lowercase letters, numbers, and the following special characters: ~!@#%^*-_=+?, |
Empty |
db_name |
String |
Mandatory |
The database name. It can contain up to 63 characters. Only letters, numbers, and underscores (_) are allowed. It cannot start with pg or a number and must be different from RDS for PostgreSQL template database names. RDS for PostgreSQL template databases include postgres, template0, and template1. |
business_db |
dify_version |
String |
Mandatory |
The Dify community edition, supporting v1.1.3, v0.15.3, and v0.15.2. |
0.15.3 |
dify_ecs_name |
String |
Mandatory |
The name of a Dify cloud server. It must be unique and contain up to 54 characters. Only letters, numbers, underscores (_), hyphens (-), and periods (.) are allowed. |
intelligent-data-insight_dify_ecs_demo |
dify_ecs_flavor |
String |
Mandatory |
The flavor of Elastic Cloud Server (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 |
dify_password |
String |
Mandatory |
The password of the Dify 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 (!@$%^-_=+[{}]:,./?). For details about how to change the password, see Resetting the Password for Logging In to an ECS on the Management Console. Default administrator account: root. |
Empty |
dify_system_disk_size |
number |
Mandatory |
The system disk size of a Dify cloud server, in GB. The default disk type is high I/O. Value range: 40–1024. The disk cannot be shrunk. |
100 |
dify_eip_size |
number |
Mandatory |
The EIP bandwidth of a Dify cloud server, in Mbit/s. EIPs are billed by traffic. Value range: 1–300. |
300 |
db_query_ecs_name |
String |
Mandatory |
The name of the database interface cloud server. It must be unique and contain up to 54 characters. Only letters, numbers, underscores (_), hyphens (-), and periods (.) are allowed. |
intelligent-data-insight_db_query_demo |
db_query_ecs_flavor_id |
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.2u.4g |
db_query_password |
number |
Mandatory |
The password of the database interface cloud server. The password must contain 8 to 26 characters and at least the following types of characters: letters, numbers, and special characters. The following special characters are allowed: !@$%^-_=+[{}]:,./?. For details about how to change the password, see Resetting the Password for Logging In to an ECS on the Management Console. Default administrator account: root. |
Empty |
db_query_eip_size |
number |
Mandatory |
The EIP bandwidth of the database interface cloud server, in Mbit/s. EIPs are billed by traffic. Value range: 1–300. |
300 |
charging_mode |
String |
Mandatory |
The billing mode. Options: postPaid (pay-per-use) and prePaid (yearly/monthly). Default value: postPaid. |
postPaid |
charge_period_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 |
charge_period |
number |
Mandatory |
The subscription term. This parameter is only mandatory when charging_mode is set to prePaid (yearly/monthly). Value range: 1–3 (charging_unit set to year); 1–9 (charging_unit set to month). |
1 |
- Log in to Huawei Cloud Solution Best Practices, choose Getting Started with Intelligent Data Insight, and click Deploy. The Create Stack page is displayed.
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 1 and click Next.
Figure 3 Setting parameters
- 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 createdFigure 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 Resource Planning and Costs 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
- Refresh the page, click the Outputs tab, and view the access links (Dify platform access link and backend database query link) and link for importing the Dify workflow DSL file in the Value column. After the stack is successfully deployed, wait approximately 5 to 10 minutes (affected by network fluctuations) before you can log in to Dify.
Figure 10 Descriptions
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