A cloud data warehouse automatic deployment method, device, terminal and storage medium

Abstract

The present application provides a cloud data warehouse automatic deployment method, device, terminal and storage medium, which relates to the field of electronic digital data processing. The method includes: using the helm chart installation package of the cloud data warehouse to deploy the basic service components of the cloud data warehouse on the kubernetes cloud native platform, the basic service components include cloud service front-end and back-end components and kubernetes node management components; using the cloud service front-end and back-end components and kubernetes node management components to create the database metadata management components and database coordination node components of the target tenant; using the cloud service front-end and back-end components, kubernetes node management components and target tenant database coordination node components to create the database computing node components of the target tenant. The present application can largely avoid the error-prone problems of traditional manual deployment, and greatly improve the ease of use, practicality and portability of cloud data warehouse products.

Description

Technical Field

[0001] The present application relates to the field of electronic digital data processing, and in particular to a cloud data warehouse automatic deployment method, device, terminal and storage medium. Background Art

[0002] GBase Cloud Data Warehouse (GCDW) is a cloud-native data warehouse with storage and computing separation launched by GBase based on the Kubernetes cloud-native platform. The GCDW product is relatively complex and contains many components. When deployed on the Kubernetes cloud-native platform using the traditional method, many related YAML files need to be manually created for each component, and many YAML files need to fill in many parameters. Not only is the process cumbersome and complicated, but it is also prone to errors. Therefore, for the GCDW product, a more efficient automated deployment method based on cloud-native is needed. Summary of the invention

[0003] The present application provides a cloud data warehouse automatic deployment method, device, terminal and storage medium to solve the problem that the process of manually deploying a cloud data warehouse on a Kubernetes cloud native platform in a traditional way is cumbersome, complex and error-prone.

[0004] In a first aspect, the present application provides a cloud data warehouse automatic deployment method, comprising:

[0005] Use the helm chart installation package of the cloud data warehouse to deploy the basic service components of the cloud data warehouse on the kubernetes cloud native platform. The basic service components include the cloud service front-end and back-end components and the kubernetes node management components.

[0006] Using the cloud service front-end and back-end components and the kubernetes node management component to create a database metadata management component and a database coordination node component of the target tenant;

[0007] The database computing node component of the target tenant is created by using the cloud service front-end and back-end components, the kubernetes node management component and the database coordination node component of the target tenant.

[0008] In a second aspect, the present application provides a cloud data warehouse automatic deployment device, comprising:

[0009] The basic component deployment module is used to deploy the basic service components of the cloud data warehouse on the kubernetes cloud native platform using the helm chart installation package of the cloud data warehouse. The basic service components include the cloud service front-end and back-end components and the kubernetes node management components.

[0010] A first creation module is used to create a database metadata management component and a database coordination node component of a target tenant by using the cloud service front-end and back-end components and the kubernetes node management component;

[0011] The second creation module is used to create the database computing node component of the target tenant by using the cloud service front-end and back-end components, the kubernetes node management component and the database coordination node component of the target tenant.

[0012] In a third aspect, the present application provides a terminal comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the steps of the method described in the first aspect or any possible implementation of the first aspect are implemented.

[0013] In a fourth aspect, the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the steps of the method described in the first aspect or any possible implementation of the first aspect.

[0014] The present application provides a method, device, terminal and storage medium for automatic deployment of cloud data warehouse, which deploys the basic service components of cloud data warehouse on Kubernetes cloud native platform by using the helm chart installation package of cloud data warehouse, the basic service components include cloud service front-end and back-end components and Kubernetes node management components; creates the database metadata management component and database coordination node component of the target tenant by using the cloud service front-end and back-end components and Kubernetes node management components; creates the database computing node component of the target tenant by using the cloud service front-end and back-end components, Kubernetes node management components and database coordination node components of the target tenant. The present application realizes the automated creation of each component of cloud data warehouse product to the maximum extent through the basic service components of cloud data warehouse deployed on Kubernetes cloud native platform, which saves the trouble of manual deployment, and also avoids the error-prone problems in traditional manual deployment to a large extent, which greatly improves the ease of use, practicality and portability of cloud data warehouse products. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0016] Figure 1 It is a flow chart for implementing the cloud data warehouse automatic deployment method provided in the embodiment of the present application;

