Creating a GaussDB(DWS) 3.0 Cluster

Preparations Before Creating a Cluster

• You have evaluated the flavor of cluster nodes.

  You can select the number of nodes by data volume, service load, and performance. More nodes bring you stronger storage and compute capabilities.

  When first using GaussDB(DWS), you can create a cluster with a smaller flavor. Then, you can adjust the cluster scale and node flavor based on the data volume and service load changes without interrupting services. For details, see Scaling Out a Cluster.

• Determine the number of nodes that can be used by users.

  Ensure that the number of available nodes is greater than or equal to 3. Otherwise, the system displays a message indicating that the cluster cannot be created. You can choose Clusters > Dedicated Clusters to view the number of available nodes.

Creating a Cluster

1. Go to the page for creating a data warehouse cluster.
2. Select a billing mode. For more information, see Pricing Details.
   • Yearly/Monthly: If you select Yearly/Monthly, you need to set the required duration in 12 before proceeding with the following steps.
   • Pay-per-use (hourly): If you select this mode, you are charged based on the actual usage duration (accurate to minutes).

3. Select a region and an AZ.
4. Configure Resource, CPU Architecture, and Node Flavor.
   

   • The number of nodes in a new cluster cannot exceed the quota that can be used by a user or 256. If the node quota is insufficient, click Increase quota to submit a service ticket and apply for higher node quota.
   • If you have yearly/monthly nodes that meet service requirements, you are advised to use these nodes first to save costs. You can select Yearly/Monthly for Billing Mode.
   Figure 1 Configuring node parameters
   

   Table 1 Node configuration parameters

   Parameter	Description	Example Value
   Resource	The options are as follows: Standard data warehouse: It can analyze hot and cold data and is highly cost-effective. Its storage and computing resources are not limited, and can be elastically scaled and billed per use. It is suitable for the converged analysis that requires integrated databases, warehouses, marts, and lakes. It is most suitable for OLAP workloads.	Standard
   Version	DWS 3.0	DWS 3.0
   Compute Resource	It can be: ESC: Scalable, reliable, and high-throughput virtual block storage is provided in a distributed architecture. This ensures that data can be quickly migrated and restored if any data replica is unavailable, preventing data from being lost because of a single hardware fault. Backup and restoration can be performed on ECSs and EVS disks. You can configure automatic backup policies for them.	-
   Storage Type	It can be: Cloud SSD Extreme SSD: suitable for workloads that demand super-high bandwidth and super-low latency. Extreme SSD V2: ultra-high-performance SSD EVS disks dedicated for latency-sensitive mission-critical applications. NOTE: For more information, see Disk Types and Performance.	-
   CPU Architecture	The following CPU architectures can be selected: X86 Kunpeng NOTE: The only difference between the x86 and Kunpeng architectures lies in the underlying architecture, of which the application layer is unaware. The same SQL syntax is used. If x86 servers are sold out when you create a cluster, select the Kunpeng architecture.	-
   Node Flavor	Select a node flavor. Each node flavor shows the vCPU, memory, and recommended application scenario. For more information about the node flavors supported by GaussDB(DWS) and their prices, see the GaussDB(DWS) pricing details. For details about the node flavors supported by GaussDB(DWS), see Data Warehouse Specifications.	-
   Hot Storage (with Cache)	Available storage capacity of each node. NOTE: The storage capacity you apply for has the necessary file system overhead, which includes index nodes and the space required for database running. The displayed 200GB/node includes the storage for cache. For example, if you create 3 nodes, each having 200 GB capacity, the total resource capacity is 600 GB, and the actual storage space available to you is 300 GB.	-
   Cold Storage	Store data in separate OBS buckets, which are billed on a pay-per-use basis.	-
   Nodes	Specify the number of nodes in the cluster. The number of nodes ranges from 3 to 256.	3
   Total	Display the cluster's total capacity. The storage capacity of each flavor includes the storage for cache. The displayed storage capacity includes the disk space consumed by backups and RAIDs.	-

