CN108156005B - Information configuration method, device and system - Google Patents

Abstract

The invention provides an information configuration method, an information configuration device and an information configuration system. And subnet information corresponding to the bottom cloud platform can be acquired from the subnet planning information, and when the fact that the bottom cloud platform creates a network but does not create a subnet is judged according to the subnet information, the subnet is created for the bottom cloud platform, so that after the network planning information and the subnet planning information of the hybrid cloud platform are planned in advance, the bottom cloud platform without the network and without the subnet can be accurately determined, the network and the subnet are automatically created for the bottom cloud platform, and the network and the subnet are automatically and accurately created for the bottom cloud platform.

Description

Information configuration method, device and system

Technical Field

The present invention relates to the field of hybrid cloud technologies, and in particular, to an information configuration method, apparatus, and system.

Background

Cloud computing is an increasing, usage and delivery model for internet-based related services, typically involving the provision of dynamically scalable and often virtualized resources over the internet. With the development of cloud computing technology, a plurality of cloud platforms of different technology types appear, for example, according to the technology types supported by the cloud platforms, the cloud platforms can be divided into an Openstack cloud platform, a Qcloud cloud platform, or an AWS cloud platform, and according to the service types of the enterprises, the cloud platforms can be divided into a private cloud platform and a public cloud platform.

The hybrid cloud platform is integrated with different types of cloud platforms, namely the hybrid cloud platform can provide external services and internal services, the hybrid cloud platform is built on a plurality of cloud platforms with different technical types, and the plurality of cloud platforms with different technical types for building the hybrid cloud platform are respectively called as bottom cloud platforms.

For each underlying cloud platform, a network and a subnet are created for the underlying cloud platform manually in the prior art, so an information configuration method is urgently needed to automatically and accurately create the network and the subnet for the underlying cloud platform.

Disclosure of Invention

In view of this, the present invention provides an information configuration method, apparatus and system to automatically and accurately create a network and a subnet for an underlying cloud platform. The technical scheme is as follows:

the invention provides an information configuration method, which comprises the following steps:

synchronizing network planning information and subnet planning information of the hybrid cloud platform, wherein the network planning information is used for indicating the network planning of the hybrid cloud platform, the subnet planning information is used for indicating the subnet planning of the hybrid cloud platform, and the hybrid cloud platform is constructed on at least one underlying cloud platform;

acquiring network information corresponding to the bottom cloud platform from the network planning information, and acquiring subnet information corresponding to the bottom cloud platform from the subnet planning information;

judging whether a network is established on the bottom cloud platform according to the network information corresponding to the bottom cloud platform to obtain a first judgment result;

when the first judgment result indicates that the network is not established on the bottom cloud platform, establishing the network for the bottom cloud platform according to the network information corresponding to the bottom cloud platform;

judging whether a network is established on the bottom cloud platform or not and whether a subnet is established on the bottom cloud platform or not according to the subnet information corresponding to the bottom cloud platform to obtain a second judgment result;

and when the second judgment result indicates that the bottom cloud platform creates a network but does not create a subnet, creating a subnet for the bottom cloud platform according to the subnet information corresponding to the bottom cloud platform.

The present invention also provides an information configuration apparatus, the apparatus comprising: the system comprises a synchronization unit, a first layer cloud platform and a second layer cloud platform, wherein the synchronization unit is used for synchronizing network planning information and subnet planning information of the hybrid cloud platform, the network planning information is used for indicating the network planning of the hybrid cloud platform, the subnet planning information is used for indicating the subnet planning of the hybrid cloud platform, and the hybrid cloud platform is constructed on at least one underlying cloud platform;

the acquiring unit is used for acquiring network information corresponding to the bottom cloud platform from the network planning information and acquiring subnet information corresponding to the bottom cloud platform from the subnet planning information;

the first judging unit is used for judging whether a network is established on the bottom cloud platform according to the network information corresponding to the bottom cloud platform to obtain a first judging result;

the first establishing unit is used for establishing a network for the bottom cloud platform according to the network information corresponding to the bottom cloud platform when the first judging result indicates that the bottom cloud platform is not established with the network;

the second judging unit is used for judging whether a network is established on the bottom cloud platform or not and whether a subnet is established on the bottom cloud platform or not according to the subnet information corresponding to the bottom cloud platform to obtain a second judging result;

and the second creating unit is used for creating a subnet for the bottom cloud platform according to the subnet information corresponding to the bottom cloud platform when the second judgment result indicates that the bottom cloud platform creates a network but does not create a subnet.

The present invention also provides an information configuration system, the system comprising: the system comprises a management center platform and a hybrid cloud platform, wherein the hybrid cloud platform is built on at least one underlying cloud platform; the hybrid cloud platform comprises the information processing device;

the management center platform comprises center equipment and a database, wherein the database is used for storing network planning information and subnet planning information of the hybrid cloud platform;

and the central equipment is used for uniformly managing the network planning information and the subnet planning information of the hybrid cloud platform.

Based on the technical scheme, the information configuration method provided by the embodiment of the invention can acquire the network information corresponding to the bottom cloud platform from the network planning information after the network planning information and the subnet planning information of the hybrid cloud platform are synchronized, and when the fact that the bottom cloud platform does not establish the network is judged according to the network information, the network is established for the bottom cloud platform. And subnet information corresponding to the bottom cloud platform can be acquired from the subnet planning information, and when the fact that the bottom cloud platform creates a network but does not create a subnet is judged according to the subnet information, the subnet is created for the bottom cloud platform, so that after the network planning information and the subnet planning information of the hybrid cloud platform are planned in advance, the bottom cloud platform without the network and without the subnet can be accurately determined, the network and the subnet are automatically created for the bottom cloud platform, and the network and the subnet are automatically and accurately created for the bottom cloud platform.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.

FIG. 1 is a diagram of a system architecture according to an embodiment of the present invention;

fig. 2 is a flowchart of an information configuring method according to an embodiment of the present invention;

fig. 3 is a schematic diagram of a management center platform and a plurality of hybrid cloud platforms according to an embodiment of the present invention;