[0017] Figure 2 It is a schematic diagram of the structure of the helm chart installation package provided in an embodiment of the present application;

[0018] Figure 3 It is a flow chart for creating a database metadata management component and a database coordination node component provided in an embodiment of the present application;

[0019] Figure 4 It is a flowchart for creating a database computing node component provided in an embodiment of the present application;

[0020] Figure 5 It is a structural diagram of a cloud data warehouse automatic deployment device provided in an embodiment of the present application;

[0021] Figure 6 It is a schematic diagram of a terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0022] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0023] In order to make the purpose, technical solutions and advantages of the present application clearer, specific embodiments will be described below in conjunction with the accompanying drawings.

[0024] Figure 1 The implementation flow chart of the cloud data warehouse automatic deployment method provided in the embodiment of the present application is detailed as follows:

[0025] In step 101, the basic service components of the cloud data warehouse are deployed on the Kubernetes cloud native platform using the helm chart installation package of the cloud data warehouse. The basic service components include cloud service front-end and back-end components and Kubernetes node management components.

[0026] In this embodiment, the cloud data warehouse is a GBase cloud data warehouse (GBase Cloud DataWarehouse, GCDW).

[0027] In the embodiment of the present application, the helm chart installation package of the GCDW cloud data warehouse is used to deploy two basic service components of GCDW on the Kubernetes cloud native platform, namely the cloud service front-end and back-end components (GCDW cloudfrontend and backend) and the Kubernetes node management component (gcdw operator).

[0028] In a possible implementation, before deploying the basic service components of the cloud data warehouse on the kubernetes cloud native platform using the helm chart installation package of the cloud data warehouse, the method may further include:

[0029] Get the Docker images of all components of the cloud data warehouse;

[0030] Accordingly, using the helm chart installation package of the cloud data warehouse to deploy the basic service components of the cloud data warehouse on the kubernetes cloud native platform, you can include:

[0031] Use the helm chart installation package of the cloud data warehouse to call the Docker image to deploy the basic service components of the cloud data warehouse on the kubernetes cloud native platform.

[0032] Among them, a Docker image is a lightweight, independent, executable software package that contains everything needed to run an application: code, runtime environment, system tools, and libraries. Docker images are immutable, and any changes will create a new image.

[0033] Optionally, according to the characteristics of the GCDW product, create a Docker image for each component, so that when creating the corresponding component, you can select the corresponding Docker image and start it.

[0034] Accordingly, use the GCDW helm chart installation package to call each of the Docker images created above and deploy the basic service components of GCDW on the Kubernetes cloud native platform.

[0035] In a possible implementation, the Docker image may include a cloud service front-end component image, a cloud service back-end component image, a kubernetes node management component image, and a database server image of a cloud data warehouse;

[0036] The database server image is used to start the corresponding first component with different startup parameters. The first component includes a database metadata management component, a database coordination node component and a database computing node component.

[0037] Optionally, the Docker image created in this embodiment includes the following:

[0038] 1) A cloud service front-end component image of GCDW: gcdw-saas-frontend;

[0039] 2) A cloud service backend component image of GCDW: gcdw-saas-backend;

[0040] 3) A Kubernetes node management component image of GCDW: gcdw-operator;

[0041] 4) GCDE's database metadata management component, database coordination node component, and database computing node component share a database server image: gcdw-database-server, and start the corresponding components through different startup parameters.

[0042] The corresponding startup parameters are as follows:

[0043] (1) The startup parameters of the database metadata management component are: startup.sh --gcware;

[0044] (2) The startup parameters of the database coordination node component are: startup.sh --coordinator;

[0045] (3) The startup parameters of the database computing node component are: startup.sh --warehouse.

