Buying a Cluster Instance

Prerequisites

• You have created a Huawei Cloud account.

Procedure

1. Log in to the GeminiDB console.
2. In the service list, choose Databases > GeminiDB Influx API.
3. On the Instances page, click Buy DB Instance.
4. On the displayed page, specify a billing mode and instance specifications and click Next.
   Figure 1 Billing mode and basic information
   

   Table 1 Billing description

   Parameter

   Description

   Billing Mode

   Method that the instance is billed in. The value can be Yearly/Monthly or Pay-per-use. Yearly/Monthly In this mode, specify Required Duration at the bottom of the page. The system bills you based on the service price. If you do not need such an instance any longer after it expires, change the billing mode to pay-per-use to optimize costs. For details, see Yearly/Monthly to Pay-per-Use. NOTE: Yearly/Monthly instances cannot be deleted directly. If such an instance is no longer required, unsubscribe from it. For details, see How Do I Unsubscribe from Yearly/Monthly Instances?. Pay-per-use If you select this billing mode, you are billed based on how much time the instance is in use. If you expect to use an instance for a long period of time, change its billing mode to yearly/monthly to optimize costs. For details, see Pay-per-Use to Yearly/Monthly.

   Table 2 Basic information

   Parameter	Description
   Region	The region where the tenant is located. It can be changed in the upper left corner. NOTICE: Select the nearest region where you will access the instance from, so latency can be kept to a minimum and response will be faster. Instances deployed in different regions cannot communicate with each other over a private network. After you buy an instance, you cannot change its region.
   DB Instance Name	The instance name: Can be the same as an existing instance name. Contains 4 to 64 characters and must start with a letter. It is case-sensitive and allows only letters, digits, hyphens (-), and underscores (_). If the name contains Chinese characters, the length cannot exceed 64 bytes. You can change the name of an instance after it is created. For details, see Changing an Instance Name.
   Compatible API	InfluxDB
   DB Instance Type	Cluster
   DB Engine Version	1.8
   AZ	Availability zone where the instance is created. An AZ is a part of a region with its own independent power supplies and networks. AZs are physically isolated but can communicate with each other over a private network. An instance can be deployed in one or three AZs. If you want to deploy an instance in a single AZ, select one AZ. If you want to deploy your instance across AZs for disaster recovery, select three AZs. Nodes of the instance are evenly distributed across the three AZs.

   Figure 2 Specifications and storage
   

   Table 3 Specifications and storage

   Parameter	Description
   Data Node Specifications	Data nodes provide read and write capabilities for time series databases. The specifications depend on configurations of the DFV shared resource pool and memory. Select specifications based on service requirements. For details about supported specifications, see Instance Specifications.
   Data Nodes	Select the number of data nodes based on service requirements. After an instance is created, you can add nodes. For details, see Adding Nodes.
   Analysis Node Specifications	Analysis nodes analyze time series data. The analysis node is in the open beta test (OBT) phase. To use it, contact customer service.
   Analysis Nodes	Select the number of analysis nodes based on your service requirements.
   Storage Space	The storage is an integer and the minimum storage is 100 GB. You can add a minimum of 1 GB at a time.
   Purchase Cold Storage	Cold storage is used to store historical data that is not frequently queried. When purchasing a GeminiDB Influx instance, you can purchase cold storage and configure the retention policy to specify the retention period of hot data. In this way, hot data will be automatically archived in cold storage after the retention period expires, reducing storage costs. The value can be: Yes Set the cold storage capacity to suit your service requirements. No Do not purchase cold storage. For more information about cold and hot data separation, see Cold and Hot Data Separation. If you do not enable cold storage when creating an instance, you can enable it later based on service requirements. For details, see Enabling Cold Storage. NOTE: Cold storage cannot be disabled after being enabled.
   Cold Storage	The cold storage is an integer from 500 GB to 100,000 GB. You can add a minimum of 1 GB each time you scale up storage space. After an instance is created, you can scale up its cold storage. For details, see Scaling Up Cold Storage.

   Figure 3 Network and database configurations
   

   Table 4 Network configurations

   Parameter	Description
   VPC	The virtual network where the instance is created. A VPC isolates networks for different services. You can select an existing VPC or create one. For details about how to create a VPC, see "Creating a VPC" in Virtual Private Cloud User Guide. With VPC sharing, you can also use a VPC and subnet shared by another account. VPC owners can share the subnets in a VPC with one or multiple accounts through Resource Access Manager (RAM). This allows for more efficient use of network resources and reduces O&M costs. For more information about VPC subnet sharing, see VPC Sharing in Virtual Private Cloud User Guide. If there are no VPCs available, the system automatically allocates a VPC to you. NOTE: After a GeminiDB Influx instance is created, the VPC where the instance is deployed cannot be changed. If you want to connect to a GeminiDB Influx instance from an ECS over a private network, ensure that the instance and the ECS are in the same VPC. If they are not, create a VPC peering connection between them.
   Subnet	A subnet where your instance is created. The subnet provides dedicated and isolated networks, improving network security. NOTE: Creating an IPv4 subnet or selecting an existing one is recommended. IPv6 subnets are not supported.
   Security Group	A security group controls access between GeminiDB Influx instances and other services. Ensure that the security group you selected allows your client to access the instance. If no security group is available, the system creates one for you.

   Table 5 Database configurations

   Parameter	Description
   Administrator	Username of the administrator account. The default value is rwuser.
   Administrator Password	Password of the administrator account. The password: Can contain 8 to 32 characters. Can include uppercase letters, lowercase letters, digits, and any of the following special characters: ~!@#%^*-_=+? For security reasons, set a strong password. The system will verify the password strength. Keep your password secure. The system cannot retrieve it if it is lost.
   Confirm Password	This password must be consistent with the administrator password.
   Parameter Template	A template of parameters for creating an instance. The template contains API configuration values that are applied to one or more instances. After an instance is created, you can modify its parameters to better meet your service requirements. For details, see Modifying Parameters of GeminiDB Influx Instances.
   Enterprise Project	This parameter is provided for enterprise users. An enterprise project groups cloud resources, so you can manage resources and members by project. The default project is default. Select an enterprise project from the drop-down list. For more information about enterprise projects, see Enterprise Management User Guide.
   SSL	A security protocol. Secure Sockets Layer (SSL) certificates set up encrypted connections between clients and servers, preventing data from being tampered with or stolen during transmission. You can enable SSL to improve data security. After an instance is created, you can connect to it using SSL. Figure 4 Enabling SSL After SSL is enabled, you can select the default certificate or the certificate issued by the CCM service. NOTE: If SSL is not enabled when you create an instance, you can enable SSL after the instance is created. For details, see Enabling and Disabling the SSL Connection. For details about how to disable SSL, see Enabling and Disabling the SSL Connection.

   Table 6 Tags

   Parameter

   Description

   Tags

   The setting is optional. Adding tags helps you better identify and manage your instances. Each instance supports up to 10 tags by default. To use more tags, contact customer service to request a quota of 20 tags. If your organization has configured a tag policy for a GeminiDB Influx instance, you need to add a tag to the instance based on the tag policy. If the tag does not comply with the tag policy, the instance may fail to be created. Contact the organization administrator to learn details about the tag policy. A tag consists of a tag key and a tag value. Tag key: mandatory if the instance is going to be tagged Each tag key is unique for each instance. The key can include up to 36 characters, including digits, letters, underscores (_), and hyphens (-). Tag value: optional if the instance is going to be tagged The value can contain up to 43 characters, including digits, letters, underscores (_), periods (.), and hyphens (-). After an instance is created, you can view its tag details on the Tags tab. In addition, you can add, modify, and delete tags of an existing instance. For details, see Managing Tags.

   Table 7 Required duration

   Parameter	Description
   Required Duration	The length of your subscription if you select Yearly/Monthly billing. Subscription lengths range from one month to three years.
   Auto-renew	This option is not selected by default. If you select this option, the renew cycle is the same as the selected duration.

5. On the displayed page, confirm instance details.
   • For yearly/monthly instances
     • To modify the configurations, click Previous.
     • If no modification is required, read and agree to the service agreement, click Pay Now, and complete the payment.
   • Pay-per-use
     • To modify the configurations, click Previous.
     • If no modification is required, read and agree to the service agreement and click Submit.

6. Click Back to Instance Management to go to the instance list.
7. On the Instances page, view and manage the created instance.
   • Creating an instance takes about 5 to 9 minutes. During the process, the instance status displayed in the DB instance list is Creating.
   • After the creation is complete, the instance status changes to Available.

     You can click in the upper right corner of the page to refresh the instance status.

   • Automated backup is enabled by default during instance creation. A full backup is automatically triggered after an instance is created.
   • The default database port of the instance is 8635 and cannot be changed.
     Figure 5 Successful purchase