CN110233750B - Private cloud management system and method - Google Patents

Abstract

Embodiments of the present invention provide a private cloud management system and method. The system includes: a management platform and at least two subsystems; wherein, the subsystems include a routing module and a private cloud; the management platform communicates with the private cloud via the routing module; each of the routing The module communicates with the management platform through a preset general communication protocol; within the subsystem, the routing module communicates with the private cloud through a non-general communication protocol corresponding to the private cloud. The embodiment of the present invention solves the problem of low management efficiency and high operation and maintenance cost in the prior art, where the management mode of one-to-one correspondence between the management platform and the private cloud leads to a large number of private clouds.

Description

Private cloud management system and method

technical field

Embodiments of the present invention relate to the technical field of operation and maintenance, and in particular to a private cloud management system and method.

Background technique

With the rapid development of the cloud computing industry, as an important part of the private cloud (Private Clouds) also occupies a large market share. Specifically, a private cloud is built for one user's sole use, thus providing effective control over data, security, and service quality. The core attribute of a private cloud is dedicated resources. For a private cloud, users own the infrastructure and can control the deployment of applications on this infrastructure. In addition, a private cloud can be deployed within the firewall of a corporate data center or in a secure colocation facility.

As for the private clouds of different network security domains, because they are built on different hardware resources, or the virtual local area network (Virtual Local Area Network, VLAN) of the application is different, the private clouds of different network security domains are isolated from each other. Therefore, when managing mutually isolated private clouds, it is usually necessary to build a corresponding management platform for each private cloud for separate management, as shown in Figure 1. The architecture diagram of the management platform and private cloud, private cloud 1, 2, 3 respectively correspond to a management platform 1, 2, 3.

However, in practical applications, the management method of one-to-one correspondence between the management platform and the private cloud, when the number of private clouds is large, the number of management platforms will increase accordingly, which usually leads to low management efficiency and high operation and maintenance costs.

Contents of the invention

Embodiments of the present invention provide a private cloud management system and method, which are used to solve the problem of one-to-one management between management platforms and private clouds in the prior art. When the number of private clouds is large, management efficiency is low and operation and maintenance costs are high. high question.

On the one hand, an embodiment of the present invention provides a private cloud management system, the system includes: a management platform and at least two subsystems;

Wherein, the subsystem includes a routing module and a private cloud;

The management platform communicates with the private cloud via the routing module;

Each of the routing modules communicates with the management platform through a preset general communication protocol;

Inside the subsystem, the routing module communicates with the private cloud through a non-universal communication protocol corresponding to the private cloud.

On the one hand, an embodiment of the present invention provides a private cloud management method, which is applied to the above-mentioned private cloud management system, and the method includes:

controlling the communication between the management platform and the private clouds of at least two subsystems via the routing module, including: controlling the communication between each routing module and the management platform through a preset general communication protocol, and controlling the The routing module is inside the subsystem and communicates with the private cloud through a non-universal communication protocol corresponding to the private cloud.

On the other hand, an embodiment of the present invention also provides an electronic device, including a memory, a processor, a bus, and a computer program stored in the memory and operable on the processor. When the processor executes the program, the above-mentioned Steps in a private cloud management approach.

In yet another aspect, an embodiment of the present invention also provides a non-transitory computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the steps in the above private cloud management method are implemented.

The private cloud management system and method provided by the embodiments of the present invention perform protocol conversion through the routing module, so that the management platform can communicate with the private cloud among multiple subsystems; the routing modules of each subsystem adopt a unified general communication protocol To communicate with the cloud management platform, the routing modules of each subsystem communicate with their respective private clouds using a preset non-universal communication protocol to realize the transmission of system uplink data and downlink data, and realize the management platform to control multiple private clouds at the same time Manage, improve management efficiency, reduce operation and maintenance costs; avoid the existence of multiple management platforms, waste resources, and increase the difficulty of operation and maintenance.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description These are some embodiments of the present invention. Those skilled in the art can also obtain other drawings based on these drawings without creative work.

FIG. 1 is a schematic diagram of a scene of a private cloud and a management platform in the background technology;

Fig. 2 is the architectural diagram of the private cloud management system provided by the embodiment of the present invention;

FIG. 3 is a schematic structural diagram of a server provided by an embodiment of the present invention.

Explanation of reference signs:

201. Management platform; 202. Subsystem; 2021. Routing module; 2022. Private cloud.

Detailed ways

In order to make the technical problems, technical solutions and advantages to be solved by the present invention clearer, the following will describe in detail with reference to the drawings and specific embodiments. In the following description, specific details, such as specific configurations and components, are provided only to assist in a comprehensive understanding of the embodiments of the present invention. Accordingly, those of ordinary skill in the art should recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted for clarity and conciseness.