FIG. 4 is a schematic diagram of an interface INetManager according to an embodiment of the present invention;

FIG. 5 is a diagram illustrating a parameter Region provided by an embodiment of the present invention;

fig. 6 is a schematic diagram of a parameter Network provided in an embodiment of the present invention;

FIG. 7 is a diagram illustrating a network-related configuration file according to an embodiment of the present invention;

FIG. 8 is a diagram of an interface ISubNetManager according to an embodiment of the present invention;

fig. 9 is a schematic diagram of a parameter SubNet according to an embodiment of the present invention;

fig. 10 is a schematic diagram of a configuration file related to a subnet provided by an embodiment of the present invention;

FIG. 11 is a schematic diagram of creating a network according to an embodiment of the present invention;

fig. 12 is a schematic diagram of creating a subnet according to an embodiment of the present invention;

FIG. 13 is a diagram illustrating synchronization information provided by an embodiment of the present invention;

fig. 14 is a schematic structural diagram of an information configuring apparatus according to an embodiment of the present invention;

fig. 15 is a schematic structural diagram of a synchronization unit in an information configuration apparatus according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Fig. 1 is an architecture diagram of a system for implementing an information configuration method according to an embodiment of the present invention, and referring to fig. 1, the system may include: management center platform 10 and mixed cloud platform 20, management center platform 10 includes: a central device 30, a first database 40, a second database 50, a second database 60, and a first network interface 70.

The hybrid cloud platform 20 is built on a plurality of underlying cloud platforms, such as the hybrid cloud platform in fig. 1, which is built on an Openstack-based private cloud platform, a Qcloud-based private cloud platform, an AWS-based private cloud platform, and a public cloud platform, and the hybrid cloud platform 20 includes: a second network interface 80, a synchronous distribution device 90 and a local database 100.

The central device 30 is configured to manage planning information of each hybrid cloud platform, such as configuration information of network devices entering the cloud, network planning information of each hybrid cloud platform, and subnet planning information of each hybrid cloud platform. Specifically, the configuration information of the network device entering the cloud includes: managing configuration information of network equipment such as a switch and a router which enter the cloud; the network planning information of each hybrid cloud platform comprises: constructing networks corresponding to a plurality of bottom cloud platforms of the hybrid cloud platform (namely mapping relations between the networks and the bottom cloud platforms) and network identification information corresponding to the networks, wherein the network identification information can be vlan ID (virtual network identification); the subnet planning information of each hybrid cloud platform includes: constructing sub-networks corresponding to a plurality of bottom cloud platforms of the hybrid cloud platform (i.e. the mapping relationship between the sub-networks and the network) and sub-network identification information corresponding to the sub-networks, where the sub-network identification information may be Cidr (class Inter-Domain Routing) information, and the sub-networks are independent network segments in the network, and thus the sub-network planning information of each hybrid cloud platform further includes: network identification information of the network.

A first database 40 for storing configuration information of the network device entering the cloud; a second database 50 for storing network planning information of each hybrid cloud platform; and a third database 60 for storing subnet planning information of each hybrid cloud platform.

The first network Interface 70 is an external Interface provided by the management center platform 10, such as an Application Programming Interface (API), and other platforms or devices may obtain information from the first database 40, the second database 50, and the third database 60 through the first network Interface 70. A user can plan the hybrid cloud platform through a client, for example, plan which underlying cloud platforms the hybrid cloud platform is built on, what the network devices entering the cloud have, what information is configured for the hybrid cloud platform, what the underlying cloud platforms correspond to, what the network identification information of the network is, what the underlying cloud platforms correspond to, what the subnet identification information is, and these pieces of information are regarded as planning information of the hybrid cloud platform, and are sent to the first network interface 70 by the client, and then sent to the central device 30 through the first network interface 70, so as to add, delete, and modify information in the first database 40, the second database 50, and the third database 60. Of course, the information in the first database 40, the second database 50 and the third database 60 may be transmitted to the client through the first network interface 70 for display.

The synchronous distribution device 90 is configured to synchronize the network planning information and the subnet planning information in the management center platform 10 into the local database 100 of the hybrid cloud platform 20, and to process the network and the subnet corresponding to the underlying cloud platform according to the synchronized network planning information and subnet planning information in the local database 100.

The second network interface 80 is an external interface provided by the hybrid cloud platform 20, and the client can access the synchronous distribution device 90 through the second network interface to obtain network planning information and subnet planning information of the hybrid cloud platform, such as the network information and subnet information corresponding to the underlying cloud platform.

The information configuration method provided by the embodiment of the present invention is mainly implemented by the synchronous distribution device in the system architecture shown in fig. 1, and the information configuration method provided by the embodiment of the present invention is introduced from the viewpoint of processing of the synchronous distribution device on one underlying cloud platform in the hybrid cloud platform. As shown in fig. 2, which shows a flowchart of an information configuration method provided in an embodiment of the present invention, the method may include the following steps:

201: and synchronizing the network planning information and the subnet planning information of the hybrid cloud platform, wherein the network planning information is used for indicating the network planning of the hybrid cloud platform, the subnet planning information is used for indicating the subnet planning of the hybrid cloud platform, and the hybrid cloud platform is constructed on at least one underlying cloud platform.

The purpose of synchronizing the network planning information and the subnet planning information of the hybrid cloud platform is to enable the network information in the hybrid cloud platform to be consistent with the network information of the hybrid cloud platform stored by the management center platform, enable the subnet information in the hybrid cloud platform to be consistent with the subnet information of the hybrid cloud platform managed by the management center platform, and further enable the networks and subnets corresponding to the underlying cloud platforms constructing the hybrid cloud platform to be consistent with the networks and subnets planned for the management center platform.

In the embodiment of the present invention, the management center platform stores the network planning information and subnet planning information of each pre-planned hybrid cloud platform, as shown in fig. 3, the management center platform stores the network planning information and subnet planning information of each pre-planned hybrid cloud platform 1, hybrid cloud platform 2, and hybrid cloud platform 3, and when the synchronous distribution device in the hybrid cloud platform 1 executes the information configuration method provided in the embodiment of the present invention, step 101 is to make the network information in the hybrid cloud platform 1 consistent with the network information of the hybrid cloud platform 1 managed by the management center platform, and make the subnet information in the hybrid cloud platform 1 consistent with the subnet information of the hybrid cloud platform 1 managed by the management center platform.