[0046] In a possible implementation, before deploying the basic service components of the cloud data warehouse on the kubernetes cloud native platform using the helm chart installation package of the cloud data warehouse, the method may further include:

[0047] Get the template file of the cloud data warehouse helm chart installation package written by the helm automation tool;

[0048] Use the template file to build the helm chart installation package of the cloud data warehouse.

[0049] Among them, the helm automation tool is an automation tool for deploying applications on the kubernetes cloud native platform, which can easily deploy complex applications with many components.

[0050] Optionally, after creating the Docker images of the GCDW components, use the helm automation tool to write the last file of the GCDW helm chart installation package to form a deployed helm chart installation package, where the helm chart installation package includes the cloud service front-end and back-end components and the kubernetes node management components.

[0051] For example, the structure of the helm chart installation package can refer to Figure 2 , including the chart.yaml configuration file and the value.yaml configuration file, as well as the template files of the GCDW cloud service front-end and back-end components and the template files of the kubernetes node management component (i.e., gcdw operator).

[0052] Template files for cloud service front-end and back-end components include gcdw-cloud-frontend-cm.yaml, gcdw-cloud-frontend-cm.yaml, gcdw-cloud-backed-st.yaml, gcdw-cloud-backed-cm.yaml, and gcdw-cloud-rbac.yaml.

[0053] Template files for kubernetes node management components include gcdw-operator-depoy.yaml, gcdw-operator-rbac.yaml, and gcdw-operator-cm.yanl.

[0054] In a possible implementation, the helm chart installation package may include the value.yaml configuration file. The basic service components of the cloud data warehouse are deployed on the kubernetes cloud native platform using the helm chart installation package of the cloud data warehouse, which may include:

[0055] Get the cloud data warehouse deployment parameters of the value.yaml configuration file in the helm chart package related to the kubernetes cloud native platform. The cloud data warehouse deployment parameters include the image name of each component in the cloud data warehouse, the number of nodes of each component, the core configuration parameters of each component, and the resource limit parameters of each component;

[0056] Use the cloud data warehouse deployment parameters and helm commands to deploy the basic service components of the cloud data warehouse.

[0057] Optionally, use the created helm chart installation package to deploy GCDW's related cloud service front-end and back-end service components and Kubernetes node management components on the Kubernetes cloud native platform. The specific steps are as follows:

[0058] First, users fill in the relevant gcdw deployment parameters in the value.yaml configuration file in the elm chart installation package according to the actual situation of the current kubernetes cloud native platform. The most important mandatory deployment parameters include the following:

[0059] 1) The image names of GCDW components, namely: the front-end component image name option in the gcdw-cloud-frontend-st.yaml file, the back-end component image name option in the gcdw-cloud-backed-st.yaml file, the node management component image name option in the gcdw-operator-deploy.yaml file, and the database metadata management component, database coordination node component, and database computing node component image name options in the gcdw-operator-cm file;

[0060] 2) The number of nodes of each GCDW component, namely the number of nodes of the front-end component in the gcdw-cloud-frontend-st.yaml file, the number of nodes of the back-end component in the gcdw-cloud-backed-st.yaml file, the number of nodes of the node management component in the gcdw-operator-deploy.yaml file, and the number of nodes of the database metadata management component, the coordination node component, and the computing node component in the gcdw-operator-cm file;

[0061] 3) The core configuration parameters of each GCDW component, namely the front-end component related configuration options in the gcdw-cloud-frontend-cm.yaml file, the back-end component related configuration options in the gcdw-cloud-backed-cm.yaml file, the node management component related configuration options in the gcdw-operator-cm.yaml file, and the database metadata management component, database coordination node component, and database computing node component related configuration options in the gcdw-operator-cm file;

[0062] 4) Resource limit parameters for each GCDW component, namely, the resource limit related options for the front-end component in the gcdw-cloud-frontend-st.yaml file, the resource limit related options for the back-end component in the gcdw-cloud-backed-st.yaml file, the resource limit related options for the node management component in the gcdw-operator-deploy.yaml file, and the resource limit related options for the database metadata management component, database coordination node component, and database computing node component in the gcdw-operator-cm file.

