TW202232395A - Cloud platform management method, apparatus, electronic device, and storage medium - Google Patents

Abstract

This invention discloses a cloud platform management method and its apparatus. The method includes: obtaining a cloud service function, dividing the cloud service function into a multiple of meta-function modules, and configuring a multiple of meta-components corresponding to the meta-function modules; obtaining customer information, retrieving the required meta-function modules and the corresponding meta-components based on the customer information; obtaining a deployment file according to the called meta-function modules and the corresponding meta components; sending the deployment file to a multiple of corresponding websites to operate the cloud service function. This method can quickly complete the purchase, customization, and deployment of the cloud service functions and realize the privatization of industrial clouds according to the needs of the enterprises, as well as realizing the flexible management of the private cloud service functions.

Description

Cloud platform management method, device, electronic device and storage medium

The present application relates to the technical field of cloud platforms, and in particular, to the field of cloud platform management.

Cloud platform refers to services based on hardware resources and software resources, providing computing, network and storage capabilities. It can provide cloud services for application development. For example, a developer of a new software as an application service conducts research and development on a cloud platform, and the direct users of the cloud platform are developers rather than ordinary users, which provides developers with a stable development environment. Financial enterprises increasingly need to deploy IT systems on industry cloud platforms to improve system stability and reduce operating costs. At the same time, financial enterprises also need to meet the operational compliance and data requirements of IT systems under the requirements of strong supervision. compliance etc.

An industry cloud is a cloud platform that is established and maintained by an organization that plays a leading role or masters key resources in an industry or a certain region, and provides paid or unpaid services to the industry or related organizations and the public in an open or semi-open manner. Most existing industry clouds are deployed in the form of private clouds or hybrid clouds. Private clouds are built for single use by one customer, thus providing the most effective control over data, security, and quality of service. However, the private cloud platform requires technicians and operation and maintenance personnel to fully grasp the use of the entire cloud computing system, resulting in high labor costs, high development and operation and maintenance costs for different users to customize functions, and a long cycle. Hybrid cloud integrates public cloud and private cloud, stores data in private cloud, but at the same time hopes to obtain computing resources of public cloud. It is the main mode and development direction of cloud computing in recent years. However, the hybrid cloud platform only realizes the centralized purchase of private cloud and public cloud service products on the same platform. Customers can use cloud products, such as cloud servers, databases, etc., but cannot manage various products on the platform. Do not do the operation and maintenance of cloud products.

The embodiments of the present application provide a cloud platform management method, device, electronic device, and storage medium to solve the problems existing in the related technologies, and the technical solutions are as follows:

In a first aspect, an embodiment of the present application provides a cloud platform management method, including:

Obtain cloud service functions, split cloud service functions into multiple meta-function modules, and configure multiple meta-elements corresponding to the meta-function modules;

Obtain customer information, and retrieve the required meta-function modules and corresponding meta-components according to the customer information;

Obtain the deployment file according to the called meta-function module and the corresponding meta-component;

Send deployment files to corresponding multiple websites to run cloud service functions.

In one embodiment, a plurality of meta-function modules constitute a meta-function library, and a plurality of corresponding meta-components constitute a meta-component library; the required meta-function modules and corresponding meta-components are retrieved according to customer information, including:

Obtain customer information, including meta-function requirement information;

According to the meta-function requirement information, the corresponding meta-function module is called from the meta-function library, and the corresponding meta-component is called from the meta-component library.

In one embodiment, it also includes:

Delete the duplicated meta-components in the recalled meta-components to determine the supporting meta-components.

In one embodiment, the deployment file is obtained according to the retrieved multiple meta-function modules and corresponding multiple meta-components, including:

Configure the parameters of the called meta-function modules and meta-components to obtain the meta-function setting file and the meta-component setting file;

Obtain the component deployment file according to the called meta-component;

The deployment file includes a meta-function configuration file, a meta-component configuration file, and a component deployment file.

In one embodiment, it also includes:

Detect and verify the operation of the cloud service functions deployed on multiple websites, and if the verification fails, return to the step of configuring multiple required meta-function modules and corresponding multiple meta-elements according to the customer information.

In one embodiment, the cloud service function includes a user management function and a billing function corresponding to the operation type;

