WO2022170760A1

WO2022170760A1 - Method and apparatus for cloud platform management, electronic device, and storage medium

Info

Publication number: WO2022170760A1
Application number: PCT/CN2021/117511
Authority: WO
Inventors: 李良杰; 韩韬; 吕苏; 王培林; 王忠钊; 解鸿浩; 孙炜程
Original assignee: 中国银联股份有限公司
Priority date: 2021-02-09
Filing date: 2021-09-09
Publication date: 2022-08-18
Also published as: TW202232395A; CN113014424B; CN113014424A

Abstract

The present application discloses a method and apparatus for cloud platform management. The specific solution implemented is: the method comprises: acquiring a cloud service function, splitting the cloud service function into meta functional modules, and configuring meta components corresponding to the meta functional modules; acquiring client information, calling a required meta functional module and the corresponding meta component on the basis of the client information; acquiring a deployment file on the basis of the called meta functional module and of the corresponding meta component; and transmitting the deployment file to multiple corresponding stations, thus running the cloud service function. The purchase, customization, and deployment of the cloud service function are accomplished quickly, the privatization of an industry cloud accomplished as required by an enterprise is implemented, and the scalable management of a private cloud service function is implemented.

Description

A cloud platform management method, device, electronic device and storage medium

This application claims the priority of the Chinese patent application with the application number of 202110180981.2 and titled "A cloud platform management method, apparatus, electronic device and storage medium", filed on February 9, 2021, and the disclosure of the Chinese patent application The contents are incorporated herein by reference.

technical field

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

Background technique

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 also 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 service products of private cloud and public cloud on the same platform. Customers can use cloud products, such as cloud servers, databases, etc., but cannot manage various products on the platform. Do the operation and maintenance of cloud products.

SUMMARY OF THE INVENTION

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-components corresponding to the meta-function modules;

Obtain customer information, and call 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 corresponding meta-component;

Send deployment files to the corresponding multiple sites 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;

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.

In one embodiment, it also includes:

Delete the duplicated meta-components in the called meta-component to determine the supporting meta-component.

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

Perform parameter configuration on the called meta-function modules and meta-components to obtain a meta-function configuration file and a meta-component configuration 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 at multiple sites. If the verification fails, return to the steps of configuring multiple required meta-function modules and corresponding multiple meta-components 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: a capital account module, an order management module, a bill 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 authority module, qualification authentication module, sub-account management module, user group management module, and authority 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 the cloud service functions into multiple meta-function modules;

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

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

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

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

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 meta-function component retrieval module includes:

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.

In one embodiment, the meta-function component invocation module further includes:

The support meta-component determination submodule is used to delete the repeated meta-components in the called meta-component to determine the support-meta-component.

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 module and meta-component to obtain the meta-function configuration file and the meta-component configuration file;

The component deployment file obtaining submodule is used to obtain the component deployment file according to the called meta-component;

In one embodiment, it also includes:

The function verification module is used to detect and verify the operation of the cloud service functions deployed at multiple sites. If the verification fails, it will return to execute multiple meta-function modules and corresponding multiple meta-components required for configuration according to customer information. step.

In a third aspect, an electronic device is provided, comprising:

at least one processor; and a memory communicatively coupled to the at least one processor;

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

In a fourth aspect, there is provided a non-transitory computer-readable storage medium storing computer instructions, the computer instructions being used to cause a computer to perform 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-components, the required meta-function modules and Meta components are used to customize functions, and then send deployment files to various sites 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.

Description of drawings

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

1 is a schematic diagram of a cloud platform in the prior art;

2 is a schematic diagram of a cloud platform management method according to an embodiment of the present application;

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;

5 is a schematic diagram of a function customization method of a sharded cloud management platform according to another embodiment of the present application;

6 is a scene diagram of a cloud platform management method according to an embodiment of the present application;

7 is a schematic diagram of functional classification of a sharded cloud management platform according to another embodiment of the present application;

8 is a schematic diagram of a cloud platform management apparatus 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.

Detailed ways

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 users. First, deploy new sites locally, and then provide customers with a complete set of cloud services through Outposts, including site 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: Obtain the cloud service function, split the cloud service function into multiple meta-function modules, and configure the meta-components 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-component;

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