It should be understood that reference throughout this specification to "an embodiment" or "an embodiment" means that a particular feature, structure, or characteristic related to the embodiment is included in at least one embodiment of the present invention. Thus, appearances of "in an embodiment" or "in an embodiment" throughout the specification do not necessarily refer to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments.

In various embodiments of the present invention, it should be understood that the sequence numbers of the following processes do not mean the order of execution, and the order of execution of each process should be determined by its functions and internal logic, rather than implementing the present invention. The implementation of the examples constitutes no limitation.

In the embodiments provided in this application, it should be understood that "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B may also be determined according to A and/or other information.

Fig. 2 shows a schematic diagram of a private cloud management system provided by an embodiment of the present invention.

As shown in FIG. 2, the private cloud management system provided by the embodiment of the present invention includes: a management platform 201 and at least two subsystems 202. In FIG. 2, the subsystem 202 includes subsystems A, B, and C; one management platform 201 can It communicates with multiple subsystems 202 to manage and control the subsystems 202, so as to reduce the number of management platforms 201 and reduce operation and maintenance costs.

Wherein, taking subsystem C in FIG. 2 as an example, the subsystem 202 includes a routing module 2021 and a private cloud 2022; each routing module 2021 communicates with the management platform 201 and the private cloud 2022 respectively, that is, the The management platform 201 communicates with the private cloud 2022 via the routing module 2021; the routing module 2021 cuts off the direct access between the management platform 201 and the private cloud 2022, adopts a protocol proxy mode, and is responsible for the management platform 201 and the private cloud. Access and O&M security between Cloud 2022, O&M security such as blocking illegal access and malicious attacks.

The routing module 2021 communicates with the management platform 201 through a preset general communication protocol, that is, the routing modules 2021 of different subsystems 202 communicate with the management platform 201 using the same communication protocol.

The management platform 201 needs to communicate with the hosts of each node in the private cloud 2022 through the routing module 2021, complete various management tasks, and issue instructions to the private cloud 2022; The running status of each container (docker), etc.

Because each management platform 201 manages a plurality of private clouds 2022, and because the communication network and hardware environment between each private cloud 2022 may be different, different communication protocols are usually used between each routing module 2021 and the corresponding private cloud 2022, Therefore, for the management platform 201, it is difficult to adopt a unified communication protocol to communicate with the private cloud 2022; The routing module 2021 of each subsystem 202 converts the uplink data through a common communication protocol, and then sends it to the management platform 201 .

Inside the subsystem, the routing module 2021 communicates with the private cloud 2022 through a non-universal communication protocol corresponding to the private cloud; wherein, for each subsystem 202, it may have its own dedicated The communication protocol is used for communication between the routing module 2021 and the private cloud 2022; as shown in Figure 2, the private cloud A communicates with the routing module A through a non-general communication protocol A, and the private cloud B communicates with the routing module B through a non-general communication protocol B , the private cloud C communicates with the routing module C through the non-universal communication protocol C; in this way, the routing module 2021 converts the downlink data according to the non-universal communication protocol, and then sends it to the private cloud 2022.

It can be understood that the non-universal communication protocols of the various subsystems 202 may be the same or different.

In the above embodiments of the present invention, protocol conversion is performed through the routing module 2021, so that the management platform 201 can communicate with the private cloud 2022 between multiple subsystems 202; the routing module 2021 of each subsystem 202 adopts a unified general communication protocol Communication with the cloud management platform 201, the routing module 2021 of each subsystem 202 communicates with its own private cloud 2022 using a preset non-universal communication protocol to complete the transmission of system uplink data and downlink data, and realize the management platform 201 at the same time Manage multiple private clouds 2022, improve management efficiency, and reduce operation and maintenance costs; avoid the existence of multiple management platforms 201, waste resources, and increase the difficulty of operation and maintenance. The embodiment of the present invention solves the problem of low management efficiency and high operation and maintenance costs in the prior art where the management platform 201 corresponds to the private cloud 2022 in a one-to-one management manner when the number of private clouds 2022 is large.

Preferably, in the embodiment of the present invention, the routing module 2021 is a bastion machine, and the bastion machine and each node inside the corresponding managed private cloud 2022 are in the network security domain of the same subsystem 202, and the bastion machine has network connectivity with each node properties to communicate with each node. Moreover, the security level of the bastion host is relatively high, which is conducive to the operation and maintenance work.