The meta-function modules obtained by splitting the billing function include: fund account module, order management module, bill management module, contract management module, quota management module, discount module, and voucher module;

The meta-function modules obtained by splitting the user management function include: account information management module, fund account management module, account permission module, qualification authentication module, sub-account management module, user group management module, Permission management module.

In a second aspect, a cloud platform management device is provided, including:

The function splitting module is used to obtain cloud service functions and split cloud service functions into multiple meta-function modules;

A meta-function component configuration module, which configures the meta-component corresponding to the meta-function module;

Meta-functional component retrieval module, used to obtain customer information, and retrieve the required meta-functional modules and corresponding meta-components according to the customer information;

The deployment file obtaining module is used to obtain the deployment file according to the called multiple meta-function modules and corresponding multiple meta-components;

The function operation module is used to send the deployment file to the corresponding multiple websites to run the cloud service function.

In one embodiment, a plurality of meta-function modules form a meta-function library, and a plurality of corresponding meta-elements form a meta-element library; the meta-function element retrieval module includes:

The customer information acquisition sub-module is used to acquire customer information, including the meta-function requirement information;

The sub-module is called, which is used to call the corresponding meta-function module from the meta-function library according to the meta-function requirement information, and call the corresponding meta-component from the meta-component library.

In one embodiment, the meta-function element retrieval module further includes:

The support element determination sub-module is used to delete the repeated element elements in the retrieved element elements to determine the support element elements.

In one embodiment, the deployment file acquisition module includes:

The configuration file generation sub-module is used to configure the parameters of the called meta-function modules and meta-elements to obtain the meta-function configuration file and the meta-element configuration file;

The component deployment file acquisition sub-module is used to obtain the component deployment file according to the called meta-component;

The deployment file includes a meta-function configuration file, a meta-component configuration file, and a component deployment file.

In one embodiment, it also includes:

The function verification module is used to test and verify the operation of the cloud service functions deployed on multiple websites. If the verification fails, it will return to execute multiple meta-function modules and corresponding multiple meta-function modules required for configuration based on customer information. component steps.

In one embodiment, the cloud service function includes a user management function and a billing function corresponding to the operation type;

The meta-function modules obtained by splitting the billing function include: fund account module, order management module, bill management module, contract management module, quota management module, discount module, and voucher module;

The meta-function modules obtained by splitting the user management function include: account information management module, fund account management module, account permission module, qualification authentication module, sub-account management module, user group management module, Permission management module.

On the third-party side, an electronic device is provided, including:

at least one processor; and memory in communication with the at least one processor;

The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can execute any one of the above methods.

In a fourth aspect, a non-transitory computer-readable storage medium storing computer instructions is provided, and the computer instructions are used to cause a computer to execute any of the above methods.

An embodiment in the above application has the following advantages or beneficial effects: by modularizing the cloud service function, obtaining a plurality of meta-functions, and configuring the corresponding meta-elements, the required meta-function modules can be retrieved for different customer information. Groups and meta-components to customize functions, and then send deployment files to various websites to run cloud service functions. Quickly complete the purchase, customization, and deployment of cloud service functions, realize industry cloud privatization according to enterprise needs, and realize scalable management of private cloud service functions.

Other effects of the above-mentioned optional manners will be described below with reference to specific embodiments.

Exemplary embodiments of the present application are described below with reference to the accompanying drawings, which include various details of the embodiments of the present application to facilitate understanding, and should be considered as exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted from the following description for clarity and conciseness.

As shown in Figure 1, the Outposts product from AWS (Amazon Cloud Services) handles the setup and management of hybrid cloud infrastructure for consumers. First, deploy new websites locally, and then provide customers with a complete set of cloud services through Outposts, including website operation and maintenance. However, the AWS Outposts cloud platform is a public cloud platform and cannot provide the services of a private cloud platform for different customers. In order to complete industry cloud privatization according to customer needs, as shown in FIG. 2 , this embodiment provides a cloud platform management method, and the specific steps include:

Step S110: obtaining the cloud service function, splitting the cloud service function into multiple meta-function modules, and configuring the meta-elements corresponding to the meta-function modules;