In one example, as shown in Figure 3, a hybrid cloud platform is provided, the cloud console is used as the public cloud platform, and the customer console (for example, the customer 1 console and the customer 2 console) and the sharded cloud management platform are used as the public cloud platform. Private cloud platforms, customer consoles (eg, customer 3 consoles) can also stand alone as private cloud platforms. Customers can access site 1 and site 2, site 3 and site 4 through the Internet interface displayed by the cloud console (for example, exposing a separate domain name to the outside world). Site 3 and Site 4 can also be accessed through the customer console and the sharded cloud management platform. Only the cloud resource services of this site are provided externally, and the services provided externally are the functions that have been customized as described above. Site 5 can also be accessed only through the customer console. It should be pointed out that the number of sites provided in this embodiment includes but is not limited to site 1 to site 5, and there may be more sites. The site is the customer's computer room, which can contain 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 data of site 3 or site 4. For example, customer 1 can be a car company, and the customer can only access site 3 deployed by this car company through the customized function modules (purchase modules, etc.) displayed on the Internet interface of customer 1's console. Client 2 can be a payment institution, and the client can only access site 4 deployed by this payment structure through the customized function module (payment module, etc.) displayed on the Internet interface of Client 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, Site 5 also enables Customer 3 to have completely independent service capabilities. Station 5 can be switched back to station 3 and station 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 function (function 5) and automation function (function 6), etc. The cloud service functions are split to obtain multiple meta-function modules. The dismantling granularity 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 menu independently configured on the page. Each meta-function is implemented by a number of specific meta-components and supporting components. 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 meta-component is the smallest unit that can be independently deployed and configured, and each meta-component is decoupled. Organize the meta-functions and meta-components 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 in the meta-function warehouse composed of meta-function modules according to customer information. According to the selected meta-functional module, the meta-components required by each meta-functional module are automatically selected from the meta-component warehouse composed of meta-components, and the meta-component list is obtained. The functional parameters of each meta-function module and the component parameters of meta-components are configured on the configuration platform to obtain a meta-function configuration file and a meta-component configuration file. Render meta-function parameters and meta-component parameters into 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 configuration file and the meta-component configuration file. The deployment file specifically includes: customized meta-component list, component package, 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 files are distributed to the client room using a specific channel, and the deployment environment is prepared in the client room at the same time, and the meta-components 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, the required meta-function modules and meta-components can be retrieved for different customer information, and the functions can be customized. Send deployment files to various sites 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.

In one embodiment, a plurality of meta-function modules form a meta-function library, and a plurality of corresponding meta-components form a meta-component 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: a contract management module, an order management module, a bill management module, a capital account management module, a voucher management module, a discount management module, a quota management module, and the like. The meta-function modules corresponding to the user management function may include: account information module, fund account module, account authority module, qualification authentication module, sub-account management module, user group management module, authority management module, and so on. Of course, it also includes meta-function modules obtained by splitting other types of cloud service functions to form a meta-function library together.

As shown in Table 1, the meta-component corresponding to the charging function and the meta-component corresponding to the user management function. For example, the meta-function module is an order management module, which may 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 require 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-components corresponding to other types of cloud service functions, which together form a meta-component library.

As shown in Figure 6, the customer console obtains customer information and sends the customer information to the shard cloud management platform. In the shard cloud management platform, create a customer, create a key for the customer, and configure the obtained customer information. The customer information includes customer name, address, personnel, computer room information, meta-function requirement information (for example, contract information, functional scope, etc.) and a series of customer-related information. Select the required meta-function module from the meta-function library for the created customer according to the functional requirement information, and configure the functional parameters, which are related to the functions that the user can operate. For example, the function requirement information includes the required meta-function module selected in the operation type. Customer A may need the contract management module, and customer B does not need the contract management module, but the order management module. Therefore, it also belongs to the billing function. For different customers, the configuration method is different, and it is determined according to the customer's meta-functional requirements. After the called meta-function module is determined according to customer requirements, the list of meta-components corresponding to the called meta-function module can be automatically listed, and the component parameters can be configured.

In one embodiment, it also includes:

Step S123: Delete the repeated meta-components in the called meta-components, and determine the supporting meta-components.