5. Click Next: Configure Network.
6. Configure the network.

   Table 2 Network parameters

   Parameter	Description	Example Value
   VPC	Specify a VPC to isolate the cluster's network. If you create a data warehouse cluster for the first time and have not configured the VPC, click View VPC. On the VPC management console that is displayed, create a VPC as needed. For details about how to create a VPC, see Creating a VPC in the Virtual Private Cloud User Guide. After selecting a VPC from the drop-down list, click View VPC to enter the VPC management console and view the detailed information about the VPC. You can click to refresh the options in the VPC drop-down list. NOTE: You cancreate a share to share VPC resources with other members. After responding to a resource sharing invitation, the members can select the shared VPC resources. For details, see How Do I Use VPC Sharing to Process GaussDB(DWS) Resources?.	vpc-dws
   Subnet	Specify a VPC subnet. A subnet provides dedicated network resources that are isolated from other networks, improving network security.	subnet-dws
   Security Group	Specify a VPC security group. A security group restricts access rules to enhance security when GaussDB(DWS) and other services access each other. Automatic creation If Automatic creation is selected, the system automatically creates a default security group. This option is selected by default. The rule of the default security group is as follows: The outbound allows all access requests, while the inbound is open only to the database port that you set to connect to the GaussDB(DWS) cluster. The format of the default security group's name is dws-<cluster name>-<database port of the GaussDB(DWS) cluster>, for example, dws-dws-demo-8000. NOTE: If the quotas of the security group and the security group rule are insufficient, an error message will be displayed after you submit the cluster creation application. You can select an existing group and retry. Manual creation You can also log in to the VPC management console to manually create a security group. Then, go back to the page for creating data warehouse clusters, click the button next to the Security Group drop-down list to refresh the page, and select the new security group. To enable the GaussDB(DWS) client to connect to the cluster, you need to add an inbound rule to the new security group to grant the access permission to the database port of the GaussDB(DWS) cluster. The following is an example of an inbound rule. For details, see Adding an Inbound Rule. Protocol: TCP. Port: 8000. Use the database port set when creating the GaussDB(DWS) cluster. This port is used for receiving client connections to GaussDB(DWS). Source: Select IP address and use the host IP address of the client host, for example, 192.168.0.10/32. After a GaussDB(DWS) cluster is created, you can change the security group. You can also add, delete, or modify security group rules in the current security group. For details, see Modifying a Security Group.	Automatic creation
   EIP	Specify whether users can use a client to connect to a cluster's database over the Internet. The following methods are supported: Do not use: Do not specify any EIPs here. If GaussDB(DWS) is used in the production environment, first bind it to ELB, and then bind it to an EIP on the ELB page. Buy now: Users specify the bandwidth of the EIP and the system automatically assigns an EIP that exclusively uses bandwidth to each cluster so that users can use the EIP to access the cluster over the Internet. The bandwidth name of an automatically assigned EIP starts with the cluster name. Specify: Specify an EIP to be bound to the cluster. If no available EIPs are displayed in the drop-down list, click Create EIP to go to the Elastic IP page and create an EIP as needed. The bandwidth can be customized. NOTE: In yearly/monthly billing mode, you cannot buy an EIP during cluster creation. If you use the EIP binding function for the first time in each project of each region, the system prompts you to create the DWSAccessVPC agency to authorize GaussDB(DWS) to access VPC. After the authorization is successful, GaussDB(DWS) can switch to a healthy VM when the VM bound with the EIP becomes faulty. By default, only cloud accounts or users with Security Administrator permissions can query and create agencies. By default, the IAM users in those accounts cannot query or create agencies. When the users use the EIP, the system makes the binding function unavailable. Contact a user with the DWS Administrator permissions to authorize the agency on the current page. Do not use indicates disabling access to the cluster over the public network. After a cluster is created, if you want to access it over the public network, bind an EIP to the cluster and create a public network domain name. For details, see Creating a Public Network Domain Name. If GaussDB(DWS) is used for the production environment, the new GaussDB(DWS) cluster needs to be bound to ELB and then to EIP. Select Do not use here.	Buy now
   ELB	Specifies whether ELB is bound. With ELB health checks, CN requests of a cluster can be quickly forwarded to normal CNs. If a CN is faulty, the workload can be immediately shifted to a healthy node, minimizing cluster access faults. Currently, ELBs can be bound in the same VPC or across VPCs. Do not use: The load balancer is not used. If GaussDB(DWS) is used in the production environment, first bind it to ELB, and then bind it to an EIP on the ELB page. Specify: Specify an ELB to be bound to the cluster. If no available load balancers are displayed in the drop-down list, click Create ELB to go to the Elastic Load Balance page and create a load balancer as needed.	Specify
   Bandwidth	Specifies the EIP bandwidth. The value ranges from 1 Mbit/s to 100 Mbit/s. This parameter is mandatory if EIP is set to Buy now.	50Mbit/s