And the management center platform can uniformly manage the network planning information and the subnet planning information of each pre-planned hybrid cloud platform, and if a new hybrid cloud platform is added, a user can also acquire the network planning information and the subnet planning information of each existing hybrid cloud platform through the management center platform, so that the probability of repeating the network planning information and the subnet planning information of each existing hybrid cloud platform can be reduced when the network information and the subnet information of the new hybrid cloud platform are planned, and the expansion of the hybrid cloud platform is facilitated.

202: and acquiring network information corresponding to the bottom cloud platform from the network planning information, and acquiring subnet information corresponding to the bottom cloud platform from the subnet planning information.

203: and judging whether a network is established on the bottom cloud platform according to the network information corresponding to the bottom cloud platform to obtain a first judgment result.

Optionally, the feasible manner of determining whether the underlying cloud platform has a network created according to the network information corresponding to the underlying cloud platform is as follows: converting network identification information in network information corresponding to the bottom cloud platform into target network identification information which can be identified by the bottom cloud platform; judging whether the description information of the underlying cloud platform stores target network identification information or not; when the description information of the bottom cloud platform does not store the target network identification information, a first judgment result indicating that the bottom cloud platform does not create a network is obtained.

The description information of the bottom cloud platform records various information related to the bottom cloud platform, for example, at least the technical type corresponding to the platform, the platform identification information, the network identification information corresponding to the platform and the subnet identification information corresponding to the platform are stored, if the bottom cloud platform has created a network, the network identification information corresponding to the platform is the identification information of the created network, and if the bottom cloud platform has not created a network, the network identification information corresponding to the platform is empty, so that whether the bottom cloud platform creates a network can be judged by judging whether the description information of the bottom cloud platform stores the target network identification information.

The reason why the network identification information in the network information corresponding to the underlying cloud platform needs to be converted into the target network identification information recognizable by the underlying cloud platform is that: the management center platform manages the network information and the subnet information of all the hybrid cloud platforms in a unified manner, the management center platform can preset the format of each information stored by the management center platform, and the set format enables the bottom cloud platform not to recognize, so that the network identification information in the network information corresponding to the bottom cloud platform needs to be converted into the target network identification information which can be recognized by the bottom cloud platform.

204: and when the first judgment result indicates that the network is not established on the bottom cloud platform, establishing the network for the bottom cloud platform according to the network information corresponding to the bottom cloud platform.

Optionally, a feasible way of creating a network for the underlying cloud platform is as follows: determining a technical type corresponding to the bottom cloud platform according to the network information corresponding to the bottom cloud platform; obtaining a network calling example corresponding to the bottom cloud platform according to the technical type corresponding to the bottom cloud platform; acquiring a network creating method corresponding to a network calling instance corresponding to a bottom cloud platform; and operating a network creation method to create a network for the underlying cloud platform.

Specifically, the processes of determining whether a network is created and creating a network are described in the embodiment of the present invention with reference to fig. 4 to 7: the synchronous distribution device constructs an interface INetManager for a network, standardizes methods of adding (Creat), deleting (Delete), modifying (Update) and searching (Get) to the network, and after constructing the interface INetManager, standardizes network management classes for underlying cloud platforms of different technology types, such as AwsNetManager provided for Amazon cloud, OpenStackNetManager provided for OpenStack-based base cloud, and VMWareNetManager provided for VMWare-based base cloud in FIG. 4.

Wherein the reference Region in fig. 4 identifies a description class of the underlying cloud platform, which records description information of the underlying cloud platform, as shown in fig. 5, the number of the underlying cloud platform (as an alternative to the identification information of the underlying cloud platform), the access address, the technology type, and the like are included, the parameter Network identifies the description class of the Network, it records the network information corresponding to the underlying cloud platform, as shown in fig. 6, including the number of the underlying cloud platform and the network identification information, the Network information recorded from the parameter Network can be obtained as the number of the underlying cloud platform, and then finding a corresponding parameter Region according to the serial number of the bottom cloud platform, judging whether the description information recorded by the parameter Region stores target network identification information, if the target network identification information is not stored, indicating that the bottom cloud platform does not create a network, and acquiring the technical type corresponding to the bottom cloud platform from the parameter Region.

After the technology type corresponding to the underlying cloud platform is obtained, a network call instance corresponding to the underlying cloud platform can be obtained from the configuration file related to the network shown in fig. 7. If the technology Type corresponding to the underlying cloud platform is "Openstack", a network call instance app.impl.openstack.openstack network manager corresponding to Openstack network manager is obtained from the configuration file shown in fig. 7, and then a network creation method Openstack network manager is found according to app.impl.openstack.openstack network manager, and a network can be created for the underlying cloud platform by running Openstack network manager.

205: and judging whether the bottom cloud platform creates a network or not and whether a subnet is created or not according to the subnet information corresponding to the bottom cloud platform, and obtaining a second judgment result.

Optionally, the feasible manner of determining whether the bottom cloud platform creates a network and whether a subnet is created according to the subnet information corresponding to the bottom cloud platform is as follows: respectively converting network identification information and subnet identification information in subnet information corresponding to the bottom cloud platform into target network identification information and target subnet identification information which can be identified by the bottom platform; and when the fact that the description information of the bottom cloud platform stores identifiable target network identification information but does not store identifiable target subnet identification information is judged, indicating that the bottom platform does not create a subnet.

The reason why the subnet identification information in the subnet information corresponding to the underlying cloud platform needs to be converted into the subnet identification information recognizable by the underlying cloud platform is that: the management center platform can preset a format of subnet identification information stored by the management center platform, and the format set by the management center platform makes the bottom cloud platform unrecognizable, so that the subnet identification information corresponding to the bottom cloud platform needs to be converted into subnet identification information recognizable by the bottom cloud platform.