In one example, the duplicated meta-components in the meta-component list corresponding to each selected functional module are deleted, and after filtering, such as filtering the duplicated components, the supporting meta-component is obtained, and then a standardized meta-component list is obtained. Common components that need to communicate or share among components are called support components. A meta-component can depend on multiple supporting meta-components. Meta-component business-related, not cross-meta function. Support components can be reused across metafunctions.

For example, as shown in Table 1, the components of the order management module, user management module and other modules all need to access the MySQL database, so the MySQL database meta-component is the support meta-component. This support element can be shared without repeated deployment, which effectively saves resources. For the meta-components bill-data, bill-server, bill-log, bill-quota, and bill-order, supporting components such as base-mysql and base-redis may be required. Therefore, for each meta-function of billing, if there are duplicate supporting components, it only needs to be introduced once. Similarly, for the user management module, supporting components such as base-mysql and base-redis are also required. Then, when the user introduces the billing function and the customer management function, the support component only needs to be introduced once.

In one embodiment, step S130 includes:

Step S131: Perform parameter configuration on the called meta-function modules and meta-components to obtain a meta-function configuration file and a component configuration file;

Step S132: obtaining a component deployment file according to the called meta-component;

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

In an example, as shown in FIG. 6 , the meta-function configuration includes a custom configuration and a default configuration, and a meta-function configuration file is generated. For example, the description text of the page can be customized, and the technical parameters have default values and can also be customized. After the supporting components required by the customer form a component list, configure the parameters of the supporting components in the list, including various technical parameter configurations. Then, a list of hardware resources required to support these components is automatically generated and submitted to the customer for confirmation. Component configuration can also contain custom configuration and default configuration. For example, the description text of the page is customized. For example, technical parameters have default values and can also be customized. Select the component version from the component repository according to the component list and assemble it to obtain the component deployment file.

In one embodiment, it also includes:

Step S150: Detect and verify the operation of the cloud service functions deployed at multiple sites. If the verification fails, return to the step of configuring multiple required meta-function modules and corresponding multiple meta-components according to customer information.

In an example, as shown in FIG. 6 , in the site, the function operation is tested and verified, which may include function test, performance test, security test, and the like. For example, check whether the verification function has been working properly, whether the page function is normal, etc. If the verification is passed, the deployment is completed, and the technical personnel and operation and maintenance personnel of different enterprises can select the corresponding functions of the enterprise through the customer console for maintenance and management.

In one example, as shown in Figure 7, there are multiple function types in the sharded cloud management platform, such as operation, product, and operation and maintenance. Taking the operation type as an example, obtain cloud service functions, such as billing functions and user management functions. Of course, there may also be other types of corresponding cloud service functions and meta-function modules. For example, the product type, the function of obtaining cloud services, may include computing functions, storage functions, and network functions, etc., and the corresponding meta-function modules may include database modules, middleware modules, and application modules. Operation and maintenance type, to obtain cloud service functions, can include automation functions, monitoring functions, etc., and the corresponding meta-function modules can include configuration modules, inspection modules, and alarm modules. Of course, the splitting of cloud service functions includes, but is not limited to, the above methods, and adaptive adjustments are made according to requirements. Each meta-function module can be further subdivided. For example, the computing-type meta-function module can be divided into memory computing sub-modules, general computing sub-modules, and bare metal servers.

In another specific implementation, as shown in FIG. 8, a cloud platform management apparatus is provided, including:

The function splitting module 110 is used to obtain the cloud service function and split the cloud service function into a plurality of meta-function modules;

a meta-function component configuration module 120, configured to configure the meta-component corresponding to the meta-function module;

The meta-functional component retrieval module 130 is used for acquiring customer information, and retrieving the required meta-functional modules and corresponding meta-components according to the customer information;

a deployment file obtaining module 140, configured to obtain a deployment file according to the called meta-function module and corresponding meta-component;

The function operation module 150 is configured to send the deployment file to the corresponding multiple sites, so as to run the cloud service function.

The support element component determination sub-module is used to delete the duplicated element components in the called meta component, and determine the support element component, so as to configure the parameters of the support element component.

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 module and meta-component to obtain the meta-function configuration file and the component configuration file;

In one embodiment, it also includes:

For the functions of each module in each device in this embodiment of the present application, reference may be made to the corresponding description in the foregoing method, and details are not described herein again.

According to the embodiments of the present application, the present application further provides an electronic device and a readable storage medium.

As shown in FIG. 9 , it is a block diagram of an electronic device according to a cloud platform management method according to an embodiment of the present application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. Electronic devices may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are by way of example only, and are not intended to limit implementations of the application described and/or claimed herein.

As shown in FIG. 9, the electronic device includes: one or more processors 901, a memory 902, and interfaces for connecting various components, including a high-speed interface and a low-speed interface. The various components are interconnected using different buses and may be mounted on a common motherboard or otherwise as desired. The processor may process instructions for execution within the electronic device, including storing in or on memory to display a Graphical User Interface (GUI) on an external input/output device, such as a display device coupled to the interface ) instructions for graphics information. In other embodiments, multiple processors and/or multiple buses may be used with multiple memories and multiple memories, if desired. Likewise, multiple electronic devices may be connected, each providing some of the necessary operations (eg, as a server array, a group of blade servers, or a multiprocessor system). A processor 901 is taken as an example in FIG. 9 .

The memory 902 is the non-transitory computer-readable storage medium provided by the present application. The memory stores instructions executable by at least one processor, so that the at least one processor executes the cloud platform management method provided by the present application. The non-transitory computer-readable storage medium of the present application stores computer instructions, and the computer instructions are used to make a computer execute a cloud platform management method provided by the present application.

As a non-transitory computer-readable storage medium, the memory 902 can be used to store non-transitory software programs, non-transitory computer-executable programs and modules, such as program instructions/modules corresponding to a cloud platform management method in the embodiments of the present application. The processor 901 executes various functional applications and data processing of the server by running the non-transitory software programs, instructions and modules stored in the memory 902, ie, implements a cloud platform management method in the above method embodiments.

The memory 902 may include a storage program area and a storage data area, wherein the storage program area may store an operating system and an application program required for at least one function; the storage data area may store a cloud platform management method created by the use of an electronic device data etc. Additionally, memory 902 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, memory 902 may optionally include memory located remotely relative to processor 901, and these remote memories may be connected to the aforementioned electronic device through a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

The above electronic device may further include: an input device 903 and an output device 904 . The processor 901 , the memory 902 , the input device 903 and the output device 904 may be connected by a bus or in other ways, and the connection by a bus is taken as an example in FIG. 9 .

The input device 903 can receive input numerical or character information, and generate key signal input related to user settings and function control of the above-mentioned electronic equipment, such as a touch screen, a keypad, a mouse, a trackpad, a touchpad, a pointing stick, one or more Input devices such as mouse buttons, trackballs, joysticks, etc. Output devices 904 may include display devices, auxiliary lighting devices (eg, LEDs), haptic feedback devices (eg, vibration motors), and the like. The display device may include, but is not limited to, a liquid crystal display (Liquid Cr9stal Displa9, LCD), a light emitting diode (Light Emitting Diode, LED) display, and a plasma display. In some implementations, the display device may be a touch screen.

Various implementations of the systems and techniques described herein can be implemented in digital electronic circuitry, integrated circuit systems, application specific integrated circuits (ASICs), computer hardware, firmware, software, and/or combinations thereof . These various embodiments may include being implemented in one or more computer programs executable and/or interpretable on a programmable system including at least one programmable processor that The processor, which may be a special purpose or general-purpose programmable processor, may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device an output device.

These computational programs (also referred to as programs, software, software applications, or codes) include machine instructions for programmable processors, and may be implemented using high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages calculation program. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or apparatus for providing machine instructions and/or data to a programmable processor ( For example, magnetic disks, optical disks, memories, programmable logic devices (PLDs)), including machine-readable media that receive machine instructions as machine-readable signals. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.

To provide interaction with a user, the systems and techniques described herein may be implemented on a computer having: a display device (eg, a CRT (Cathode Ray Tube) or an LCD (liquid crystal) for displaying information to the user monitor); and a keyboard and pointing device (eg, a mouse or trackball) through which a user can provide input to the computer. Other kinds of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (eg, visual feedback, auditory feedback, or tactile feedback); and can be in any form (including acoustic input, voice input, or tactile input) to receive input from the user.