Step S120: acquiring customer information, and retrieving required meta-function modules and corresponding meta-components according to the customer information;

Step S130: obtaining a deployment file according to the called meta-function module and corresponding meta-element;

Step S140: Send the deployment file to the corresponding multiple websites to run the cloud service function.

In one example, as shown in Figure 3, a hybrid cloud platform is provided, with the cloud console as the public cloud platform, and the customer consoles (for example, the customer 1 console and the customer 2 console) and the sharded cloud management platform as the private cloud platform , the customer console (for example, customer 3 console) can also stand alone as a private cloud platform. Customers can access website 1 and website 2, website 3 and website 4 through the Internet interface displayed by the cloud console (for example, externally exposed individual function variable names). Website 3 and Website 4 can also be accessed through the customer console and the shard cloud management platform. Only the cloud resource services of this website are provided externally, and the services provided externally are the functions that have been customized as described above. It is also possible to access the website 5 only through the customer console. It should be pointed out that the number of websites provided in this embodiment includes but is not limited to website 1 to website 5, and there may be more websites. The website is the customer's computer room, which can include multiple servers.

When customers access through the customer console and the shard cloud management platform, the customer console is a console customized for different customers, and the customer console only displays the information of website 3 or website 4. For example, customer 1 can be a car company, and the customer can only access the website 3 deployed by this car company through the customized function modules (purchasing modules, etc.) displayed on the Internet interface of customer 1's console. Customer 2 can be a payment institution, and the customer can only access the website 4 deployed by this payment structure through the customized function modules (payment modules, etc.) displayed on the Internet interface of Customer 2's console. The console of Customer 3 is no longer transferred through the sharded cloud management platform, so it no longer has the ability to customize functions. At the same time, Website 5 also enables Customer 3 to have completely independent service capabilities. Website 5 can be switched back to website 3 and website 4 as needed.

As shown in Figure 4, in the sharded cloud management platform, cloud service functions can be disassembled according to usage scenarios and logical deployment, and cloud service functions can be divided into various types, such as operation type, operation and maintenance type, and product type. Multiple cloud service functions can be included in each type. For example, the operation type may include billing function (function 1) and user management function (function 2), etc., the operation and maintenance type may include computing function (function 3) and storage function (function 4), etc., and the product may include monitoring Functions (Function 5) and Automation Functions (Function 6), etc. The cloud service functions are split to obtain multiple meta-function modules. The dismantling is subdivided as much as possible, each meta-function module is an independent function, and the meta-function is the smallest unit of function configuration, which is a function function table independently configured on the page. Each meta-function is implemented by a number of specific meta-elements and support elements. From the technical framework, each meta-functional module is disassembled into independently deployable program execution units, and the same meta-functional module is divided into multiple sub-components from the technical logic, which are called meta-components. Each element is the smallest unit that can be independently deployed and configured, and the elements are decoupled. Organize the meta-functions and meta-elements separated from the functions and technologies of the aforementioned cloud service functions, and configure them reasonably according to the functional characteristics and technical architecture. Each combination is an independent private cloud platform that can be run.

As shown in Figure 5, the enterprise can complete the privatization of the industry cloud according to the needs, that is, customize the corresponding private cloud platform for different customers. In the sharded cloud management platform, the customized scheduler selects the required meta-function module from the meta-function warehouse composed of meta-function modules according to customer information. According to the selected meta-function module, the meta-components required by each meta-function module are automatically selected from the meta-component warehouse composed of meta-components to obtain a list of meta-components. On the configuration platform, configure the function parameters of each meta-function module and the component parameters of the meta-components, and obtain the meta-function setting file and the meta-component setting file. Render meta-function parameters and meta-component parameters to the selected meta-component to get a customized list of meta-components. The component deployment file is obtained according to the called meta-component, and the deployment file is obtained by combining the meta-function setting file and the meta-component setting file. The deployment file specifically includes: customized meta-component list, component package program, deployment script, deployment configuration, bottom-up data, deployment manual, meta-function configuration file (including function parameters), and meta-component configuration file (including meta-component parameters). The deployment file is distributed to the client room using a specific pipeline, and the deployment environment is prepared in the client room at the same time, and the meta elements that have been prepared in the client room can be deployed remotely.

In this embodiment, by modularizing the cloud service function, multiple meta-functions are obtained, and corresponding meta-components are configured, so that the required meta-function modules and meta-components can be retrieved for different customer information, and the functions can be customized , and then send the deployment file to each website to run the cloud service function. Quickly complete the purchase, customization, and deployment of cloud service functions, realize industry cloud privatization according to enterprise needs, and realize scalable management of private cloud service functions.

In one embodiment, a plurality of meta-function modules form a meta-function library, and a plurality of corresponding meta-elements form a meta-element library; step S120 includes:

Step S121: Acquire customer information, where the customer information includes meta-function requirement information;

Step S122 : according to the meta-function requirement information, the corresponding meta-function module is retrieved from the meta-function library, and the corresponding meta-component is retrieved from the meta-component library.

In an example, as shown in Table 1, the cloud service functions included in the operation type may be charging functions and user management functions. The meta-function modules corresponding to the billing function may include: contract management module, order management module, bill management module, fund account management module, voucher management module, discount management module, quota management module, etc. Wait. The meta-function modules corresponding to the user management function may include: account information module, capital account module, account permission module, qualification authentication module, sub-account management module, user group management module, permission management module mods, etc. Of course, it also includes meta-function modules obtained by splitting other types of cloud service functions to form a meta-function library.

As shown in Table 1, the meta elements corresponding to the billing function and the meta elements corresponding to the user management function. For example, the meta-function module is an order management module, which can correspond to an order receiving meta-component, an order storage meta-component, an order-distributing meta-component, an order statistics meta-component, and the like. Both the order management module and the quota management module need bill-data, bill-server, bill-log and other billing-related meta-components to be implemented, but the order management module additionally requires bill-order, and quota management also requires bill -quota. Then if a client needs all the billing functions, then the meta functions like bill-data, bill-server, bill-log only need to be introduced once. Of course, it also includes meta-elements corresponding to other types of cloud service functions, which together form a meta-element library.

S110: Obtain the cloud service function, split the cloud service function into multiple meta-function modules, and configure the meta-elements corresponding to the meta-function modules S120: Obtain customer information, and retrieve the required meta-function modules and corresponding meta-components according to the customer information S121: Obtain customer information, including meta-function requirement information S122: Call the corresponding meta-function module from the meta-function library according to the meta-function requirement information, and call the corresponding meta-component from the meta-component library S130: Obtain a deployment file according to the called meta-function module and corresponding meta-component S140: Send the deployment file to the corresponding multiple websites to run the cloud service function

The accompanying drawings are used for better understanding of the present solution, and do not constitute a limitation to the present application. in:

[Fig. 1] is a schematic diagram of a cloud platform in the prior art; [Fig. 2] is a schematic diagram of a cloud platform management method according to an embodiment of the present application; [Fig. 3] is a schematic diagram of a hybrid cloud platform according to an embodiment of the present application; [Fig. 4] is a schematic diagram of function splitting according to an embodiment of the present application; [Fig. 5] is a schematic diagram of a function customization method of a sharded cloud management platform according to another embodiment of the present application; [Fig. 6] is a scene diagram of a cloud platform management method according to an embodiment of the present application; [Fig. 7] is a schematic diagram of functional classification of a sharded cloud management platform according to another embodiment of the present application; [ Fig. 8 ] is a schematic diagram of a cloud platform management device according to an embodiment of the present application; [ Fig. 9 ] is a block diagram of an electronic device used to implement a cloud platform management method according to an embodiment of the present application.

S110: Obtain the cloud service function, split the cloud service function into multiple meta-function modules, and configure the meta-elements corresponding to the meta-function modules

S120: Obtain customer information, and retrieve the required meta-function modules and corresponding meta-components according to the customer information

S130: Obtain a deployment file according to the called meta-function module and corresponding meta-component

S140: Send the deployment file to the corresponding multiple websites to run the cloud service function

Claims (14)