206: and when the second judgment result indicates that the bottom cloud platform creates a network but does not create a subnet, creating a subnet for the bottom cloud platform according to the subnet information corresponding to the bottom cloud platform.

Optionally, a feasible way of creating a subnet for the underlying cloud platform is as follows: determining a technical type corresponding to the bottom cloud platform according to the subnet information corresponding to the bottom cloud platform; obtaining a subnet calling example corresponding to the bottom cloud platform according to the technical type corresponding to the bottom cloud platform; acquiring a subnet creating method corresponding to a subnet calling instance corresponding to a bottom cloud platform; and operating a subnet creating method to create a subnet for the underlying cloud platform.

Specifically, the processes of determining whether a subnet is created and creating a subnet are described in the embodiment of the present invention with reference to fig. 8 to 10: the synchronous distribution device constructs an interface ISubNetManager for the subnet, standardizes a method for adding (Creat), deleting (Delete), modifying (Update) and searching (Get) to the subnet, and standardizes a subnet management class for underlying cloud platforms of different technical types after constructing the interface ISubNetManager, such as providing AwsSubNemanmanager for Amazon cloud, providing OpenStack SubNemanmanager for OpenStack-based foundation cloud, and providing VMWare SubNemanmanager for VMWare-based foundation cloud in FIG. 8.

In fig. 8, the parameter SubNet identifies the description class of the SubNet, and records SubNet information corresponding to the underlying cloud platform, as shown in fig. 9, the description class includes the number of the underlying cloud platform, network identification information, and SubNet identification information, so that the number of the underlying cloud platform can be obtained from the SubNet information recorded in the parameter SubNet, and then a corresponding parameter Region is found according to the number of the underlying cloud platform, and it is determined whether the description information recorded in the parameter Region stores the target network identification information and the target SubNet identification information, if the description information stores the target network identification information but does not store the target SubNet identification information, it is determined that the underlying cloud platform does not create a SubNet, and at this time, the technical type corresponding to the underlying cloud platform is obtained from the parameter Region.

After the technology type corresponding to the underlying cloud platform is obtained, a network call instance corresponding to the underlying cloud platform can be obtained from the configuration file related to the subnet shown in fig. 10. If the technology Type corresponding to the underlying cloud platform is "Openstack", a subnet call instance app.im.openstack.openstack.openstack subnetworkmanager corresponding to Openstack subnetworkmanager is acquired from a configuration file related to the subnet shown in fig. 10, and then a subnet creation method Openstack subnetworkmanager creates a subnet for the underlying cloud platform by finding the subnet according to app.im.openstack.openstack subnetworkmanager, and then the subnet creation method Openstack is executed.

The following describes a process of creating a network and a subnet for an underlying cloud platform by taking an example that a hybrid cloud platform is built on n underlying cloud platforms (region1, … …, region), where fig. 11 illustrates the process of creating a network for an underlying cloud platform, which may include the following steps:

1101: traversing all the bottom cloud platforms (region1, region2, … …, region), the region is the ith bottom cloud platform.

1102: judging that the region traversal is finished, if so, finishing the process; if not, step 1103 is performed.

1103: and network identification information (vlan1, vlan2, … … and vlan) corresponding to the region is taken from the synchronized network planning information, and vlan i is the ith network identification information.

1104: traverse (vlan1, vlan2, … …, vlan).

1105: and judging that the vlan traversal is finished, if so, finishing the flow, and if not, executing step 1106.

1106: taking vlan i.

1107: and converting the vlan i into target network identification information which can be recognized by the regioni.

1108: judging whether the target network identification information exists in the regional information, if so, marking that the vlan is issued, namely, the regional information establishes a network; if not, step 1109 is performed.

1109: a network is created for the regioni.

1110: and judging whether the creation is successful, if so, returning to the step 1105, and if not, sending a creation failure mail archive, wherein the creation failure mail carries failed vlan i so as to indicate that the network is not successfully created for the regioni.

Fig. 12 illustrates a process for the underlying cloud platform to create a subnet, which may include the following steps:

1201: traversing all the bottom cloud platforms (region1, region2, … …, region), the region is the ith bottom cloud platform.

1202: judging that the region traversal is finished, if so, finishing the process; if not, step 1203 is performed.

1203: and acquiring subnet identification information (sunbet1, sunbet2, … … and sunbet) corresponding to the region from the synchronized subnet planning information, wherein sunbet i is the ith subnet identification information.

1204: traversal (sunbet1, sunbet2, … …, sunbet).

1205: and judging that the sunbet traversal is ended, if so, ending the process, and if not, executing the step 1206.

1206: taking sunbeti.

1207: and taking the vlan i corresponding to sunbet.

1208: and converting the vlan i into target network identification information which can be recognized by the regioni.

1209: and judging whether the target network identification information exists in the regional information, if so, executing step 1210, and if not, sending a creation failure mail archive, wherein the creation failure mail carries failed vlan i to indicate that the network is not successfully created for the regional information.

1210: and converting the sunbet into target subnet identification information which can be identified by the regioni.

1211: judging whether the target subnet identification information exists in the regioni description information, if so, marking that sunbeti is issued, namely that the regioni establishes a subnet; if not, step 1212 is performed.

1212: a subnet is created for the regioni.

1213: and judging whether the creation is successful, if so, returning to the step 1205, and if not, sending a creation failure mail archive, wherein the creation failure mail carries failed sunbeti so as to indicate that the subnet is not successfully created for the regioni.

Based on the technical scheme, the information configuration method provided by the embodiment of the invention can acquire the network information corresponding to the bottom cloud platform from the network planning information after the network planning information and the subnet planning information of the hybrid cloud platform are synchronized, and when the fact that the bottom cloud platform does not establish the network is judged according to the network information, the network is established for the bottom cloud platform. And subnet information corresponding to the bottom cloud platform can be acquired from the subnet planning information, and when the fact that the bottom cloud platform creates a network but does not create a subnet is judged according to the subnet information, the subnet is created for the bottom cloud platform, so that after the network planning information and the subnet planning information of the hybrid cloud platform are planned in advance, the bottom cloud platform without the network and without the subnet can be accurately determined, the network and the subnet are automatically created for the bottom cloud platform, and the network and the subnet are automatically and accurately created for the bottom cloud platform.