The systems and techniques described herein may be implemented on a computing system that includes back-end components (eg, as a data server), or a computing system that includes middleware components (eg, an application server), or a computing system that includes front-end components (eg, a user computer having a graphical user interface or web browser through which a user may interact with implementations of the systems and techniques described herein), or including such backend components, middleware components, Or any combination of front-end components in a computing system. The components of the system may be interconnected by any form or medium of digital data communication (eg, a communication network). Examples of communication networks include: Local Area Network (LAN), Wide Area Network (WAN), and the Internet.

A computer system can include clients and servers. Clients and servers are generally remote from each other and usually interact through a communication network. The relationship of client and server arises by computer programs running on the respective computers and having a client-server relationship to each other.

It should be understood that steps may be reordered, added or deleted using the various forms of flow shown above. For example, the steps described in the present application can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solutions disclosed in the present application can be achieved, no limitation is imposed herein.

The above-mentioned specific embodiments do not constitute a limitation on the protection scope of the present application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent replacements and improvements made within the spirit and principles of this application shall be included within the protection scope of this application.

Claims

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-components corresponding to the meta-function modules;

Acquiring customer information, and retrieving 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 corresponding meta-component;

Send the deployment file to the corresponding multiple sites to run the cloud service function.
The method according to claim 1, wherein the plurality of meta-function modules form a meta-function library, and the corresponding plurality of meta-components form a meta-component library; the required meta-function is fetched according to customer information Modules and corresponding meta-components, including:

Acquiring customer information, the customer information includes meta-function 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 called meta-component to determine the supporting meta-component.
The method according to any one of claims 1-3, wherein the acquiring the 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-components to obtain a meta-function configuration file and a meta-component configuration file;

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

Wherein, the deployment file includes the meta-function configuration file, the meta-component configuration file, and the component deployment file.
The method according to any one of claims 1-4, further comprising:

Detect and verify the operation of the cloud service functions deployed in the multiple sites, and if the verification fails, return to execute the multiple meta-function modules required for the configuration according to the customer information and the corresponding multiple meta-components. step.
The method according to any one of claims 1-5, wherein the cloud service function includes a user management function and a charging function corresponding to an operation type;

The meta-function modules obtained by splitting the charging function include: a capital account module, an order management module, a bill 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: an account information management module, a capital account management module, an account authority module, a qualification authentication module, a sub-account management module, a user group management module, and an authority 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-functional component configuration module, which configures the meta-component corresponding to the meta-functional module;

a meta-function component retrieval module, used for acquiring customer information, and retrieving required meta-function 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 sites to run the cloud service function.
The device according to claim 7, wherein the plurality of meta-function modules constitute a meta-function library, and the corresponding plurality of meta-components constitute a meta-component library; the meta-function component retrieval module comprises:

a customer information acquisition sub-module for acquiring customer information, where 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 apparatus according to claim 8, wherein the meta-function component invoking module further comprises:

The support meta-component determination submodule is used to delete the repeated meta-components in the called meta-component to determine the support-meta-component.
The device according to any one of claims 7-9, wherein the deployment file acquisition module comprises:

a configuration file generation submodule, used for parameter configuration of the called meta-function modules and meta-components, to obtain a meta-function configuration file and a meta-component configuration file;

The component deployment file obtaining submodule is used to obtain the component deployment file according to the called meta-component;

Wherein, the deployment file includes the meta-function configuration file, the meta-component configuration file, and the component deployment file.
The device according to any one of claims 7-10, further comprising:

A function verification module, used to detect and verify the operation of the cloud service functions deployed in the multiple sites, and if the verification fails, return to execute the multiple meta-function modules required for the configuration according to the customer information and the corresponding steps for multiple meta-components.
The device according to any one of claims 7-11, wherein the cloud service function includes a user management function and a billing function corresponding to an operation type;

The meta-function modules obtained by splitting the charging function include: a capital account module, an order management module, a bill 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: an account information management module, a capital account management module, an account authority module, a qualification authentication module, a sub-account management module, a user group management module, and an authority management module.
An electronic device, comprising:

at least one processor; and a memory communicatively coupled to the at least one processor;

wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to execute any of claims 1-6 the method described.
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.