CN113014424B - Cloud platform management method and device, electronic equipment and storage medium - Google Patents
Cloud platform management method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN113014424B CN113014424B CN202110180981.2A CN202110180981A CN113014424B CN 113014424 B CN113014424 B CN 113014424B CN 202110180981 A CN202110180981 A CN 202110180981A CN 113014424 B CN113014424 B CN 113014424B
- Authority
- CN
- China
- Prior art keywords
- meta
- function
- module
- component
- management
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
- H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a cloud platform management method and device. The specific implementation scheme is as follows: the cloud service function is acquired, split into meta-function modules, and a meta-component corresponding to the meta-function modules is configured; acquiring client information, and calling a required meta function module and a corresponding meta component according to the client information; acquiring a deployment file according to the called meta function module and the corresponding meta component; and sending the deployment file to a plurality of corresponding sites to run the cloud service function. The purchase, customization and deployment of the cloud service function are rapidly completed, the industry cloud privatization is completed according to the enterprise needs, and the telescopic management of the private cloud service function is realized.
Description
Technical Field
The application relates to the technical field of cloud platforms, in particular to the field of cloud platform management.
Background
Cloud platforms refer to services based on hardware resources and software resources, providing computing, networking, and storage capabilities. Cloud services can be provided for the development of applications. For example, a new software, i.e., a developer of an application service, is developed on a cloud platform, and a direct user of the cloud platform is a developer rather than an ordinary user, which provides a stable development environment for the developer. Financial enterprises increasingly need to deploy IT systems on industry cloud platforms to improve system stability and reduce operation cost, and meanwhile, the financial enterprises also need to meet operation compliance, data compliance and the like of the IT systems under the requirement of strong supervision.
Industry clouds are cloud platforms that are established and maintained by organizations that are dominant or master of critical resources within the industry or within an area, in a public or semi-public manner, to provide paid or gratuitous services to the industry's internal or related organizations and the public. Existing industry clouds are mostly deployed in private or hybrid cloud forms. 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 completely master the use of the whole cloud computing system, has high labor cost, and has high development and operation and maintenance cost and long period required for customizing functions of different users. The hybrid cloud merges public cloud and private cloud, and data are stored in the private cloud, but meanwhile, the hybrid cloud hopes that computing resources of the public cloud can be obtained, and is a main mode and development direction of cloud computing in recent years. However, the hybrid cloud platform only realizes that the purchase service products of the private cloud and the public cloud are concentrated on the same platform, and clients can use cloud products, such as cloud servers, databases and the like, but cannot manage various products on the platform, and do not do operation and maintenance work on the cloud products.
Disclosure of Invention
The embodiment of the application provides a cloud platform management method, a cloud platform management device, electronic equipment and a storage medium, so as to solve the problems in the related art, and the technical scheme is as follows:
in a first aspect, an embodiment of the present application provides a cloud platform management method, including:
acquiring 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 client information, and calling a required meta function module and a corresponding meta component according to the client information;
acquiring a deployment file according to the called meta function module and the corresponding meta component;
and sending the deployment file to a plurality of corresponding sites to run the cloud service function.
In one embodiment, a plurality of meta-function modules form a meta-function library, and a corresponding plurality of meta-components form a meta-component library; the method for calling the required meta-function module and the corresponding meta-component according to the client information comprises the following steps:
acquiring client information, wherein the client information comprises meta-function requirement information;
and calling a corresponding meta function module from a meta function library according to the meta function requirement information, and calling a corresponding meta component from a meta component library.
In one embodiment, the method further comprises:
deleting repeated components in the fetched components to determine the supporting components.
In one embodiment, obtaining a deployment file from the plurality of invoked meta-function modules and the corresponding plurality of meta-components includes:
parameter configuration is carried out on the fetched meta function module and the meta component to obtain a meta function configuration file and a meta component configuration file;
acquiring a component deployment file according to the fetched meta-component;
the deployment files comprise meta-function configuration files, meta-component configuration files and component deployment files.
In one embodiment, the method further comprises:
and detecting and verifying the running condition of the cloud service function deployed at a plurality of sites, and returning to execute a plurality of meta-function modules and a plurality of corresponding meta-components required by the configuration according to the client information if the running condition is verified to be not passed.
In one embodiment, the cloud service function includes a user management function and a charging function corresponding to an operation type;
the meta function module obtained by splitting the charging function comprises: the system comprises a fund account module, an order management module, a bill management module, a contract management module, a quota management module, a discount module and a cash security module;
the meta function module obtained by splitting the user management function comprises: the system comprises an account information management module, a fund 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.
In a second aspect, a cloud platform management apparatus is provided, including:
the function splitting module is used for acquiring cloud service functions and splitting the cloud service functions into a plurality of meta-function modules;
the meta-function component configuration module is used for configuring a meta-component corresponding to the meta-function module;
the meta function component calling module is used for acquiring the client information, calling the required meta function module and the corresponding meta component according to the client information;
the deployment file acquisition module is used for acquiring deployment files according to the plurality of the called meta-function modules and the corresponding plurality of the meta-components;
and the function operation module is used for sending the deployment file to a plurality of corresponding sites so as to operate the cloud service function.
In one embodiment, a plurality of meta-function modules form a meta-function library, and a corresponding plurality of meta-components form a meta-component library; the meta function component invoking module includes:
the client information acquisition sub-module is used for acquiring client information, wherein the client information comprises meta-function requirement information;
and 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 retrieval module further comprises:
and the support component determining sub-module is used for deleting repeated components in the called components and determining the support component.
In one embodiment, the deployment file acquisition module comprises:
the configuration file generation sub-module is used for carrying out parameter configuration on the called meta-function module and the meta-component to obtain a meta-function configuration file and a meta-component configuration file;
the component deployment file acquisition sub-module is used for acquiring a component deployment file according to the fetched meta-component;
the deployment files comprise meta-function configuration files, meta-component configuration files and component deployment files.
In one embodiment, the method further comprises:
and the function verification module is used for detecting and verifying the running condition of the cloud service functions deployed at the multiple sites, and returning to execute the multiple meta-function modules and the corresponding multiple meta-components required by the configuration according to the client information if the verification is not passed.
In one embodiment, the cloud service function includes a user management function and a charging function corresponding to an operation type;
the meta function module obtained by splitting the charging function comprises: the system comprises a fund account module, an order management module, a bill management module, a contract management module, a quota management module, a discount module and a cash security module;
the meta function module obtained by splitting the user management function comprises: the system comprises an account information management module, a fund 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.
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 the at least one processor to enable the at least one processor to perform the method of any one of the above.
In a fourth aspect, there is provided a non-transitory computer readable storage medium storing computer instructions for causing a computer to perform the method of any one of the above.
One embodiment of the above application has the following advantages or benefits: the cloud service function is modularized, so that a plurality of meta functions are obtained, corresponding meta components are configured, required meta function modules and meta components can be called according to different client information, function customization is carried out, and further, deployment files are sent to each site to operate the cloud service function. The purchase, customization and deployment of the cloud service function are rapidly completed, the industry cloud privatization is completed according to the enterprise needs, and the telescopic management of the private cloud service function is realized.
Other effects of the above alternative will be described below in connection with specific embodiments.
Drawings
The drawings are for better understanding of the present solution and do not constitute a limitation of the present application. Wherein:
FIG. 1 is a schematic diagram of a prior art cloud platform;
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 functional split schematic diagram according to an embodiment of the present application;
FIG. 5 is a schematic diagram of a method for customizing functionality of a tiled cloud management platform according to another embodiment of the present application;
FIG. 6 is a scenario diagram of a cloud platform management method according to an embodiment of the present application;
FIG. 7 is a schematic diagram of a functional classification of a sliced 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 for implementing a cloud platform management method according to an embodiment of the present application.
Detailed Description
Exemplary embodiments of the present application are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present application to facilitate understanding, and should be considered as merely exemplary. Accordingly, one 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 in the following description for clarity and conciseness.
As shown in fig. 1, the Outposts product of AWS (amazon cloud service) handles the setup and management of hybrid cloud infrastructure for users. First, a new site is deployed locally on the customer, and then a complete set of cloud services, including the site's operational dimensions, is provided to the customer through Outposts. However, the AWS offsites cloud platform is a public cloud platform, and cannot provide services of a private cloud platform for different clients.
In order to accomplish industry cloud privatization according to customer needs, as shown in fig. 2, the embodiment provides a cloud platform management method, which specifically includes the steps of:
step S110: acquiring a cloud service function, splitting the cloud service function into a plurality of meta-function modules, and configuring meta-components corresponding to the meta-function modules;
step S120: acquiring client information, and calling a required meta function module and a corresponding meta component according to the client information;
step S130: acquiring a deployment file according to the called meta function module and the corresponding meta component;
step S140: and sending the deployment file to a plurality of corresponding sites to run the cloud service function.
In one example, as shown in fig. 3, a hybrid cloud platform is provided, with the cloud console as a public cloud platform, the client console (e.g., client 1 console and client 2 console) and the sliced cloud management platform as private cloud platforms, and the client console (e.g., client 3 console) alone as private cloud platform. Customers may access sites 1 and 2, sites 3 and 4 through an internet interface presented by the cloud console (e.g., exposing separate domain names to the outside). The site 3 and the site 4 can be accessed through the client console and the fragment cloud management platform, only cloud resource service of the site is provided for the outside, and the service provided for the outside is the customized function. Site 5 may also be accessed only through a client console. It should be noted that the number of stations provided in this embodiment includes, but is not limited to, station 1 to station 5, and there may be more stations. The site is a machine room of the client, and the machine room can comprise a plurality of servers.
When a client accesses through the client console and the fragment cloud management platform, the client console is a console customized for different clients, and only displays data of the site 3 or the site 4. For example, the client 1 may be a vehicle enterprise, and the client may only access the site 3 deployed by the vehicle enterprise through the custom function module (purchase module, etc.) displayed on the internet interface of the console of the client 1. Customer 2 may be a payment mechanism, and the customer may only access site 4 deployed by the payment mechanism via a custom function module (payment module, etc.) presented by the customer 2 console internet interface. The console of the client 3 does not need to be transferred through the fragment cloud management platform, and therefore, the client 3 does not have function customization capability, and meanwhile, the site 5 also enables the client 3 to have complete independent autonomous service capability. Station 5 may switch back to the form of stations 3, 4 as needed.
As shown in fig. 4, in the fragmented cloud management platform, the cloud service function may be divided into various types, for example, an operation type, an operation and maintenance type, a product type, and the like, according to a usage scenario and a logical deployment. Multiple cloud service functions may be included in each type. For example, the operation type may include a billing function (function 1), a user management function (function 2), and the like, the operation type may include a calculation function (function 3), a storage function (function 4), and the like, and the product may include a monitoring function (function 5), an automation function (function 6), and the like. And splitting the cloud service function to obtain a plurality of meta-function modules. The disassembly granularity is subdivided as far as possible, each meta-function module is an independent function, the meta-function is the minimum unit of function configuration, and the meta-function module is a function menu which is independently configured on a page. Each meta-function is implemented by a number of specific meta-components and support components. Each meta-function module is disassembled into an independently-deployable program execution unit from the technical framework, and the same meta-function module is technically and logically split into a plurality of sub-components, which are called meta-components. Each component is the minimum unit which can be independently deployed and configured, and decoupling is achieved among the components. And organizing meta-functions and meta-components of the cloud service functions separated from functions and technologies, and reasonably configuring according to functional characteristics and technical architecture, wherein each combination is an independent private cloud platform capable of running.
As shown in fig. 5, the enterprise can complete industry cloud privatization according to the needs, that is, customizing corresponding private cloud platforms for different clients. In the fragment cloud management platform, a custom scheduler selects a required meta-function module in a meta-function warehouse formed by the meta-function modules according to customer information. And automatically selecting the components needed by each element function module from an element component warehouse formed by element components according to the selected element function modules, and obtaining an element component list. And configuring the function parameters of each meta-function module and the component parameters of the meta-component in the configuration platform to obtain a meta-function configuration file and a meta-component configuration file. And rendering the meta-function parameters and the meta-component parameters into the selected meta-components to obtain a customized meta-component list. And acquiring a component deployment file according to the fetched meta-component, and combining the meta-function configuration file and the meta-component configuration file to obtain the deployment file. The deployment file specifically comprises: customized meta-component lists, component packages, deployment scripts, deployment configurations, bottoming data, deployment manuals, meta-function configuration files (including function parameters), meta-component configuration files (including meta-component parameters). The deployment files are distributed to the client room by using a specific channel, and the deployment environment is prepared in the client room, so that the prepared components in the client room can be deployed remotely.
In this embodiment, the cloud service function is modularized to obtain a plurality of meta functions, and corresponding meta components are configured, so that the required meta function modules and meta components can be called for different client information, the function customization is performed, and further, the deployment file is sent to each site to operate the cloud service function. The purchase, customization and deployment of the cloud service function are rapidly completed, the industry cloud privatization is completed according to the enterprise needs, and the telescopic management of the private cloud service function is realized.
In one embodiment, a plurality of meta-function modules form a meta-function library, and a corresponding plurality of meta-components form a meta-component library; step S120 includes:
step S121: acquiring client information, wherein the client information comprises meta-function requirement information;
step S122: and calling a corresponding meta function module from a meta function library according to the meta function requirement information, and calling a corresponding meta component from a meta component library.
In one example, as shown in table 1, the cloud service functions included in the operation type may be a billing function and a user management function. The meta function module corresponding to the charging function may include: contract management module, order management module, bill management module, funds account management module, voucher management module, discount management module, quota management module, and the like. The meta function module corresponding to the user management function may include: an account information module, a fund account module, an account authority module, a qualification authentication module, a sub-account management module, a user group management module, an authority management module and the like. Of course, the system also comprises meta-function modules obtained by splitting other types of cloud service functions, and the meta-function modules together form a meta-function library.
The components corresponding to the charging function and the components corresponding to the user management function are shown in table 1. For example, the meta-function module is an order management module, and may correspond to an order receiving component, an order storage component, an order distribution component, an order statistics component, and the like. Both the order management module and the quota management module need bill-data, bill-server, bill-log and other charging related components to realize, but the order management module also needs bill-order additionally, and quota management also needs bill-quota. Then if a customer needs all billing functions, then the meta-functions of bill-data, bill-server, bill-log need only be introduced once. Of course, the cloud service system also comprises the components corresponding to other types of cloud service functions, and the components are combined into a component library.
As shown in fig. 6, the client console obtains the client information and sends the client information to the sharded cloud management platform. In the fragment cloud management platform, a client is created, and a key and acquired client information are created for the client. Customer information includes customer name, address, personnel, room information, meta-function requirement information (e.g., contract information, function scope, etc.) a series of customer-related information. And selecting a required meta function module from a meta function library for the created client according to the function requirement information, and configuring the function parameters related to the functions which can be operated by the user. For example, the function requirement information includes a meta-function module required by selecting in the operation type, the customer a may need a contract management module, and the customer B does not need a contract management module, but needs an order management module, so the system also belongs to a charging function, faces different customers, has different configuration modes, and is determined according to the meta-function requirements of the customers. After the called meta-function module is determined according to the customer requirement, a meta-component list corresponding to the called meta-function module can be automatically listed to carry out configuration of component parameters.
In one embodiment, the method further comprises:
step S123: deleting repeated components in the fetched components to determine the supporting components.
In one example, duplicate components in the component list corresponding to each selected functional module are deleted, and the duplicate components are filtered, for example, to obtain a supporting component, thereby obtaining a standardized component list. Common components that need to communicate or be shared for each component are referred to as support meta-components. One subassembly may rely on multiple support subassemblies. The meta-component services are related and do not span meta-functions. The support assembly can be reused across functions.
For example, as shown in table 1, the components of the order management module, the user management module, etc. all need to access the MySQL database, then the MySQL database component is the support component. The supporting components can be shared, repeated deployment is not needed, and resources are effectively saved. For the meta-components bill-data, bill-server, bill-log, bill-quota, bill-order, a support component such as base-mysql, base-redis may be required. The support assembly is repeatedly introduced only once for each element of the billing function. Similarly, for the user management module, a support component such as base-mysql, base-redis is also required. The support assembly only needs to be introduced once when the user introduces the billing function and the customer management function.
In one embodiment, step S130 includes:
step S131: parameter configuration is carried out on the fetched meta function module and the meta component to obtain a meta function configuration file and a component configuration file;
step S132: acquiring a component deployment file according to the fetched meta-component;
the deployment files comprise meta-function configuration files, component configuration files and component deployment files.
In one example, as shown in FIG. 6, the meta-function configuration includes a custom configuration and a default configuration, generating a meta-function configuration file. For example, the explanatory text of the page can be customized, and the technical parameters have default values and can also be customized. After the support element components required by the clients form a component list, parameter configuration is carried out on the support element components in the component list, and the parameters comprise various technical parameter configurations. A list of hardware resources needed to support these components is then automatically generated and the customer is given confirmation. Component configurations may also include custom configurations and default configurations. For example, the descriptive text of the page is custom. For example, the technical parameters have default values and can be customized. And selecting and assembling the component version from the component warehouse according to the component list, and acquiring a component deployment file.
In one embodiment, the method further comprises:
step S150: and detecting and verifying the running condition of the cloud service function deployed at a plurality of sites, and returning to execute a plurality of meta-function modules and a plurality of corresponding meta-components required by the configuration according to the client information if the running condition is verified to be not passed.
In one example, as shown in FIG. 6, in a site, the verification of the function operation may include functional testing, performance testing, security testing, and the like. For example, it is detected whether the authentication function has been normally operated, whether the page function is normal, and the like. If the verification is passed, the deployment is completed, and technicians and operation and maintenance personnel of different enterprises can select corresponding functions of the enterprise through the client console to carry out maintenance and management.
In one embodiment, the cloud service function includes a user management function and a charging function corresponding to an operation type;
the meta function module obtained by splitting the charging function comprises: the system comprises a fund account module, an order management module, a bill management module, a contract management module, a quota management module, a discount module and a cash security module;
the meta function module obtained by splitting the user management function comprises: the system comprises an account information management module, a fund 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.
In one example, as shown in fig. 7, there are multiple functional types in the sliced cloud management platform, such as operations, products, and dimensions. Taking the operation type as an example, a cloud service function, such as a charging function, a user management function, and the like, is acquired. Of course, there may be other types of corresponding cloud service functions and meta-function modules. For example, the product type, the acquisition cloud service function, may include a computing function, a storage function, a network function, and the like, and the corresponding meta-function module may include a database module, a middleware module, an application module, and the like. The operation and maintenance type can acquire cloud service functions, and can comprise an automation function, a monitoring function and the like, and the corresponding meta-function modules can comprise a configuration module, a patrol module, an alarm module and the like. Of course, the splitting of the cloud service function includes, but is not limited to, the above manner, and adaptive adjustment is performed according to requirements. Each meta-function module may also be further subdivided, for example, the computing meta-function module may be divided into a memory computing sub-module, a general computing sub-module, a bare metal server, and the like.
In another embodiment, as shown in fig. 8, there is provided a cloud platform management apparatus, including:
the function splitting module 110 is configured to obtain a cloud service function, and split the cloud service function into a plurality of meta-function modules;
a meta function component configuration module 120 for configuring a meta component corresponding to the meta function module;
the meta function component retrieving module 130 is configured to obtain client information, and retrieve a required meta function module and a corresponding meta component according to the client information;
a deployment file obtaining module 140, configured to obtain a deployment file according to the invoked meta function module and the corresponding meta component;
the function running module 150 is configured to send the deployment file to a plurality of sites to run the cloud service function.
In one embodiment, a plurality of meta-function modules form a meta-function library, and a corresponding plurality of meta-components form a meta-component library; the meta function component invoking module includes:
the client information acquisition sub-module is used for acquiring client information, wherein the client information comprises meta-function requirement information;
and 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 retrieval module further comprises:
and the support component determining sub-module is used for deleting repeated components in the retrieved components, determining the support component and carrying out parameter configuration on the support component.
In one embodiment, the deployment file acquisition module comprises:
the configuration file generation sub-module is used for carrying out parameter configuration on the called meta-function module and the meta-component to obtain a meta-function configuration file and a component configuration file;
the component deployment file acquisition sub-module is used for acquiring a component deployment file according to the fetched meta-component;
the deployment files comprise meta-function configuration files, component configuration files and component deployment files.
In one embodiment, the method further comprises:
and the function verification module is used for detecting and verifying the running condition of the cloud service functions deployed at the multiple sites, and returning to execute the multiple meta-function modules and the corresponding multiple meta-components required by the configuration according to the client information if the verification is not passed.
In one embodiment, the cloud service function includes a user management function and a charging function corresponding to an operation type;
the meta function module obtained by splitting the charging function comprises: the system comprises a fund account module, an order management module, a bill management module, a contract management module, a quota management module, a discount module and a cash security module; the meta function module obtained by splitting the user management function comprises: the system comprises an account information management module, a fund 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.
The functions of each module in each apparatus of the embodiments of the present application may be referred to the corresponding descriptions in the above methods, which are not described herein again.
According to embodiments of the present application, an electronic device and a readable storage medium are also provided.
Fig. 9 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, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant 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, memory 902, and interfaces for connecting the components, including high-speed interfaces and low-speed interfaces. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions executing within the electronic device, including instructions stored in or on memory to display graphical information of a graphical user interface (Graphical User Interface, GUI) on an external input/output device, such as a display device coupled to the interface. In other embodiments, multiple processors and/or multiple buses may be used, if desired, along with multiple memories and multiple memories. Also, multiple electronic devices may be connected, each providing a portion of the necessary operations (e.g., as a server array, a set of blade servers, or a multiprocessor system). In fig. 9, a processor 901 is taken as an example.
Memory 902 is a non-transitory computer-readable storage medium provided herein. The memory stores instructions executable by the at least one processor to cause the at least one processor to perform a cloud platform management method provided herein. The non-transitory computer readable storage medium of the present application stores computer instructions for causing a computer to perform a cloud platform management method provided by the present application.
The memory 902 is used as a non-transitory computer readable storage medium, and 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 of the server and data processing by running non-transitory software programs, instructions, and modules stored in the memory 902, that is, implements a cloud platform management method in the above-described 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, at least one application program required for a function; the storage data area may store data created according to the use of an electronic device of one cloud platform management method, and the like. In addition, the 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 optionally includes memory remotely located relative to processor 901, which may be connected to the electronic device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The electronic device may further include: an input device 903 and an output device 904. The processor 901, memory 902, input devices 903, and output devices 904 may be connected by a bus or other means, for example in fig. 9.
The input device 903 may receive input numeric or character information and generate key signal inputs related to user settings and function controls of the electronic device described above, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, a pointer stick, one or more mouse buttons, a track ball, a joystick, and the like. The output means 904 may include a display device, auxiliary lighting means (e.g., LEDs), tactile feedback means (e.g., vibration motors), and the like. The display device may include, but is not limited to, a Liquid Crystal Display (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 here can be implemented in digital electronic circuitry, integrated circuitry, application specific integrated circuits (Application Specific Integrated Circuits, ASIC), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
These computing programs (also referred to as programs, software applications, or code) include machine instructions for a programmable processor, and may be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device (e.g., magnetic discs, optical disks, memory, programmable logic devices (programmable logic device, PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., CRT (Cathode Ray Tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and pointing device (e.g., a mouse or trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local area network (Local Area Network, LAN), wide area network (Wide Area Network, WAN) and the internet.
The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present application may be performed in parallel, sequentially, or in a different order, provided that the desired results of the technical solutions disclosed in the present application can be achieved, and are not limited herein.
The above embodiments do not limit the scope of the application. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present application are intended to be included within the scope of the present application.
Claims (12)
1. The cloud platform management method is characterized by comprising the following steps of:
acquiring a cloud service function, splitting the cloud service function into a plurality of meta-function modules, configuring a plurality of meta-components corresponding to the meta-function modules, wherein the meta-function modules form a meta-function library, and the corresponding meta-components form a meta-component library;
acquiring customer information, and calling a required meta-function module and a corresponding meta-component according to the customer information, wherein the corresponding meta-function module is called from the meta-function library according to the meta-function requirement information, and the corresponding meta-component is called from the meta-component library;
the component is a minimum unit which is separated from the same functional module from technical logic and can be configured independently;
acquiring a deployment file according to the called meta function module and the corresponding meta component;
and sending the deployment file to a plurality of corresponding sites to run the cloud service function.
2. The method as recited in claim 1, further comprising:
deleting repeated components in the fetched components to determine the supporting components.
3. The method of claim 1, wherein the obtaining the deployment file from the plurality of fetched meta-function modules and the corresponding plurality of meta-components comprises:
performing parameter configuration on the called meta-function module and the meta-component to obtain a meta-function configuration file and a meta-component configuration file;
acquiring a component deployment file according to the fetched meta-component;
the deployment files comprise the meta-function configuration file, the meta-component configuration file and the component deployment file.
4. The method as recited in claim 1, further comprising:
and detecting and verifying the running condition of the cloud service function deployed at the plurality of sites, and returning to the step of executing the plurality of meta-function modules and the corresponding plurality of meta-components required by the configuration according to the client information if the running condition is verified to be not passed.
5. The method according to claim 1, wherein the cloud service function includes a user management function and a charging function corresponding to an operation type;
the meta function module obtained by splitting the charging function comprises: the system comprises a fund account module, an order management module, a bill management module, a contract management module, a quota management module, a discount module and a cash security module;
the meta function module obtained by splitting the user management function comprises: the system comprises an account information management module, a fund 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.
6. A cloud platform management apparatus, comprising:
the function splitting module is used for acquiring a cloud service function and splitting the cloud service function into a plurality of meta-function modules;
the meta-function module configuration module is used for configuring meta-components corresponding to the meta-function modules, the meta-function modules form a meta-function library, and the corresponding meta-components form a meta-component library;
the system comprises a meta-function component calling module, a meta-function component calling module and a meta-function component, wherein the meta-function component calling module is used for acquiring customer information, calling a required meta-function module and a corresponding meta-component according to the customer information, and calling the corresponding meta-function module from the meta-function library and the corresponding meta-component from the meta-component library according to the meta-function requirement information;
the component is a minimum unit which is separated from the same functional module from technical logic and can be configured independently;
the deployment file acquisition module is used for acquiring a deployment file according to the called meta-function module and the corresponding meta-component;
and the function operation module is used for sending the deployment file to a plurality of corresponding sites so as to operate the cloud service function.
7. The apparatus of claim 6, wherein the meta-function component invocation module further comprises:
and the support component determining sub-module is used for deleting repeated components in the called components and determining the support component.
8. The apparatus of claim 6, wherein the deployment file acquisition module comprises:
the configuration file generation sub-module is used for carrying out parameter configuration on the called meta-function module and the meta-component to obtain a meta-function configuration file and a meta-component configuration file;
the component deployment file acquisition sub-module is used for acquiring a component deployment file according to the fetched meta-component;
the deployment files comprise the meta-function configuration file, the meta-component configuration file and the component deployment file.
9. The apparatus as recited in claim 6, further comprising:
and the function verification module is used for detecting and verifying the running condition of the cloud service functions deployed at the multiple sites, and returning to the step of executing the multiple meta-function modules and the corresponding multiple meta-components required by the configuration according to the client information if the verification is not passed.
10. The apparatus of claim 6, wherein the cloud service function comprises a user management function and a charging function corresponding to an operation type;
the meta function module obtained by splitting the charging function comprises: the system comprises a fund account module, an order management module, a bill management module, a contract management module, a quota management module, a discount module and a cash security module;
the meta function module obtained by splitting the user management function comprises: the system comprises an account information management module, a fund 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.
11. 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 to enable the at least one processor to perform the method of any one of claims 1-5.
12. A non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the method of any one of claims 1-5.
Priority Applications (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110180981.2A CN113014424B (en) | 2021-02-09 | 2021-02-09 | Cloud platform management method and device, electronic equipment and storage medium |
| TW110133171A TW202232395A (en) | 2021-02-09 | 2021-09-07 | Cloud platform management method, apparatus, electronic device, and storage medium |
| PCT/CN2021/117511 WO2022170760A1 (en) | 2021-02-09 | 2021-09-09 | Method and apparatus for cloud platform management, electronic device, and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110180981.2A CN113014424B (en) | 2021-02-09 | 2021-02-09 | Cloud platform management method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113014424A CN113014424A (en) | 2021-06-22 |
| CN113014424B true CN113014424B (en) | 2023-08-01 |
Family
ID=76401980
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110180981.2A Active CN113014424B (en) | 2021-02-09 | 2021-02-09 | Cloud platform management method and device, electronic equipment and storage medium |
Country Status (3)
| Country | Link |
|---|---|
| CN (1) | CN113014424B (en) |
| TW (1) | TW202232395A (en) |
| WO (1) | WO2022170760A1 (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113014424B (en) * | 2021-02-09 | 2023-08-01 | 中国银联股份有限公司 | Cloud platform management method and device, electronic equipment and storage medium |
| CN113821276B (en) * | 2021-10-11 | 2024-04-26 | 腾讯科技（深圳）有限公司 | Custom service management method and related device |
| CN115802321B (en) * | 2022-11-04 | 2024-04-05 | 中国联合网络通信集团有限公司 | Service function arrangement method, system, electronic equipment and storage medium |
| CN116860260A (en) * | 2023-04-26 | 2023-10-10 | 安元科技股份有限公司 | Tailorable operation and maintenance deployment method under micro front end architecture |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105162884A (en) * | 2015-09-25 | 2015-12-16 | 浪潮(北京)电子信息产业有限公司 | Cloud management platform based on micro-service architecture |
| CN108073419A (en) * | 2018-01-04 | 2018-05-25 | 广州供电局有限公司 | A kind of implementation method in electric power enterprise mobile application common component storehouse |
| CN111930355A (en) * | 2020-08-12 | 2020-11-13 | 创意信息技术股份有限公司 | Web back-end development framework and construction method thereof |
| CN112256348A (en) * | 2020-10-23 | 2021-01-22 | 北京浪潮数据技术有限公司 | Cloud service platform creation method and system, electronic equipment and storage medium |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103164286A (en) * | 2013-03-12 | 2013-06-19 | 无锡云动科技发展有限公司 | Implement method, resource manager and cloud calculating system of cloud computing platform arrangement |
| US20170236084A1 (en) * | 2013-12-12 | 2017-08-17 | NetSuite Inc. | System and methods for implementing custom transactions within a multi-tenant platform |
| CN104270417B (en) * | 2014-09-12 | 2017-11-10 | 湛羽 | A kind of integrated service based on cloud computing provides system and method |
| US11973758B2 (en) * | 2016-09-14 | 2024-04-30 | Microsoft Technology Licensing, Llc | Self-serve appliances for cloud services platform |
| US10547682B2 (en) * | 2016-11-10 | 2020-01-28 | Adobe Inc. | Dynamically scaling application components using microservices |
| CN110113417A (en) * | 2019-05-08 | 2019-08-09 | 苏州浪潮智能科技有限公司 | Cloud service combination and dispatching platform based on OpenStack |
| CN111147572B (en) * | 2019-12-24 | 2022-04-15 | 中国建设银行股份有限公司 | Cloud customer service platform management system and method |
| CN113014424B (en) * | 2021-02-09 | 2023-08-01 | 中国银联股份有限公司 | Cloud platform management method and device, electronic equipment and storage medium |
-
2021
- 2021-02-09 CN CN202110180981.2A patent/CN113014424B/en active Active
- 2021-09-07 TW TW110133171A patent/TW202232395A/en unknown
- 2021-09-09 WO PCT/CN2021/117511 patent/WO2022170760A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105162884A (en) * | 2015-09-25 | 2015-12-16 | 浪潮(北京)电子信息产业有限公司 | Cloud management platform based on micro-service architecture |
| CN108073419A (en) * | 2018-01-04 | 2018-05-25 | 广州供电局有限公司 | A kind of implementation method in electric power enterprise mobile application common component storehouse |
| CN111930355A (en) * | 2020-08-12 | 2020-11-13 | 创意信息技术股份有限公司 | Web back-end development framework and construction method thereof |
| CN112256348A (en) * | 2020-10-23 | 2021-01-22 | 北京浪潮数据技术有限公司 | Cloud service platform creation method and system, electronic equipment and storage medium |
Non-Patent Citations (3)
| Title |
|---|
| Wang Bin.Research on Digital Publishing Application System Based on Micro-Service Architecture.《ICNCC '17: Proceedings of the 2017 VI International Conference on Network, Communication and Computing》.2017,第 140–144页. * |
| 微服务架构在网络教学平台中的应用研究;曹晓春;;科技与创新(第05期);全文 * |
| 面向微服务的江苏农业行政执法系统研究;毛林;成维莉;余云飞;程涛;;安徽农业科学(第29期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| TW202232395A (en) | 2022-08-16 |
| WO2022170760A1 (en) | 2022-08-18 |
| CN113014424A (en) | 2021-06-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113014424B (en) | Cloud platform management method and device, electronic equipment and storage medium | |
| CN110310034B (en) | Service arrangement and business flow processing method and device applied to SaaS | |
| EP3155576B1 (en) | Providing a subscription for a service using an existing subscription | |
| CN107590186B (en) | Method for managing and executing data processing policy and policy engine system | |
| CN111930521A (en) | Method and device for deploying application, electronic equipment and readable storage medium | |
| US10803411B1 (en) | Enterprise platform deployment | |
| CN111831420A (en) | Method and device for task scheduling, electronic equipment and computer-readable storage medium | |
| CN104246741A (en) | Orchestrating hybrid cloud services | |
| AU2016322817B2 (en) | Application provisioning system for requesting configuration updates for application objects across data centers | |
| US10817387B2 (en) | Auto point in time data restore for instance copy | |
| US9912760B2 (en) | Dynamically generating solution stacks | |
| WO2015195590A1 (en) | Tenant provisioning for testing a production multi-tenant service | |
| WO2021111235A1 (en) | Microservices change management and analytics | |
| CN113361838A (en) | Business wind control method and device, electronic equipment and storage medium | |
| CN111698326B (en) | Method and device for determining cost attribution of cloud service resources | |
| US10015050B2 (en) | Distributed computing system | |
| CN111258567A (en) | Service code development processing method and device | |
| CN109345249A (en) | A kind of payment fail processing method and device | |
| WO2023169193A1 (en) | Method and device for generating smart contract | |
| US11893383B2 (en) | Configuration properties management for software | |
| CN116664060A (en) | Method, system and device for generating expense reimbursement basic data | |
| US11074273B2 (en) | Framework for continuous processing of a set of documents by multiple software applications | |
| US9542171B2 (en) | Managing an application modification process | |
| CN115827051A (en) | Software integration management system, method and server | |
| WO2024049456A1 (en) | Method and system for testing automation in marketplace |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40047892 Country of ref document: HK |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |