Updated on 2024-08-08 GMT+08:00

Quick Deployment

This section describes how to quickly deploy this solution.

Table 1 Parameter description

Parameter

Type

Mandatory

Description

Default Value

vpc_name

String

Yes

Virtual Private Cloud (VPC) name. You can select a template and create a VPC with the unique name. The name can include 1 to 57 characters and can contain letters, digits, underscores (_), hyphens (-), and periods (.).

deploy-a-highly-available-mongodb-demo

secgroup_name

String

Yes

Security group name. A new security group needs to be created. For details about how to configure a security group rule, see (Optional) Modifying Security Group Rules. The name can include 1 to 64 characters and can contain letters, digits, underscores (_), hyphens (-), and periods (.).

deploy-a-highly-available-mongodb-demo

ecs_name

String

Yes

Cloud server name, which must be unique. It can include 1 to 52 characters and can contain letters, digits, underscores (_), hyphens (-), and periods (.).

deploy-a-highly-available-mongodb-demo

ecs_flavor

String

Yes

Instance flavor of ECS or FlexusX. The flavor ID format of a FlexusX instance is x1.?u.?g. For example, the flavor ID of a FlexusX instance with 2 vCPUs and 4 GiB memory is x1.2u.4g. For details about FlexusX instance flavors, see the console. For details about ECS flavors, see A Summary List of x86 ECS Specifications.

x1.1u.2g

ecs_password

String

Yes

Initial password of the cloud server. The password can include 8 to 26 characters and must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters (!@$%^-_=+[{}]:,./?). The password cannot contain any username or the username spelled backwards. The administrator username is root.

Left blank

system_disk_size

String

Yes

System disk size of the cloud server. Value range (GiB): 40–1024. The system disk size cannot be reduced.

40

data_disk_size

String

Yes

Data disk size of the cloud server. Value range (GiB): 10–32768

100

charging_mode

String

Yes

Billing mode. By default, fees are automatically deducted. The value can be prePaid (yearly/monthly) or postPaid (pay-per-use).

postPaid

charging_unit

String

Yes

Subscription period unit. This parameter is mandatory when the billing mode is set to prePaid. The value can be month (monthly) or year (yearly).

month

charging_period

number

Yes

Required duration. When charging_unit is set to year, the value ranges from 1 to 3. When charging_unit is set to month, the value ranges from 1 to 9. This parameter is mandatory when charging_mode is set to prePaid.

1

eip_bandwidth_size

number

Yes

Elastic IP (EIP) bandwidth size, in Mbit/s. This template uses an EIP billed by bandwidth. The value ranges from 1 to 2000.

5

mongodb_password

String

Yes

Password of user root of the MongoDB database. After a MongoDB database is created, you can change its password by referring to (Optional) Changing the Password of the MongoDB Database. The password can include 4 to 12 characters and can contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters @%^-=

Left blank

  1. Log in to Huawei Cloud Solution Best Practices, choose Quick Deployment for a High-Availability MongoDB Database, and click Deploy.

    Figure 1 Selecting a solution

  2. On the Select Template page, click Next.

    Figure 2 Select Template

  1. On the Configure Parameters page, configure parameters by referring to Table 1 and click Next.

    Figure 3 Configure Parameters

  2. On the Configure Stack page, select the rf_admin_trust agency and click Next.

    Figure 4 Configure Stack

  1. On the Confirm Configurations page, click Create Execution Plan.

    Figure 5 Confirm Configurations

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

    Figure 6 Create Execution Plan

  3. Wait until the status of the execution plan changes to Available and click Deploy in the Operation column. In the displayed dialog box, click Execute.

    Figure 7 Execution plan created
    Figure 8 Confirming the execution plan

  4. Wait until the automatic deployment is complete and click the Events tab to view details.

    Figure 9 Resources created