A cloud platform management method, comprising: Obtaining a cloud service function, splitting the cloud service function into a plurality of meta-function modules, and configuring a plurality of meta-elements corresponding to the meta-function modules; Obtain customer information, and retrieve the required meta-function modules and corresponding meta-components according to the customer information; Obtain the deployment file according to the called meta-function module and the corresponding meta-component; Send the deployment file to the corresponding multiple websites to run the cloud service function. The method according to claim 1, wherein the plurality of meta-function modules constitute a meta-function library, and the corresponding plurality of meta-elements constitute a meta-component library; the required meta-function modules are retrieved according to customer information Groups and corresponding meta-elements, including: Obtain customer information, including meta-functional requirement information; The corresponding meta-function module is retrieved from the meta-function library according to the meta-function requirement information, and the corresponding meta-component is retrieved from the meta-component library. The method of claim 2, further comprising: Delete the duplicated meta-components in the recalled meta-components to determine the supporting meta-components. The method according to any one of claim 1 to 3, wherein the acquiring a deployment file according to the retrieved multiple meta-function modules and corresponding multiple meta-components includes: Perform parameter configuration on the called meta-function modules and meta-elements to obtain a meta-function setting file and a meta-element setting file; Obtain the component deployment file according to the called meta-component; Wherein, the deployment file includes the meta-function profile, the meta-component profile and the component deployment profile. The method according to any one of claim 1 to 4, further comprising: Detecting and verifying the operation of the cloud service functions deployed on the multiple websites, if the verification fails, returning to execute the multiple meta-function modules and corresponding multiple meta-elements required for the configuration according to the customer information A step of. The method according to any one of claim items 1 to 5, wherein the cloud service function includes a user management function and a billing function corresponding to the operation type; The meta-function modules obtained by splitting the billing function include: a fund account module, an order management module, a billing management module, a contract management module, a quota management module, a discount module, and a voucher module; The meta-function modules obtained by splitting the user management function include: account information management module, capital account management module, account permission module, qualification authentication module, sub-account management module, and user group management module , Permission management module. A cloud platform management device, comprising: A function splitting module, used to obtain cloud service functions, and split the cloud service functions into multiple meta-function modules; A meta-function component configuration module, which configures the meta-component corresponding to the meta-function module; A meta-functional component retrieval module, used to obtain customer information, and to retrieve the required meta-functional modules and corresponding meta-components according to the customer information; The deployment file obtaining module is used to obtain the deployment file according to the called meta-function module and the corresponding meta-component; A function operation module, configured to send the deployment file to the corresponding multiple websites to run the cloud service function. The device according to claim 7, wherein the plurality of meta-function modules form a meta-function library, and the corresponding plurality of meta-elements form a meta-element library; the meta-function element retrieval module comprises: The customer information acquisition sub-module is used to acquire customer information, and the customer information includes meta-function requirement information; The calling sub-module is used for calling the corresponding meta-function module from the meta-function library according to the meta-function requirement information, and calling the corresponding meta-component from the meta-component library. The device according to claim 8, wherein the meta-function element retrieval module further comprises: The support element determination sub-module is used to delete the repeated element elements in the retrieved element elements to determine the support element elements. The device according to any one of claims 7 to 9, wherein the deployment file acquisition module comprises: A configuration file generating sub-module is used for parameter configuration of the called meta-function modules and meta-elements to obtain a meta-function configuration file and a meta-element configuration file; The component deployment file acquisition sub-module is used to obtain the component deployment file according to the called meta-component; Wherein, the deployment file includes the meta-function profile, the meta-component profile and the component deployment profile. The device according to any one of claims 7 to 10, further comprising: A function verification module, used to detect and verify the operation of the cloud service functions deployed on the multiple websites, and if the verification fails, return to execute the multiple meta-function modules required for the configuration according to the customer information and corresponding steps of a plurality of meta-elements. The device according to any one of claim items 7 to 11, wherein the cloud service function includes a user management function and a billing function corresponding to the operation type; The meta-function modules obtained by splitting the billing function include: a fund account module, an order management module, a billing management module, a contract management module, a quota management module, a discount module, and a voucher module; The meta-function modules obtained by splitting the user management function include: account information management module, capital account management module, account permission module, qualification authentication module, sub-account management module, and user group management module , Permission management module. An electronic device comprising: at least one processor; and memory communicatively coupled to the at least one processor; Wherein, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can execute as in the request items 1-6 The method of any one. A non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause the computer to perform the method of any one of claims 1-6.

Images