Optionally, in the embodiment of the present invention, when the management platform 201 issues an instruction to the private cloud 2022, the instruction to be issued is converted by the general communication protocol and transmitted to the routing module 2021;

The routing module 2021 converts the instruction to be issued to the private cloud 2022 through the non-universal communication protocol.

Wherein, the non-universal communication protocol is used for communication between the routing module 2021 and the private cloud 2022, and for each subsystem 202, it may have its own dedicated communication protocol (ie non-universal communication protocol) for the routing module 2021 and the private cloud 2022 for communication; the non-universal communication protocol of each subsystem 202 may be the same or different.

For the instructions or other downlink data issued by the management platform 201, the management platform 201 first converts the instructions to be issued into a unified data format through the general communication protocol, and then transmits them to the routing module 2021; The instructions to be issued in the data format are converted into a data format recognizable by the private cloud 2022 after being converted by the non-universal communication protocol corresponding to the private cloud 2022, and transmitted to the private cloud 2022.

Optionally, in the embodiment of the present invention, when the private cloud 2022 uploads data to the management platform 201, the data to be uploaded is converted by the non-universal communication protocol and transmitted to the routing module 2021;

The routing module 2021 converts the data to be uploaded to the management platform 201 through the general communication protocol.

Similarly, when the private cloud 2022 uploads data to the management platform 201, the private cloud 2022 first converts the data to be uploaded into a data format recognizable by the routing module 2021 through the non-universal communication protocol, and then transmits it to the routing module 2021 ; The routing module 2021 converts the data to be uploaded to the management platform 201 after conversion through a unified general communication protocol.

Optionally, in the embodiment of the present invention, the management platform 201 performs preset management operations on the nodes inside the private cloud 2022 according to the data uploaded by the private cloud 2022, completes various management tasks, and reports to the private cloud Issue instructions in 2022;

The preset management operations include: statistics of computing resources, collection of node status information, and/or monitoring of the running status of each application container on the node, etc., for private cloud 2022 management monitoring and visual presentation.

Further, in the embodiment of the present invention, the management platform 201 is provided with a management account for each of the subsystems 202, so as to manage and maintain the private cloud 2022 of each subsystem 202.

As an example, the communication protocol of HTTP+Json is uniformly used as a general communication protocol between the management platform 201 and the routing module 2021; the web service protocol is used as a non-general communication protocol between the routing module 2021 and the private cloud 2022 to communicate;

The routing module 2021 can convert the HTTP+Json protocol instructions issued by the management platform 201 into web service protocol data through the webservice protocol, and interact with each node in the corresponding managed private cloud 2022; The web service protocol data uploaded by the private cloud 2022 is uploaded to the management platform 201 after being converted by the HTTP+Json protocol.

In the above embodiments of the present invention, protocol conversion is performed through the routing module 2021, so that the management platform 201 can communicate with the private cloud 2022 between multiple subsystems 202; the routing module 2021 of each subsystem 202 adopts a unified general communication protocol Communication with the cloud management platform 201, the routing module 2021 of each subsystem 202 communicates with its own private cloud 2022 using a preset non-universal communication protocol to realize the transmission of system uplink data and downlink data, and realize the management platform 201 at the same time Manage multiple private clouds 2022, improve management efficiency, and reduce operation and maintenance costs; avoid the existence of multiple management platforms 201, waste resources, and increase the difficulty of operation and maintenance. The embodiment of the present invention solves the problem of low management efficiency and high operation and maintenance costs in the prior art where the management platform 201 corresponds to the private cloud 2022 in a one-to-one management manner when the number of private clouds 2022 is large.

The private cloud management system provided by the embodiment of the present invention is described above, and the private cloud management method provided by the embodiment of the present invention will be described below with reference to the accompanying drawings.

An embodiment of the present invention provides a private cloud management method, which is applied to the above-mentioned private cloud management system. Referring to FIG. 2, the private cloud management system includes: a management platform 201 and at least two subsystems 202;

The methods include:

Controlling the communication between the management platform 201 and the private cloud 2022 of at least two subsystems 202 via the routing module 2021 includes: controlling each routing module 2021 and the management platform 201 through a preset general communication protocol Communication and control The routing module 2021 communicates with the private cloud 2022 within the subsystem 202 through a non-universal communication protocol corresponding to the private cloud 2022 .

Wherein, as shown in FIG. 2 , each routing module 2021 communicates with the management platform 201 and the private cloud 2022 respectively, that is, the management platform 201 communicates with the private cloud 2022 via the routing module 2021 The routing module 2021 cuts off the direct access between the management platform 201 and the private cloud 2022, adopts the mode of protocol proxy, and is responsible for the access and operation and maintenance security between the management platform 201 and the private cloud 2022, such as intercepting illegal access and attack on purpose.