[0063] After filling in the GCDW deployment parameters in the value.yaml configuration file, you can use the helm command to deploy the basic service components of GCDW.

[0064] For example, deploy an application named gcdw in the namespace gcdw-sysytem of the Kubernetes cloud native platform:

[0065] Operation example: helm install gcdw. / chart -n gcdw-system

[0066] After deploying the gcdw helm chart, you can view the basic service components of gcdw in the namespace gcdw-system, including all resource objects of the cloud service front-end and back-end components (gcdw cloud frontend and backend) and the kubernetes node management component (gcdw operator), including statefulset, deployment, pod, service, configmap, etc.

[0067] In step 102, the database metadata management component and database coordination node component of the target tenant are created using the cloud service front-end and back-end components and the kubernetes node management component.

[0068] In the embodiment of the present application, the cloud service front-end and back-end components and the kubernetes node management components deployed in step 101 are used to create database metadata management components and database coordination node components for each target tenant.

[0069] In a possible implementation, the cloud service front-end and back-end components may include a cloud service front-end component and a cloud service back-end component. Using the cloud service front-end and back-end components and the kubernetes node management component to create a database metadata management component and a database coordination node component of a target tenant may include:

[0070] Get the request of the target tenant;

[0071] Use the cloud service front-end component to send the target tenant's request to the cloud service back-end component, and use the cloud service back-end component to send the target user's request to the kubernetes node management component;

[0072] In the kubernetes node management component, the database metadata management component and database coordination node component of the target tenant are created using the parameters in the request of the target tenant.

[0073] Optionally, after obtaining the request of the target tenant, this embodiment passes through the cloud service front-end component and the cloud service back-end component respectively, and after reaching the kubernetes node management component, it uses the parameters in the target tenant's request to create the database metadata management component and database coordination node component of the target tenant.

[0074] For example, refer to Figure 3 The steps to create a tenant's database metadata management component and database coordination node component are as follows:

[0075] Step 3.1, log in to the GCDW cloud service front-end web interface (i.e., cloud service front-end component), and register a GCDW tenant through the tenant registration page;

[0076] Step 3.2: The cloud service front-end component sends a request to create a GCDW tenant to the cloud service back-end component.

[0077] In step 3.3, the cloud service backend component calls the tenant management process in the component to send a request to the kubernetes api-server service [l xl1] to create a gcdw coordiantor crd instance [l xl2], that is, calls the relevant k8s api to send a request to the k8s platform; the kubernetes api-server service is the communication gateway service of the kubernetes cloud native platform, that is, the k8s api-server; the gcdw coordiantor crd instance is a custom resource instance of the cloud data warehouse management node and coordination node;

[0078] Step 3.4, kubernetes api-server forwards the relevant request message to the kubernetes node management component (gcdw operator);

[0079] Step 3.5, after receiving the above request, the kubernetes node management component calls the gcdwcoordinator crd controller service [l xl3] in the component, creates the database metadata management component and database coordination node component of the tenant and all other related resources involved according to the relevant parameters in the request, and returns the relevant resource information to the cloud service backend component;

[0080] In step 3.6, the cloud service backend component returns the database metadata management component and database coordination node component information created in the above steps to the cloud service front-end web interface. Users can query the relevant information of the tenant's database metadata management component and database coordination node component through the page.

[0081] In step 103, the database computing node component of the target tenant is created by using the cloud service front-end and back-end components, the kubernetes node management component and the database coordination node component of the target tenant.

[0082] In an embodiment of the present application, the warehouse service of the cloud service front-end and back-end components and the kubernetes node management component created in step 101 and the database coordination node component of the target tenant created in step 102 are used to create relevant resources of the database computing node component of the target tenant.

[0083] In a possible implementation, the cloud service front-end and back-end components may include a cloud service front-end component and a cloud service back-end component. Using the cloud service front-end and back-end components, the kubernetes node management component, and the database coordination node component of the target tenant to create the database computing node component of the target tenant may include:

[0084] Obtain a request for creating a database computing node component of a target tenant, and use the cloud service front-end component to send the request for creating the database computing node component to the cloud service back-end component;

[0085] Using the cloud service backend component, converting the request to create the database computing node component of the target tenant into a corresponding SQL statement, and sending the SQL statement to the database coordination node component of the target tenant;

[0086] After receiving the SQL statement, the database coordination node component sends a request to create a database computing node component to the kubernetes node management component;

[0087] In the Kubernetes node management component, the database computing node component of the target user is created using the parameters in the request to create the database computing node component of the target tenant.

[0088] Optionally, after this embodiment obtains a request to create a database computing node component for the target tenant, the cloud service front-end component is used to send the request to the cloud service back-end component, and then the cloud service back-end component converts the request into a corresponding SQL statement, and sends the SQL statement to the database coordination node component of the target user, and uses the database coordination node component to send the request to the kubernetes node management component, and uses the parameters in the request to create the database computing node component of the target tenant.

[0089] For example, refer to Figure 4 , the steps to create a tenant's database compute node component are as follows:

[0090] Step 4.1, log in to the GCDW cloud service front-end web interface (i.e., cloud service front-end component), and log in to the GCDW tenant page that has been registered before (i.e., the GCDW tenant registered in step 3.1);

[0091] Step 4.2, creating a database computing node component request for the tenant in the tenant page, and the cloud service front-end component sends the request to create the database computing node component for the tenant to the cloud service back-end component;

[0092] Step 4.3, the cloud service backend component converts the request to create the tenant's database computing node component into a corresponding SQL statement, and forwards the SQL statement to the database service process of the tenant's database coordination node component (gcdw coordiantor);

[0093] Step 4.4, after receiving the corresponding SQL statement, the database service process of the database coordination node component of the tenant sends a request to create a gcdw warehouse crd instance [l xl4] to the kubernetes api-server service (i.e., k8s api-server), that is, receives the relevant SQL statement and calls the relevant k8s api to send a request to the k8s platform; wherein, the gcdw warehouse crd instance is a custom resource instance of the cloud data warehouse computing node;

[0094] Step 4.5, the kubernetes api-server service forwards the relevant request message to the kubernetes node management component (i.e., gcdw operator);

[0095] Step 4.6: After receiving the above request, the kubernetes node management component calls the gcdw warehousecrd controller component [l xl5] in the component, creates the relevant resources of the tenant's database computing node component according to the relevant parameters in the request, and returns the relevant resource information to the database service process of the tenant's database coordination node component;

[0096] Step 4.7, the database service process of the tenant's database coordination node component returns the resource information of the database computing node component to the cloud service backend component;

[0097] In step 4.8, the cloud service backend component returns the resource information of the tenant's database computing node component created in the above step to the cloud service front-end web interface, and the user can query the relevant resource information of the tenant's database computing node component through the page.

[0098] The present application provides a method for automatic deployment of a cloud data warehouse, which deploys the basic service components of the cloud data warehouse on the Kubernetes cloud native platform by using the helm chart installation package of the cloud data warehouse, wherein the basic service components include cloud service front-end and back-end components and Kubernetes node management components; creates the database metadata management component and database coordination node component of the target tenant by using the cloud service front-end and back-end components and Kubernetes node management components; creates the database computing node component of the target tenant by using the cloud service front-end and back-end components, Kubernetes node management components and the database coordination node component of the target tenant. The present application realizes the automated creation of each component of the cloud data warehouse product to the maximum extent through the basic service components of the cloud data warehouse deployed on the Kubernetes cloud native platform, which saves the trouble of manual deployment, and also largely avoids the error-prone problems in traditional manual deployment, greatly improving the ease of use, practicality and portability of the cloud data warehouse product.

[0099] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0100] The following is an embodiment of the device of the present application. For details not described in detail, please refer to the corresponding method embodiment described above.