In the embodiment of the present invention, a feasible manner of synchronizing the network planning information and the subnet planning information of the hybrid cloud platform is shown in fig. 13, and may include the following steps:

1301: and acquiring all the network planning information and all the subnet planning information stored by the management center platform.

Optionally, the manner of obtaining all the network planning information and all the subnet planning information may be: the management center platform can actively push all the network planning information and all the subnet planning information to each mixed cloud platform, although the management center platform can immediately push all the network planning information and all the subnet planning information to each mixed cloud platform after the network planning information and the subnet planning information are updated, in this way, the management center platform needs to be changed to push all the network planning information and all the subnet planning information messages after the change is made according to the number of the managed mixed cloud platforms, and if a new mixed cloud platform is added, the management center platform needs to add a new address of the mixed cloud platform into the pushed messages, so that the new mixed cloud platform can obtain all the network planning information and all the subnet planning information managed by the management center platform.

Optionally, the manner of obtaining all the network planning information and all the subnet planning information may be: all the network planning information and all the subnet planning information are pulled from the management center platform regularly, so that the management center platform cannot be changed due to the change of the number of the managed hybrid cloud platforms, but the timeliness of information acquisition is reduced by the method.

1302: and screening out the network information and the subnet information corresponding to each bottom cloud platform from all the network planning information and all the subnet planning information. Specifically, the network information and the subnet information corresponding to each bottom cloud platform are screened out through the mapping relation between the bottom cloud platform and the network and the mapping relation between the bottom cloud platform and the subnet.

1303: and comparing the screened network information with the network information stored in the local database of the hybrid cloud platform to obtain the network information only stored in the local database and the network information not stored in the local database.

1304: and synchronizing the network planning information of the hybrid cloud platform according to the network information only stored in the local database and the network information not stored in the local database. Optionally deleting the network information only stored in the local database, and deleting the network corresponding to the network information only stored in the local database; adding the network information which is not stored into a local database to synchronize the network planning information of the hybrid cloud platform, so that the network information in the hybrid cloud platform is consistent with the network information of the hybrid cloud platform managed by the management center platform.

1305: and comparing the screened subnet information with subnet information stored in a local database of the hybrid cloud platform to obtain subnet information only stored in the local database and subnet information not stored in the local database.

1306: and synchronizing the subnet planning information of the hybrid cloud platform according to the subnet information only stored in the local database and the subnet information not stored in the local database. Optionally, deleting the subnet information only stored in the local database, and deleting the subnet corresponding to the subnet information only stored in the local database; adding the subnet information which is not stored into a local database to synchronize subnet planning information of the hybrid cloud platform, so that the subnet information in the hybrid cloud platform is consistent with the subnet information of the hybrid cloud platform managed by the management center platform.

According to the technical scheme, the subnet information and the network information which are only stored in the local database are deleted, and the subnet information and the network information which are not stored in the local database are added into the local database, so that the network information and the subnet information in the local database are consistent with the network information and the subnet information of the corresponding hybrid cloud platform managed by the management center platform. When the subnet information and the network information which are only stored in the local database are deleted, the network corresponding to the subnet information which is only stored in the local database and the subnet corresponding to the subnet information which is only stored in the local database are deleted together, so that the network architecture of each bottom layer cloud platform for constructing the hybrid cloud platform is consistent with the network architecture planned for the hybrid cloud platform on the management center platform, and the accuracy of the network architecture is improved.

In the following, the information configuring apparatus provided in the embodiment of the present invention is introduced, and the information configuring apparatus described below may be regarded as a functional unit architecture that is required to be set by the synchronous distribution device to implement the information configuring method provided in the embodiment of the present invention.

Fig. 14 is a schematic structural diagram of an information configuring apparatus according to an embodiment of the present invention, which may include: a synchronization unit 11, an acquisition unit 12, a first judgment unit 13, a first creation unit 14, a second judgment unit 15, and a second creation unit 16.

The synchronization unit 11 is configured to synchronize network planning information and subnet planning information of the hybrid cloud platform, where the network planning information is used to indicate network planning of the hybrid cloud platform, the subnet planning information is used to indicate subnet planning of the hybrid cloud platform, and the hybrid cloud platform is constructed on at least one underlying cloud platform.

The purpose of synchronizing the network planning information and the subnet planning information of the hybrid cloud platform is to enable the network information in the hybrid cloud platform to be consistent with the network information of the hybrid cloud platform stored by the management center platform, enable the subnet information in the hybrid cloud platform to be consistent with the subnet information of the hybrid cloud platform managed by the management center platform, and further enable the networks and subnets corresponding to the underlying cloud platforms constructing the hybrid cloud platform to be consistent with the networks and subnets planned for the management center platform.

The obtaining unit 12 is configured to obtain network information corresponding to the underlying cloud platform from the network planning information, and obtain subnet information corresponding to the underlying cloud platform from the subnet planning information.

The first determining unit 13 is configured to determine whether a network is created on the underlying cloud platform according to the network information corresponding to the underlying cloud platform, so as to obtain a first determination result. Optionally, the manner for the first determining unit 13 to determine whether a network is created is as follows: converting network identification information in the network information corresponding to the bottom cloud platform into target network identification information which can be identified by the bottom cloud platform; judging whether the description information of the underlying cloud platform stores target network identification information or not; when the description information of the bottom cloud platform does not store the target network identification information, a first judgment result indicating that the bottom cloud platform does not create a network is obtained.

The description information of the bottom cloud platform records various information related to the bottom cloud platform, for example, at least the technical type corresponding to the platform, the platform identification information, the network identification information corresponding to the platform and the subnet identification information corresponding to the platform are stored, if the bottom cloud platform has created a network, the network identification information corresponding to the platform is the identification information of the created network, and if the bottom cloud platform has not created a network, the network identification information corresponding to the platform is empty, so that whether the bottom cloud platform creates a network can be judged by judging whether the description information of the bottom cloud platform stores the target network identification information.