7. Click Next: Configure Advanced Settings.
8. Configure cluster parameters.

   Table 3 Cluster parameters

   Parameter	Description	Example Value
   Cluster Name	Set the name of the data warehouse cluster. The cluster name contains 4 to 64 case-insensitive characters and must start with a letter. Only letters, digits, hyphens (-), and underscores (_) are allowed. NOTE: If the cluster name cannot be changed on the console, contact technical support.	dws-demo
   Cluster Version	Version of the database instance installed in the cluster. The example version number is for reference only.	9.0.0
   Default Database	The default database name of the cluster is gaussdb. NOTE: This name cannot be changed.	gaussdb
   Administrator Account	Set the database administrator name. The username must meet the following requirements: Consists of lowercase letters, digits, or underscores. Starts with a lowercase letter or an underscore. Contains 6 to 64 characters. Cannot be a keyword of the GaussDB(DWS) database. For details about the keywords of the GaussDB(DWS) database, see Keyword in the Data Warehouse Service (DWS) Developer Guide.	dbadmin
   Administrator Password	Set the password of the database administrator account. The password complexity requirements are as follows: Contains 12 to 32 characters. Cannot be the username or the username spelled backwards. Must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters (~!?,.:;_(){}[]/<>@#%^&*+|\=-) Passes the weak password check. NOTE: Change the password regularly and keep it secure.	-
   Confirm Password	Enter the database administrator password again.	-
   Database Port	Set the port used when the client or application connects to the database in the cluster. The port number ranges from 8000 to 30000.	8000
   IPv6	Specify whether to enable the IPv6 dual stack for the cluster. If this function is enabled, a client or application can connect to the database using an IPv6 address. NOTE: To enable IPv6, the following conditions must be met: The subnet configured in 7 is an IPv6 dual-stack subnet. The cluster supports IPv6 addresses and a maximum of three NICs. The cluster version must be 8.2.1.210 or later.	-
   Time Zone	You can set the time zone for the tenant cluster, including the system OS time zone and cluster data warehouse time zone.	-

9. Select the enterprise project of the cluster. You can configure this parameter only when the Enterprise Project Management service is enabled. The default value is default.

   An enterprise project facilitates project-level management and grouping of cloud resources and users.

   You can select the default enterprise project default or other existing enterprise projects. To create an enterprise project, log in to the Enterprise Management console. For details, see Enterprise Management User Guide.

10. Configure advanced parameters. Select Default to keep the default values of the advanced parameters. You can also select Custom to modify the values.
    • After this function is enabled, you can set the retention mode and the backup device used by the current cluster for automated snapshots. For more information, see Table 4.

      Table 4 Automated snapshot parameters

      Parameter	Description
      Backup Device	Select OBS or NFS from the drop-down list.
      NFS Backup File System Address (NFS)	NFS shared IP address. To mount the SFS shared path, enter its IP address. If successful, a mount directory will be created in the /var/chroot/nfsbackup directory of the cluster instance.

    • CNs

      CNs receive access requests from the clients and return the execution results. In addition, a CN splits and distributes tasks to the DNs for parallel execution.

      The value ranges from 3 to the number of cluster nodes. The maximum value is 20 and the default value is 3. In a large-scale cluster, you are advised to deploy multiple CNs.

    • Tags

      A tag is a key-value pair used to identify a cluster. For details about the keys and values, see Table 5. By default, no tag is added to the cluster.

      If your organization has configured GaussDB(DWS) tag policies, you need to add tags to clusters based on the tag policies. If a tag does not comply with the tag policies, cluster creation may fail. Contact your organization administrator to learn more about tag policies.

      For details about tags, see Overview.

      Table 5 Tag parameters

      Parameter	Description	Example Value
      Tag key	You can: Select a predefined tag key or an existing resource tag key from the drop-down list of the text box. NOTE: To add a predefined tag, you need to create one on TMS and select it from the drop-down list of Tag key. You can click View predefined tags to enter the Predefined Tags page of TMS. Then, click Create Tag to create a predefined tag. For more information, see Creating Predefined Tags in Tag Management Service User Guide. Enter a tag key in the text box. A tag key can contain a maximum of 36 characters. It cannot be an empty string or start or end with a space. The value cannot contain the following characters: =*<>\,|/ NOTE: A key must be unique in a given cluster.	key01
      Value	You can: Select a predefined tag value or resource tag value from the drop-down list of the text box. Enter a tag value in the text box. A tag value can contain a maximum of 43 characters, which can be an empty string. It cannot start or end with a space. The value cannot contain the following characters: =*<>\,|/	value01

11. Select a billing mode. If you select the yearly/monthly mode, you also need to configure the service duration.

    Table 6 Duration

    Parameter	Function
    Required Duration (Yearly/Monthly)	Configure the required duration. You get a greater discount if you purchase a longer period. Price is displayed at the bottom of the page for your reference. You can click Pricing details to view the detailed price.
    Auto-renewal (Yearly/Monthly)	By default, this option is not selected. Renewal rules: If you select one month to nine months, the renewal interval is one month. Your subscription will be renewed each year for yearly billing. Example: Customer A purchases a cluster in yearly/monthly mode and select enables auto-renewal. If the cluster is subscribed to for eight months, it will be automatically renewed each month. If the cluster is subscribed to for two years, it will be automatically renewed each year. For details about the renewal fee deduction, see Fee Deduction Rules.

12. Click Next: Confirm.
    

    If the number of requested nodes, vCPU (cores), or memory (GB) exceed the user's remaining quota, a warning dialog box is displayed, indicating that the quota is insufficient and displaying the detailed remaining quota and the current quota application. You can click Increase quota in the warning dialog box to submit a service ticket and apply for higher node quota. Once approved, we will update your resource quota accordingly and send you a notification. For details about quota operations, see Quotas.

13. Click Next. If the billing mode is Yearly/Monthly, click Buy Now. The payment page is displayed.

    After the submission is successful, the creation starts. Click Back to Cluster List. The cluster management page is displayed. The initial status of the cluster is Creating. Cluster creation takes some time. Wait for a while. Clusters in the Available state are ready for use.