[0101] Figure 5 The following is a schematic diagram showing the structure of the cloud data warehouse automatic deployment device provided in the embodiment of the present application. For the sake of convenience, only the parts related to the embodiment of the present application are shown, which are described in detail as follows:

[0102] like Figure 5 As shown, the cloud data warehouse automatic deployment device 5 includes:

[0103] A basic component deployment module 51 is used to deploy the basic service components of the cloud data warehouse on the Kubernetes cloud native platform using the helm chart installation package of the cloud data warehouse. The basic service components include the cloud service front-end and back-end components and the Kubernetes node management components.

[0104] A first creation module 52 is used to create a database metadata management component and a database coordination node component of a target tenant by using a cloud service front-end and back-end component and a kubernetes node management component;

[0105] The second creation module 53 is used to create a database computing node component of the target tenant by using the cloud service front-end and back-end components, the kubernetes node management component and the database coordination node component of the target tenant.

[0106] The present application provides a cloud data warehouse automatic deployment device, which deploys the basic service components of the cloud data warehouse on the Kubernetes cloud native platform by using the helm chart installation package of the cloud data warehouse, the basic service components include cloud service front-end and back-end components and Kubernetes node management components; creates the database metadata management component and database coordination node component of the target tenant by using the cloud service front-end and back-end components and Kubernetes node management components; creates the database computing node component of the target tenant by using the cloud service front-end and back-end components, Kubernetes node management components and the database coordination node component of the target tenant. The present application realizes the automated creation of each component of the cloud data warehouse product to the maximum extent through the basic service components of the cloud data warehouse deployed on the Kubernetes cloud native platform, saves the trouble of manual deployment, and largely avoids the error-prone problems in traditional manual deployment, greatly improving the ease of use, practicality and portability of the cloud data warehouse product.

[0107] In a possible implementation, the device may further include an image creation module, and the image creation module may be used to:

[0108] Get the Docker images of all components of the cloud data warehouse;

[0109] Accordingly, the basic component deployment module can be used to:

[0110] Use the helm chart installation package of the cloud data warehouse to call the Docker image to deploy the basic service components of the cloud data warehouse on the kubernetes cloud native platform.

[0111] In a possible implementation, the Docker image may include a cloud service front-end component image, a cloud service back-end component image, a kubernetes node management component image, and a database server image of a cloud data warehouse;

[0112] The database server image is used to start the corresponding first component with different startup parameters. The first component includes a database metadata management component, a database coordination node component and a database computing node component.

[0113] In a possible implementation, the device may further include an installation package creation module, and the installation package creation module may be used to:

[0114] Get the template file of the cloud data warehouse helm chart installation package written by the helm automation tool;

[0115] Use the template file to build the helm chart installation package of the cloud data warehouse.

[0116] In one possible implementation, the helm chart installation package may include a value.yaml configuration file, and the basic component deployment module may be used to:

[0117] Get the cloud data warehouse deployment parameters of the value.yaml configuration file in the helm chart package related to the kubernetes cloud native platform. The cloud data warehouse deployment parameters include the image name of each component in the cloud data warehouse, the number of nodes of each component, the core configuration parameters of each component, and the resource limit parameters of each component;

[0118] Use the cloud data warehouse deployment parameters and helm commands to deploy the basic service components of the cloud data warehouse.

[0119] In a possible implementation, the cloud service front-end and back-end components may include a cloud service front-end component and a cloud service back-end component, and the first creation module may be used to:

[0120] Get the request of the target tenant;

[0121] Use the cloud service front-end component to send the target tenant's request to the cloud service back-end component, and use the cloud service back-end component to send the target user's request to the kubernetes node management component;

[0122] In the kubernetes node management component, the database metadata management component and database coordination node component of the target tenant are created using the parameters in the request of the target tenant.

[0123] In a possible implementation, the cloud service front-end and back-end components may include a cloud service front-end component and a cloud service back-end component, and the second creation module may be used to:

[0124] Obtain a request for creating a database computing node component of a target tenant, and use the cloud service front-end component to send the request for creating the database computing node component to the cloud service back-end component;

[0125] Using the cloud service backend component, converting the request to create the database computing node component of the target tenant into a corresponding SQL statement, and sending the SQL statement to the database coordination node component of the target tenant;

[0126] After receiving the SQL statement, the database coordination node component sends a request to create a database computing node component to the kubernetes node management component;

[0127] In the Kubernetes node management component, the database computing node component of the target user is created using the parameters in the request to create the database computing node component of the target tenant.

[0128] Figure 6 is a schematic diagram of a terminal provided in an embodiment of the present application. Figure 6 As shown, the terminal 6 of this embodiment includes: a processor 60, a memory 61, and a computer program 62 stored in the memory 61 and executable on the processor 60. When the processor 60 executes the computer program 62, the steps in the above-mentioned various cloud data warehouse automatic deployment method embodiments are implemented, such as Figure 1 Alternatively, when the processor 60 executes the computer program 62, the functions of each module / unit in the above-mentioned device embodiments are realized, for example Figure 5 The functions of each module are shown.

[0129] Exemplarily, the computer program 62 may be divided into one or more modules / units, which are stored in the memory 61 and executed by the processor 60 to complete the present application. The one or more modules / units may be a series of computer program instruction segments capable of completing specific functions, which are used to describe the execution process of the computer program 62 in the terminal 6. For example, the computer program 62 may be divided into Figure 5 The modules shown.

[0130] The terminal 6 may be a computing device such as a desktop computer, a notebook, a PDA, or a cloud server. The terminal 6 may include, but is not limited to, a processor 60 and a memory 61. Those skilled in the art will appreciate that Figure 6It is only an example of terminal 6 and does not constitute a limitation on terminal 6. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the terminal may also include input and output devices, network access devices, buses, etc.

[0131] The processor 60 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0132] The memory 61 may be an internal storage unit of the terminal 6, such as a hard disk or memory of the terminal 6. The memory 61 may also be an external storage device of the terminal 6, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the terminal 6. Further, the memory 61 may also include both an internal storage unit of the terminal 6 and an external storage device. The memory 61 is used to store the computer program and other programs and data required by the terminal. The memory 61 may also be used to temporarily store data that has been output or is to be output.

[0133] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0134] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0135] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0136] In the embodiments provided in the present application, it should be understood that the disclosed devices / terminals and methods can be implemented in other ways. For example, the device / terminal embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0137] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0138] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0139] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by the processor, the steps of the above-mentioned various cloud data warehouse automatic deployment method embodiments can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device that can carry the computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practices in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practices, computer-readable media does not include electrical carrier signals and telecommunication signals.

[0140] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A cloud data warehouse automatic deployment method, characterized in that: include: Use the helm chart installation package of the cloud data warehouse to deploy the basic service components of the cloud data warehouse on the kubernetes cloud native platform. The basic service components include the cloud service front-end and back-end components and the kubernetes node management components. Using the cloud service front-end and back-end components and the kubernetes node management component to create a database metadata management component and a database coordination node component of the target tenant; Create a database computing node component of the target tenant using the cloud service front-end and back-end components, the kubernetes node management component and the database coordination node component of the target tenant; The cloud service front-end and back-end components include a cloud service front-end component and a cloud service back-end component, and the step of using the cloud service front-end and back-end components, the kubernetes node management component and the database coordination node component of the target tenant to create the database computing node component of the target tenant includes: Obtaining a request for creating a database computing node component of the target tenant, and using the cloud service front-end component to send the request for creating the database computing node component to the cloud service back-end component; Using the cloud service backend component to convert the request to create the database computing node component of the target tenant into a corresponding SQL statement, and sending the SQL statement to the database coordination node component of the target tenant; After receiving the SQL statement, using the database coordination node component to send the request to create the database computing node component to the kubernetes node management component; In the kubernetes node management component, the database computing node component of the target tenant is created using the parameters in the request for creating the database computing node component of the target tenant.