The reason why the network identification information in the network information corresponding to the underlying cloud platform needs to be converted into the target network identification information recognizable by the underlying cloud platform is that: the management center platform manages the network information and the subnet information of all the hybrid cloud platforms in a unified manner, the management center platform can preset the format of each information stored by the management center platform, and the set format enables the bottom cloud platform not to recognize, so that the network identification information in the network information corresponding to the bottom cloud platform needs to be converted into the target network identification information which can be recognized by the bottom cloud platform.

The first creating unit 14 is configured to create a network for the underlying cloud platform according to the network information corresponding to the underlying cloud platform when the first determination result indicates that the underlying cloud platform does not create the network. Optionally, a feasible way for the first creating unit 14 to create the network for the underlying cloud platform is: determining a technical type corresponding to the bottom cloud platform according to the network information corresponding to the bottom cloud platform; obtaining a network calling example corresponding to the bottom cloud platform according to the technical type corresponding to the bottom cloud platform; acquiring a network creating method corresponding to a network calling instance corresponding to a bottom cloud platform; the network creating method is operated to create the network for the underlying cloud platform, and the specific process refers to the relevant description in the method embodiment, which is not described again in this embodiment of the present invention.

The second judging unit 15 is configured to judge whether the underlying cloud platform creates a network and whether a subnet is created according to the subnet information corresponding to the underlying cloud platform, so as to obtain a second judgment result. Optionally, the feasible manner for the second determining unit 15 to determine whether a network is created and whether a subnet is created is as follows: respectively converting network identification information and subnet identification information in subnet information corresponding to the bottom cloud platform into target network identification information and target subnet identification information which can be identified by the bottom platform; and when the fact that the description information of the bottom cloud platform stores identifiable target network identification information but does not store identifiable target subnet identification information is judged, indicating that the bottom platform does not create a subnet.

And a second creating unit 16, configured to create a subnet for the bottom cloud platform according to subnet information corresponding to the bottom cloud platform when the second determination result indicates that the bottom cloud platform has created a network but has not created a subnet. Optionally, a feasible way for the second creating unit 16 to create the subnet for the underlying cloud platform is as follows: determining a technical type corresponding to the bottom cloud platform according to the subnet information corresponding to the bottom cloud platform; obtaining a subnet calling example corresponding to the bottom cloud platform according to the technical type corresponding to the bottom cloud platform; acquiring a subnet creating method corresponding to a subnet calling instance corresponding to a bottom cloud platform; the subnet creating method is operated to create the subnet for the underlying cloud platform, and the specific process refers to the relevant description in the method embodiment, which is not described again in this embodiment of the present invention.

Based on the technical scheme, the information configuration device provided by the embodiment of the invention can acquire the network information corresponding to the bottom cloud platform from the network planning information after synchronizing the network planning information and the subnet planning information of the hybrid cloud platform, and creates a network for the bottom cloud platform when judging that the bottom cloud platform does not create the network according to the network information. And subnet information corresponding to the bottom cloud platform can be acquired from the subnet planning information, and when the fact that the bottom cloud platform creates a network but does not create a subnet is judged according to the subnet information, the subnet is created for the bottom cloud platform, so that after the network planning information and the subnet planning information of the hybrid cloud platform are planned in advance, the bottom cloud platform without the network and without the subnet can be accurately determined, the network and the subnet are automatically created for the bottom cloud platform, and the network and the subnet are automatically and accurately created for the bottom cloud platform.

Fig. 15 is a schematic structural diagram of a synchronization unit in an information configuration apparatus according to an embodiment of the present invention, where the synchronization unit may include: an acquisition subunit 111, a screening subunit 112, a first comparison subunit 113, a first synchronization subunit 114, a second comparison subunit 115, and a second synchronization subunit 116.

And the obtaining subunit 111 is configured to obtain all the network planning information and all the subnet planning information stored in the management center platform. Optionally, a feasible way of acquiring all the network planning information and all the subnet planning information is: the management center platform actively pushes all network planning information and all subnet planning information to each hybrid cloud platform; or all the network planning information and all the subnet planning information are pulled from the management center platform periodically.

And a screening subunit 112, configured to screen out, from all the network planning information and all the subnet planning information, network information and subnet information corresponding to each underlying cloud platform. Specifically, the network information and the subnet information corresponding to each bottom cloud platform are screened out through the mapping relation between the bottom cloud platform and the network and the mapping relation between the bottom cloud platform and the subnet.

The first comparing subunit 113 is configured to compare the screened network information with the network information stored in the local database, so as to obtain the network information only stored in the local database and the network information not stored in the local database.

A first synchronization subunit 114, configured to synchronize the network planning information of the hybrid cloud platform according to the network information only stored in the local database and the network information not stored in the local database. Optionally, the method for synchronizing the network planning information of the hybrid cloud platform is as follows: deleting the network information only stored in the local database, and deleting the network corresponding to the network information only stored in the local database; adding the network information which is not stored into a local database to synchronize the network planning information of the hybrid cloud platform, so that the network information in the hybrid cloud platform is consistent with the network information of the hybrid cloud platform managed by the management center platform.

And a second comparing subunit 115, configured to compare the screened subnet information with subnet information stored in the local database, so as to obtain subnet information only stored in the local database and subnet information not stored in the local database.

And a second synchronization subunit 116, configured to synchronize subnet planning information of the hybrid cloud platform according to the subnet information only stored in the local database and subnet information not stored in the local database. Optionally, the method for synchronizing the subnet planning information of the hybrid cloud platform is as follows: deleting the subnet information only stored in the local database, and deleting the subnet corresponding to the subnet information only stored in the local database; adding the subnet information which is not stored into a local database to synchronize subnet planning information of the hybrid cloud platform, so that the subnet information in the hybrid cloud platform is consistent with the subnet information of the hybrid cloud platform managed by the management center platform.

According to the technical scheme, the subnet information and the network information which are only stored in the local database are deleted, and the subnet information and the network information which are not stored in the local database are added into the local database, so that the network information and the subnet information in the local database are consistent with the network information and the subnet information of the corresponding hybrid cloud platform managed by the management center platform. When the subnet information and the network information which are only stored in the local database are deleted, the network corresponding to the subnet information which is only stored in the local database and the subnet corresponding to the subnet information which is only stored in the local database are deleted together, so that the network architecture of each bottom layer cloud platform for constructing the hybrid cloud platform is consistent with the network architecture planned for the hybrid cloud platform on the management center platform, and the accuracy of the network architecture is improved.

In addition, an embodiment of the present invention further provides an information configuration system, including: the information configuration method comprises a management center platform and a hybrid cloud platform, wherein the hybrid cloud platform is built on at least one underlying cloud platform, optional structures of the hybrid cloud platform and the management center platform are shown in fig. 1, and the synchronous distribution equipment can realize the information configuration method provided by the embodiment of the invention through the information processing devices shown in fig. 14 and 15.

It should be noted that: the embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.

Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (18)

1. An information configuration method, characterized in that the method comprises:

synchronizing network planning information and subnet planning information of the hybrid cloud platform, wherein the network planning information is used for indicating the network planning of the hybrid cloud platform, the subnet planning information is used for indicating the subnet planning of the hybrid cloud platform, and the hybrid cloud platform is constructed on at least one underlying cloud platform;

acquiring network information corresponding to the bottom cloud platform from the network planning information, and acquiring subnet information corresponding to the bottom cloud platform from the subnet planning information;

judging whether a network is established on the bottom cloud platform according to the network information corresponding to the bottom cloud platform to obtain a first judgment result;

when the first judgment result indicates that the network is not established on the bottom cloud platform, establishing the network for the bottom cloud platform according to the network information corresponding to the bottom cloud platform;

judging whether a network is established on the bottom cloud platform or not and whether a subnet is established on the bottom cloud platform or not according to the subnet information corresponding to the bottom cloud platform to obtain a second judgment result;

and when the second judgment result indicates that the bottom cloud platform creates a network but does not create a subnet, creating a subnet for the bottom cloud platform according to the subnet information corresponding to the bottom cloud platform.

2. The method according to claim 1, wherein the creating a network for the underlying cloud platform according to the network information corresponding to the underlying cloud platform comprises:

determining a technical type corresponding to the bottom cloud platform according to the network information corresponding to the bottom cloud platform;

obtaining a network calling example corresponding to the bottom cloud platform according to the technical type corresponding to the bottom cloud platform;

acquiring a network creating method corresponding to a network calling instance corresponding to the bottom cloud platform;

and operating the network creation method to create a network for the underlying cloud platform.

3. The method according to claim 1, wherein the determining whether the underlying cloud platform has a network created according to the network information corresponding to the underlying cloud platform to obtain a first determination result includes:

converting network identification information in network information corresponding to a bottom cloud platform into target network identification information which can be identified by the bottom cloud platform;

judging whether the description information of the underlying cloud platform stores the target network identification information or not;

and when the target network identification information is not stored in the description information of the bottom cloud platform, obtaining a first judgment result indicating that the bottom cloud platform does not create a network.

4. The method according to claim 1, wherein the creating a subnet for the underlying cloud platform according to the subnet information corresponding to the underlying cloud platform comprises:

determining a technical type corresponding to the bottom cloud platform according to the subnet information corresponding to the bottom cloud platform;

obtaining a subnet calling example corresponding to the bottom cloud platform according to the technical type corresponding to the bottom cloud platform;

acquiring a subnet creating method corresponding to a subnet calling instance corresponding to the bottom cloud platform;

and operating the subnet creating method to create a subnet for the underlying cloud platform.

5. The method according to claim 1, wherein the determining whether the underlying cloud platform has a network created and whether a subnet created according to the subnet information corresponding to the underlying cloud platform to obtain a second determination result includes:

converting the network identification information in the subnet information corresponding to the bottom cloud platform into target network identification information recognizable by the bottom cloud platform, and converting the subnet identification information in the subnet information corresponding to the bottom cloud platform into target subnet identification information recognizable by the bottom cloud platform;

judging whether the description information of the underlying cloud platform stores target network identification information and whether the description information of the underlying cloud platform stores target subnet identification information;

and when the description information of the bottom cloud platform stores target network identification information but does not store target subnet identification information, obtaining a second judgment result indicating that the bottom cloud platform creates a network but does not create a subnet.

6. The method of claim 1, wherein synchronizing network planning information and subnet planning information for the hybrid cloud platform comprises:

acquiring all network planning information and all subnet planning information stored by a management center platform;

screening out network information and subnet information corresponding to each underlying cloud platform from all the network planning information and all the subnet planning information;

comparing the screened network information with network information stored in a local database to obtain network information only stored in the local database and network information not stored in the local database;

synchronizing the network planning information of the hybrid cloud platform according to the network information only stored in the local database and the network information not stored in the local database;

comparing the screened subnet information with subnet information stored in a local database to obtain subnet information only stored in the local database and subnet information not stored in the local database;

and synchronizing the subnet planning information of the hybrid cloud platform according to the subnet information only stored in the local database and the subnet information not stored in the local database.

7. The method of claim 6, wherein synchronizing the network planning information of the hybrid cloud platform according to the network information stored only in the local database and the network information not stored in the local database comprises:

deleting the network information only stored in the local database, and deleting the network corresponding to the network information only stored in the local database;

and adding the network information which is not stored into the local database so as to synchronize the network planning information of the hybrid cloud platform.

8. The method of claim 6, wherein synchronizing subnet planning information of the hybrid cloud platform according to the subnet information stored only in the local database and subnet information not stored in the local database comprises:

deleting the subnet information only stored in the local database, and deleting the subnet corresponding to the subnet information only stored in the local database;

and adding the subnet information which is not stored into the local database so as to synchronize subnet planning information of the hybrid cloud platform.

9. An information configuring apparatus, the apparatus comprising:

the system comprises a synchronization unit, a first layer cloud platform and a second layer cloud platform, wherein the synchronization unit is used for synchronizing network planning information and subnet planning information of the hybrid cloud platform, the network planning information is used for indicating the network planning of the hybrid cloud platform, the subnet planning information is used for indicating the subnet planning of the hybrid cloud platform, and the hybrid cloud platform is constructed on at least one underlying cloud platform;

the acquiring unit is used for acquiring network information corresponding to the bottom cloud platform from the network planning information and acquiring subnet information corresponding to the bottom cloud platform from the subnet planning information;

the first judging unit is used for judging whether a network is established on the bottom cloud platform according to the network information corresponding to the bottom cloud platform to obtain a first judging result;

the first establishing unit is used for establishing a network for the bottom cloud platform according to the network information corresponding to the bottom cloud platform when the first judging result indicates that the bottom cloud platform is not established with the network;

the second judging unit is used for judging whether a network is established on the bottom cloud platform or not and whether a subnet is established on the bottom cloud platform or not according to the subnet information corresponding to the bottom cloud platform to obtain a second judging result;

and the second creating unit is used for creating a subnet for the bottom cloud platform according to the subnet information corresponding to the bottom cloud platform when the second judgment result indicates that the bottom cloud platform creates a network but does not create a subnet.

10. The apparatus according to claim 9, wherein the first creating unit is configured to create a network for the underlying cloud platform according to the network information corresponding to the underlying cloud platform, and specifically includes:

determining a technical type corresponding to the bottom cloud platform according to the network information corresponding to the bottom cloud platform;

obtaining a network calling example corresponding to the bottom cloud platform according to the technical type corresponding to the bottom cloud platform;

acquiring a network creating device corresponding to a network calling instance corresponding to the bottom cloud platform;

and operating the network creating device to create a network for the underlying cloud platform.

11. The apparatus according to claim 9, wherein the first determining unit is configured to determine whether a network is created in the underlying cloud platform according to network information corresponding to the underlying cloud platform, and obtain a first determination result, and specifically includes:

converting network identification information in network information corresponding to a bottom cloud platform into target network identification information which can be identified by the bottom cloud platform;

judging whether the description information of the underlying cloud platform stores the target network identification information or not;

and when the target network identification information is not stored in the description information of the bottom cloud platform, obtaining a first judgment result indicating that the bottom cloud platform does not create a network.

12. The apparatus according to claim 9, wherein the second creating unit is configured to create a subnet for the underlying cloud platform according to subnet information corresponding to the underlying cloud platform, and specifically includes:

determining a technical type corresponding to the bottom cloud platform according to the subnet information corresponding to the bottom cloud platform;

obtaining a subnet calling example corresponding to the bottom cloud platform according to the technical type corresponding to the bottom cloud platform;

acquiring a subnet creating device corresponding to a subnet calling instance corresponding to the bottom cloud platform;

and operating the subnet creating device to create a subnet for the bottom cloud platform.

13. The apparatus according to claim 9, wherein the second determining unit is configured to determine whether the underlying cloud platform has a network created and whether a subnet created according to the subnet information corresponding to the underlying cloud platform, and obtain a second determination result, and specifically includes:

converting the network identification information in the subnet information corresponding to the bottom cloud platform into target network identification information recognizable by the bottom cloud platform, and converting the subnet identification information in the subnet information corresponding to the bottom cloud platform into target subnet identification information recognizable by the bottom cloud platform;

judging whether the description information of the underlying cloud platform stores target network identification information and whether the description information of the underlying cloud platform stores target subnet identification information;

and when the description information of the bottom cloud platform stores target network identification information but does not store target subnet identification information, obtaining a second judgment result indicating that the bottom cloud platform creates a network but does not create a subnet.

14. The apparatus of claim 9, wherein the synchronization unit comprises:

the acquisition subunit is used for acquiring all the network planning information and all the subnet planning information stored by the management center platform;

the screening subunit is used for screening out the network information and the subnet information corresponding to each underlying cloud platform from all the network planning information and all the subnet planning information;

the first comparison subunit is used for comparing the screened network information with the network information stored in a local database to obtain the network information only stored in the local database and the network information not stored in the local database;

the first synchronization subunit is configured to synchronize the network planning information of the hybrid cloud platform according to the network information only stored in the local database and the network information not stored in the local database;

the second comparison subunit is used for comparing the screened subnet information with subnet information stored in a local database to obtain subnet information only stored in the local database and subnet information not stored in the local database;

and the second synchronization subunit is configured to synchronize the subnet planning information of the hybrid cloud platform according to the subnet information only stored in the local database and the subnet information not stored in the local database.

15. The apparatus according to claim 14, wherein the first synchronization subunit is configured to synchronize the network planning information of the hybrid cloud platform according to the network information only stored in the local database and the network information not stored in the local database, and specifically includes:

deleting the network information only stored in the local database, and deleting the network corresponding to the network information only stored in the local database;

and adding the network information which is not stored into the local database so as to synchronize the network planning information of the hybrid cloud platform.

16. The apparatus according to claim 14, wherein the second synchronizing subunit is configured to synchronize subnet planning information of the hybrid cloud platform according to the subnet information stored only in the local database and the subnet information not stored in the local database, and specifically includes:

deleting the subnet information only stored in the local database, and deleting the subnet corresponding to the subnet information only stored in the local database;

and adding the subnet information which is not stored into the local database so as to synchronize subnet planning information of the hybrid cloud platform.

17. An information provisioning system, comprising: the system comprises a management center platform and a hybrid cloud platform, wherein the hybrid cloud platform is built on at least one underlying cloud platform; the hybrid cloud platform comprises the information configuration device of any one of the preceding claims 9 to 16;

the management center platform comprises center equipment and a database, wherein the database is used for storing network planning information and subnet planning information of the hybrid cloud platform;

and the central equipment is used for uniformly managing the network planning information and the subnet planning information of the hybrid cloud platform.

18. A computer-readable storage medium, in which a computer-executable program is stored, which, when loaded and executed by a processor, implements the information configuring method of any one of claims 1 to 8.

Images