Controlling the communication between the routing module 2021 and the management platform 201 through a preset general communication protocol, that is, controlling the routing modules 2021 of different subsystems 202 to communicate with the management platform 201 using the same communication protocol.

The management platform 201 needs to communicate with the hosts of each node in the private cloud 2022 through the routing module 2021 to complete various management tasks and issue instructions to the private cloud 2022. The running status of the container (docker), etc.

Because each management platform 201 corresponds to multiple private clouds 2022, and because the communication network and hardware environment between each private cloud 2022 may be different, different communication protocols are usually used between each routing module 2021 and the corresponding private cloud 2022 , for the management platform 201, it is difficult to use a unified communication protocol to communicate with the private cloud 2022; and in order to realize the communication between each private cloud 2022 and the management platform 201, for the uplink data sent by the private cloud 2022 to the management platform 201, The routing module 2021 of each subsystem 202 converts the uplink data through a common communication protocol, and then sends it to the management platform 201 .

And, control the communication between the routing module 2021 and the private cloud 2022 through a preset non-common communication protocol; for each subsystem 202, it may have its own dedicated communication protocol for the routing module 2021 and the private cloud Communication between 2022; as shown in Figure 2, private cloud A communicates with routing module A through non-general communication protocol A, private cloud B communicates with routing module B through non-general communication protocol B, and private cloud C communicates with routing module B through non-general communication protocol C Communicate with the routing module C; in this way, the routing module 2021 converts the downlink data according to the non-universal communication protocol, and then sends it to the private cloud 2022.

It can be understood that the non-universal communication protocols of the various subsystems 202 may be the same or different.

Optionally, in the embodiment of the present invention, the method further includes:

When controlling the management platform 201 to issue instructions to the private cloud 2022, transfer the instructions to be issued to the routing module 2021 after being converted by the general communication protocol;

Controlling the routing module 2021 to transfer the instruction to be issued to the private cloud 2022 after converting it through the non-universal communication protocol.

Wherein, for the instructions issued by the management platform 201 or other downlink data, the control management platform 201 first converts the instructions to be issued into a unified data format through the general communication protocol, and then transmits them to the routing module 2021; The routing module 2021 then converts the instruction to be issued into a data format recognizable by the private cloud 2022 through a non-universal communication protocol corresponding to the private cloud 2022 , and transmits it to the private cloud 2022 .

Optionally, in the embodiment of the present invention, the method further includes: when controlling the private cloud 2022 to upload data to the management platform 201, transfer the data to be uploaded to the router after being converted by the non-universal communication protocol Module 2021;

Controlling the routing module 2021 to transfer the data to be uploaded to the management platform 201 after conversion through the general communication protocol.

Wherein, when controlling the private cloud 2022 to upload data to the management platform 201, the data to be uploaded is first converted into a data format recognizable by the routing module 2021 through the non-universal communication protocol, and then transmitted to the routing module 2021; The routing module 2021 transfers the data to be uploaded to the management platform 201 after being converted through a unified general communication protocol.

In the above embodiments of the present invention, the protocol conversion is performed by controlling the routing module 2021, so that the management platform 201 can communicate with the private cloud 2022 between multiple subsystems 202; the routing module 2021 of each subsystem 202 adopts a unified general communication The protocol communicates with the cloud management platform 201, and the routing module 2021 of each subsystem 202 communicates with its own private cloud 2022 using a preset non-universal communication protocol to realize the transmission of system uplink data and downlink data, and realize the management platform 201 Manage multiple private clouds 2022 at the same time, improve management efficiency, and reduce operation and maintenance costs; avoid the existence of multiple management platforms 201, waste resources, and increase the difficulty of operation and maintenance. The embodiment of the present invention solves the problem of low management efficiency and high operation and maintenance costs in the prior art where the management platform 201 corresponds to the private cloud 2022 in a one-to-one management manner when the number of private clouds 2022 is large.

On the other hand, an embodiment of the present invention also provides an electronic device, including a memory, a processor, a bus, and a computer program stored in the memory and operable on the processor. When the processor executes the program, the above-mentioned Steps in a private cloud management approach.

An example is as follows. When the electronic device is a server, FIG. 3 illustrates a schematic diagram of a physical structure of the server.

As shown in Figure 3, this server can comprise: processor (processor) 310, communication interface (Communications Interface) 320, memory (memory) 330 and communication bus 340, wherein, processor 310, communication interface 320, memory 330 through communication The bus 340 implements mutual communication. The processor 310 can call logic instructions in the memory 330 to perform the following methods:

controlling the communication between the management platform and the private clouds of at least two subsystems via the routing module, including: controlling the communication between each routing module and the management platform through a preset general communication protocol, and controlling the The routing module is inside the subsystem and communicates with the private cloud through a non-universal communication protocol corresponding to the private cloud.

In addition, the above-mentioned logic instructions in the memory 330 may be implemented in the form of software functional units and may be stored in a computer-readable storage medium when sold or used as an independent product. Based on this understanding, the essence of the technical solution of the present invention or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disc, etc., which can store program codes. .

In yet another aspect, an embodiment of the present invention also provides a non-transitory computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the steps in the above private cloud management method are implemented.

The device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in One place, or it can be distributed to multiple network elements. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. It can be understood and implemented by those skilled in the art without any creative efforts.

Through the above description of the implementations, those skilled in the art can clearly understand that each implementation can be implemented by means of software plus a necessary general hardware platform, and of course also by hardware. Based on this understanding, the essence of the above technical solution or the part that contributes to the prior art can be embodied in the form of software products, and the computer software products can be stored in computer-readable storage media, such as ROM/RAM, magnetic discs, optical discs, etc., including several instructions to make a computer device (which may be a personal computer, server, or network device, etc.) execute the methods described in various embodiments or some parts of the embodiments.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still be Modifications are made to the technical solutions described in the foregoing embodiments, or equivalent replacements are made to some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present invention.

Claims (10)

1. A private cloud management system, characterized in that it comprises: a management platform and at least two subsystems; Wherein, the subsystem includes a routing module and a private cloud; The management platform communicates with the private cloud via the routing module; each routing module and the corresponding private cloud usually use different communication protocols; Each of the routing modules communicates with the management platform through a preset general communication protocol; Inside the subsystem, the routing module communicates with the private cloud through a non-universal communication protocol corresponding to the private cloud; The routing module cuts off the direct access between the management platform and the private cloud, and takes charge of the access and operation and maintenance security between the management platform and the private cloud by means of a protocol agent. 2. The system of claim 1, wherein: The routing module is a bastion host. 3. The system according to claim 1, wherein when the management platform issues an instruction to the private cloud, the instruction to be issued is converted by the general communication protocol and then transmitted to the routing module; The routing module converts the instruction to be issued through the non-universal communication protocol and transmits it to the private cloud. 4. The system according to claim 1, wherein when the private cloud uploads data to the management platform, the data to be uploaded is converted by the non-universal communication protocol and then transmitted to the routing module; The routing module converts the data to be uploaded through the general communication protocol and transmits it to the management platform. 5. The system according to claim 4, wherein the management platform performs preset management operations on nodes inside the private cloud according to the data uploaded by the private cloud; The preset management operations include: counting computing resources, collecting node status information and/or monitoring the running status of each application container on the node. 6. The system according to claim 1, wherein a management account for each of the subsystems is set in the management platform. 7. A private cloud management method, applied to the private cloud management system according to any one of claims 1 to 6, characterized in that the method comprises: controlling the communication between the management platform and the private clouds of at least two subsystems via the routing module, including: controlling the communication between each routing module and the management platform through a preset general communication protocol; and controlling the communication between the routing module and the management platform; The routing module is inside the subsystem and communicates with the private cloud through a non-universal communication protocol corresponding to the private cloud; wherein, the routing module cuts off the communication between the management platform and the private cloud The direct access adopts the method of protocol proxy, which is responsible for the access and operation and maintenance security between the management platform and the private cloud; wherein, each routing module and the corresponding private cloud usually adopt different communication protocols. 8. The method according to claim 7, further comprising: When controlling the management platform to issue instructions to the private cloud, transfer the instructions to be issued to the routing module after being converted by the general communication protocol; Controlling the routing module to convert the instruction to be issued to the private cloud through the non-universal communication protocol; and / or When controlling the private cloud to upload data to the management platform, transfer the data to be uploaded to the routing module after conversion through the non-universal communication protocol; Controlling the routing module to convert the data to be uploaded through the general communication protocol and then transmit it to the management platform. 9. An electronic device, characterized in that it comprises a memory, a processor, a bus, and a computer program stored on the memory and operable on the processor, and the processor according to claim 7 or 8 is implemented when the program is executed. Steps in the private cloud management methodology described in . 10. A non-transitory computer-readable storage medium, on which a computer program is stored, characterized in that: when the program is executed by a processor, the steps in the private cloud management method as described in claim 7 or 8 are implemented .

Images