2. The cloud data warehouse automatic deployment method according to claim 1, characterized in that: Before deploying the basic service components of the cloud data warehouse on the kubernetes cloud native platform using the helm chart installation package of the cloud data warehouse, the method further includes: Obtain Docker images of all components of the cloud data warehouse; Accordingly, the basic service components of the cloud data warehouse are deployed on the kubernetes cloud native platform using the helm chart installation package of the cloud data warehouse, including: The helm chart installation package of the cloud data warehouse is used to call the Docker image to deploy the basic service components of the cloud data warehouse on the kubernetes cloud native platform.

3. The cloud data warehouse automatic deployment method according to claim 2, characterized in that: The Docker image includes a cloud service front-end component image, a cloud service back-end component image, a kubernetes node management component image and a database server image of the cloud data warehouse; The database server image is used to start the corresponding first component with different startup parameters, and the first component includes a database metadata management component, a database coordination node component and a database computing node component.

4. The cloud data warehouse automatic deployment method according to claim 1, characterized in that: Before deploying the basic service components of the cloud data warehouse on the kubernetes cloud native platform using the helm chart installation package of the cloud data warehouse, the method further includes: Obtain a template file of the cloud data warehouse helm chart installation package written by the helm automation tool; The template file is used to build the helm chart installation package of the cloud data warehouse.

5. The cloud data warehouse automatic deployment method according to claim 1, characterized in that: The helm chart installation package includes a value.yaml configuration file. The basic service components of the cloud data warehouse are deployed on the kubernetes cloud native platform using the helm chart installation package of the cloud data warehouse, including: Obtain cloud data warehouse deployment parameters of the value.yaml configuration file in the helm chart package related to the kubernetes cloud native platform, wherein the cloud data warehouse deployment parameters include the image name of each component in the cloud data warehouse, the number of nodes of each component, the core configuration parameters of each component, and the resource limit parameters of each component; The basic service components of the cloud data warehouse are deployed using the cloud data warehouse deployment parameters and helm commands.

6. The cloud data warehouse automatic deployment method according to claim 1, characterized in that: The cloud service front-end and back-end components include a cloud service front-end component and a cloud service back-end component. The use of the cloud service front-end and back-end components and the kubernetes node management component to create a database metadata management component and a database coordination node component of a target tenant includes: Obtaining a request for the target tenant; Using the cloud service front-end component to send the target tenant's request to the cloud service back-end component, and using the cloud service back-end component to send the target tenant's request to the kubernetes node management component; In the kubernetes node management component, the database metadata management component and the database coordination node component of the target tenant are created using the parameters in the request of the target tenant.

7. A cloud data warehouse automatic deployment device, characterized in that: include: The basic component deployment module is used to deploy the basic service components of the cloud data warehouse on the kubernetes cloud native platform using the helm chart installation package of the cloud data warehouse. The basic service components include the cloud service front-end and back-end components and the kubernetes node management components. A first creation module is used to create a database metadata management component and a database coordination node component of a target tenant by using the cloud service front-end and back-end components and the kubernetes node management component; A second creation module is used to create a database computing node component of the target tenant by using the cloud service front-end and back-end components, the kubernetes node management component and the database coordination node component of the target tenant; The cloud service front-end and back-end components include a cloud service front-end component and a cloud service back-end component, and the second creation module is specifically used for: Obtaining a request for creating a database computing node component of the target tenant, and using the cloud service front-end component to send the request for creating the database computing node component to the cloud service back-end component; Using the cloud service backend component to convert the request to create the database computing node component of the target tenant into a corresponding SQL statement, and sending the SQL statement to the database coordination node component of the target tenant; After receiving the SQL statement, using the database coordination node component to send the request to create the database computing node component to the kubernetes node management component; In the kubernetes node management component, the database computing node component of the target tenant is created using the parameters in the request for creating the database computing node component of the target tenant.

8. A terminal comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the cloud data warehouse automatic deployment method as described in any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the cloud data warehouse automatic deployment method as described in any one of claims 1 to 6 are implemented.

Images