CN106533751B - SDN controller cluster merging method and device - Google Patents
SDN controller cluster merging method and device Download PDFInfo
- Publication number
- CN106533751B CN106533751B CN201610972287.3A CN201610972287A CN106533751B CN 106533751 B CN106533751 B CN 106533751B CN 201610972287 A CN201610972287 A CN 201610972287A CN 106533751 B CN106533751 B CN 106533751B
- Authority
- CN
- China
- Prior art keywords
- cluster
- persistent data
- sdn controller
- controller
- sub
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/508—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement
- H04L41/5096—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement wherein the managed service relates to distributed or central networked applications
Abstract
The embodiment of the invention provides a method and a device for merging SDN controller clusters, which are applied to a main host controller in an SDN controller sub-cluster, and the method comprises the following steps: when the SDN controller sub-cluster where the SDN controller sub-cluster is located is detected to be merged with other SDN controller sub-clusters of the cluster, obtaining the updating time of locally stored persistent data, and obtaining the updating time of persistent data of main controllers used by other SDN controller sub-clusters; judging whether the update time of the locally stored persistent data is later than that of the master controller of the other SDN controller sub-cluster main; and if not, degrading the SDN controller sub-cluster where the self is located so as to join other SDN controller sub-clusters with latest persistent data updating time. The embodiment of the invention can ensure that the data stored in the main master controller of the SDN controller cluster after combination is the latest data.
Description
Technical Field
The invention relates to the technical field of communication, in particular to a method and a device for merging SDN controller clusters.
Background
Multiple controllers in an SDN network may form a controller cluster. In an SDN controller cluster, each controller is configured with its role in the SDN controller cluster. Specifically, the role of the controller in the SDN cluster is two: a master controller (leader controller) and a general controller (member controller). In the SDN network shown in fig. 1(a), the SDN controller cluster includes a master controller 1, a master controller 2, a general controller 1, and a general controller 2.
After the configuration of the SDN controller cluster is completed, an election mechanism is started, a main controller is elected and generated in a plurality of main controllers through the election mechanism, and the rest main controllers are standby main controllers. The main master controller is responsible for making centralized decision and management on data and services generated by other controllers in the SDN controller cluster so as to achieve the purpose of keeping data consistent and synchronous in the range of the SDN controller cluster. As shown in fig. 1(a), in an SDN controller cluster, a main controller 1 is an active main controller, and a main controller 2 is a standby main controller.
In an SDN controller cluster, a communication interface between a host controller and a management platform (e.g., a cloud management platform) is a northbound interface, and a communication interface between the host controller and a network device (e.g., an access device) is a southbound interface. As shown in fig. 1(a), the communication interface between the host controller 1 and the cloud management platform is a northbound interface, and the communication interfaces between the host controller 1, the host controller 2, and the access device are southbound interfaces. Through the northbound interface, the main controller 1 may receive persistent data, such as configuration data, user management information, and the like, issued by the cloud management platform. Through the southbound interface, the main controller 1 and the main controller 2 can interactively operate data with each exchange device through the access device. In addition, the main controller 1 may also synchronize persistent data issued by the cloud management platform to the main controller 2 through the access device.
In some cases, due to network failure or other reasons, the SDN controller cluster may be split, that is, one SDN controller cluster is split into more than two SDN controller sub-clusters. As shown in fig. 1(b), after the controller cluster is split, the master controller 1 and the general controller 1 form one controller sub-cluster, and the master controller 2 and the general controller 2 form another controller sub-cluster. In this case, when the cloud management platform issues the persistent data, the persistent data can only be issued to the main controller 1, and due to a network failure, the main controller 1 cannot synchronize the persistent data to the main controller 2.
After the network failure is recovered, merging the SDN controller sub-clusters into one SDN controller cluster, and selecting a primary main controller of the merged SDN controller cluster according to a policy, for example, the number of controllers in each SDN controller sub-cluster may be determined; or selecting the master main controller in one of the SDN controller sub-clusters as the master main controller of the merged cluster according to the priority of the master main controller in each SDN controller sub-cluster, where when the SDN controller sub-clusters shown in fig. 1(b) are merged, when the priority of the master main controller 2 is higher than the priority of the master main controller 1, the master main controller 2 may be used as the master main controller of the merged controller cluster.
However, after the controller cluster is split, the persistent data issued by the cloud management platform cannot be received in the main controller 2, so that the latest persistent data is lost when the main controller 2 is used as the main controller of the merged controller cluster, and the data stored in the main controller of the merged controller cluster is not the latest persistent data.
Disclosure of Invention
The embodiment of the invention aims to provide a method and a device for merging SDN controller clusters, so as to ensure that data stored in a main host controller of the SDN controller clusters after merging is the latest data. The specific technical scheme is as follows:
in a first aspect, an embodiment of the present invention provides a method for merging SDN controller clusters, where the method is applied to a master host controller in an SDN controller sub-cluster, and the method includes:
when the SDN controller sub-cluster where the SDN controller sub-cluster is located is detected to be merged with other SDN controller sub-clusters of the cluster, obtaining the updating time of locally stored persistent data, and obtaining the updating time of persistent data of main controllers used by other SDN controller sub-clusters;
judging whether the update time of the locally stored persistent data is later than that of the master controller of the other SDN controller sub-cluster main;
and if not, degrading the SDN controller sub-cluster where the self is located so as to join other SDN controller sub-clusters with latest persistent data updating time.
In a second aspect, an embodiment of the present invention provides an SDN controller cluster merging device, which is applied to an active host controller in an SDN controller sub-cluster, and the device includes:
the acquiring module is used for acquiring the update time of the locally stored persistent data and acquiring the update time of the persistent data of the master controller for the sub-cluster of other SDN controllers when the fact that the sub-cluster of the SDN controller where the acquiring module is located is merged with the sub-clusters of other SDN controllers of the cluster is detected;
the judging module is used for judging whether the updating time of the locally stored persistent data is later than that of the persistent data of the other SDN controller sub-cluster main controllers;
and the merging module is used for degrading the SDN controller sub-cluster where the merging module is positioned when the judgment result of the judging module is negative so as to add other SDN controller sub-clusters with latest persistent data updating time.
The embodiment of the invention provides a method and a device for merging SDN controller clusters, wherein a master main controller in each SDN controller sub-cluster can locally store corresponding persistent data updating time, and when the master main controller in the SDN controller sub-cluster detects that the SDN controller sub-cluster in which the master main controller is located is merged with other SDN controller sub-clusters of the cluster, the master main controller can determine whether degradation merging is carried out or not according to the locally stored persistent data updating time and the obtained persistent data updating time of the master main controllers of the other SDN controller sub-clusters. When the update time of the self persistent data is latest, the persistent data stored by the self persistent data can be shown to be the latest data, and at the moment, the main controller does not do any operation; when the update time of the persistent data of the master host controller is not the latest, it indicates that persistent data later than the update time of the master host controller still exists, and in this case, the master host controller may downgrade the SDN controller sub-cluster where the master host controller is located to add the SDN controller sub-cluster where the master host controller with the latest update time of the persistent data is located, thereby ensuring that the master host controller of the merged SDN cluster is the master host controller that stores the latest persistent data. Moreover, since the non-persistent data can be restored according to the persistent data, the embodiment of the invention can ensure that the data stored in the main host controller of the SDN cluster after merging is the latest data.
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 some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1(a) is a schematic diagram of an SDN network structure including an SDN controller cluster;
fig. 1(b) is a schematic structural diagram of the SDN network after the SDN controller cluster shown in fig. 1(a) is split;
fig. 2 is a flowchart of a SDN controller cluster merging method according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of an SDN controller cluster merging device according to an embodiment of the present invention;
fig. 4 is another schematic structural diagram of an SDN controller cluster merging device according to an embodiment of the present invention.
Detailed Description
In order to ensure that the data stored in the primary main controller of the SDN controller cluster after merging is the latest data, embodiments of the present invention provide a method and an apparatus for merging SDN controller clusters.
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.
It should be noted that the embodiments and features of the embodiments may be combined with each other without conflict. The present invention will be described in detail below with reference to the embodiments with reference to the attached drawings.
According to the embodiment provided by the application, data in controllers of an SDN controller cluster are divided into two types for different treatment, namely persistent data and non-persistent data. The persistent data refers to data that needs to be stored in a persistent storage device, for example, a database or a persistent file, by the SDN controller, and is not lost after power failure restart, and is usually issued by a management platform, such as a cloud management platform. For example, various configuration data, user management information for SDN controllers, and the like. Non-persistent data refers to data that does not need to be stored by the SDN controller into a persistent storage device. Such data may be obtained by performing dynamic operation calculations based on persistent data and network real-time status, such as operation data, flow table information, and the like.
When the split SDN controller sub-clusters are merged into one SDN controller cluster, as long as persistent data stored in a main controller of the merged SDN controller cluster is ensured to be the latest data, the main controller can recover the latest non-persistent data according to the latest persistent data, so that all data stored in the main controller are ensured to be the latest data.
In the embodiment of the present invention, when the controller cluster is split into the controller sub-clusters, the active main controller of each controller sub-cluster updates the locally stored persistent data as the active main controller persistent data update time of the controller sub-cluster. For example, when the master controller is upgraded from the standby master controller to the active master controller in the split controller sub-cluster, the persistent data update time of the master controller is the initial persistent time of the controller sub-cluster in which the master controller is located.
When persistent data of a controller sub-cluster is updated, for example, when the persistent data is added, modified, deleted, etc., the master controller of the controller sub-cluster may record the time of updating, that is, the latest time of updating the persistent data. An embodiment of the present invention provides a merging method process for an SDN controller cluster, which is applied to a primary host controller in an SDN controller sub-cluster, and as shown in fig. 2, the merging method process may include the following steps:
s201, when detecting that the SDN controller sub-cluster where the SDN controller sub-cluster is located is merged with other SDN controller sub-clusters of the cluster, obtaining the updating time of locally stored persistent data, and obtaining the updating time of the persistent data of the main controller used by the other SDN controller sub-clusters.
In the embodiment of the present invention, the active host controller may detect whether the SDN controller sub-cluster in which the active host controller is located is merged with other SDN controller sub-clusters of the cluster. The reason that the plurality of SDN controller sub-clusters are split in the SDN controller cluster is that due to network faults and the like, when the network faults are repaired, the main master controller of each SDN controller sub-cluster sends interaction messages. Therefore, in the embodiment of the present invention, the master host controller in the SDN controller sub-cluster may detect whether the SDN controller sub-cluster in which the master host controller is located is merged with other SDN controller sub-clusters of the present cluster by determining whether an interaction packet sent by the master host controller for the other SDN controller sub-clusters of the same controller cluster is received.
It should be noted that, the active host controller may also adopt any existing method to detect whether the SDN controller sub-cluster where the active host controller is located is merged with other SDN controller sub-clusters of the cluster, and the embodiment of the present invention does not limit the process.
When the master host controller detects that the SDN controller sub-cluster where the master host controller is located is merged with other SDN controller sub-clusters of the cluster, the master host controller can acquire the locally stored persistent data updating time and the persistent data updating time of the master host controllers of the other SDN controller sub-clusters, and determine how to merge the SDN clusters according to the self persistent data updating time and the persistent data updating time of the master host controllers of the other SDN controller sub-clusters.
For example, the active host controller may obtain the persistent data update time through a corresponding path according to a predetermined path for storing the persistent data update time.
In one implementation, when the master host controller obtains the persistent data update time of the master controllers for the other SDN controller sub-cluster masters, the master host controller may send a persistent data update time request message to the master controllers for the other SDN controller sub-cluster masters; and receiving response messages sent by other SDN controller sub-cluster main controllers, and acquiring the persistent data updating time carried in each response message and corresponding to each SDN controller sub-cluster main controller.
When the master controller sends the persistent data update time request message to the master controllers of the other SDN controller sub-clusters, the master controller can send the persistent data update time request message to the master controllers of the other SDN controller sub-clusters in a unicast mode according to the address information of the master controllers in the other SDN controller sub-clusters.
In another implementation manner, when the master host controller detects that the SDN controller sub-cluster in which the master host controller is located is merged with other SDN controller sub-clusters of the local cluster, the master host controller may actively send a notification message carrying self persistent data update time to the other SDN controller sub-cluster masters of the local cluster; or, when sending the interaction message to the other SDN controller sub-cluster master controller, the device may carry the persistent data update time of the device in the interaction message and send the persistent data update time to the other SDN controller sub-cluster master controller.
Similarly, the active main controller may also receive notification messages or interaction messages sent by other SDN controller subset main controllers, and obtain persistent data update time corresponding to each SDN controller subset main controller carried in the received messages.
S202, judging whether the updating time of the locally stored persistent data is later than that of the persistent data of the other SDN controller sub-cluster main controller; if not, step S203 is executed, and if yes, no operation is executed.
After obtaining the locally stored persistent data update time and the persistent data update times of the other SDN controller subset master controllers, the master controller may determine whether the locally stored persistent data update times are all later than the persistent data update times of the other SDN controller subset master controllers.
That is to say, the active host controller may determine whether the locally stored persistent data is the latest data in all the active host controllers, so as to determine how to merge the SDN controller clusters according to the determination result.
And S203, degrading the SDN controller sub-cluster where the self is located so as to join other SDN controller sub-clusters with latest persistent data updating time.
When the master host controller judges that the update time of the locally stored persistent data is not later than that of the master host controllers of the other SDN controller sub-cluster, the locally stored persistent data is not the latest data and cannot be used as the master host controller of the combined SDN controller sub-cluster. In this case, the active host controller may downgrade the SDN controller sub-cluster where the active host controller is located, so as to add the SDN controller sub-cluster where the active host controller with the latest persistent data update time is located.
Specifically, the active host controller may restart its own physical machine, or may restart its own SDN controller subset process. In the process of restarting the physical machine or the SDN controller sub-cluster process by the main master controller, the standby master controller and the common controller in the SDN controller sub-cluster where the main master controller is located are disconnected from the main master controller. And the standby main controller and the common controller are connected with the main controller which is not restarted again. Because only the master controller with the latest persistent data update time is not restarted, the standby master controller and the common controller in the SDN controller sub-cluster in which the master controller is located can be ensured to be added to the SDN controller sub-cluster in which the master controller with the latest persistent data update time is located.
In the embodiment of the present invention, in addition to the above method, any existing method may be adopted in the process of degrading the SDN controller sub-cluster in which the active host controller is located, and details of the process are not described in the embodiment of the present invention.
The method provided by the embodiment of the invention can be applied to the main master controller in any SDN controller sub-cluster. That is to say, the active host controller in each SDN controller sub-cluster executes the above steps, and further determines whether to downgrade the SDN controller sub-cluster in which it is located.
When a plurality of SDN controller sub-clusters appear in the SDN controller cluster, for a master controller in each SDN controller sub-cluster, as long as the persistent data updating time is not the latest, the master controller can degrade the SDN controller sub-cluster where the master controller is located. That is, only the active host controller with the latest persistent data update time will not degrade the SDN controller sub-cluster in which the active host controller is located. Therefore, other SDN controller sub-clusters may join the SDN controller sub-cluster where the active host controller with the latest persistent update time is located, thereby completing merging of the SDN controller clusters. And the merged primary master controller of the SDN controller cluster is the primary master controller with the latest update time of the persistent data.
After the merged SDN controller cluster is obtained, the primary host controller of the SDN controller cluster may synchronize the persistent data to each general controller in the SDN controller cluster according to the persistent data stored locally, so that the primary host controller and each general controller recover local non-persistent data according to the persistent data.
The embodiment of the invention provides a method for merging SDN controller clusters, wherein a master main controller in each SDN controller sub-cluster can locally store corresponding persistent data updating time, and when the master main controller in the SDN controller sub-cluster detects that the SDN controller sub-cluster in which the master main controller is located is merged with other SDN controller sub-clusters in the cluster, the master main controller can determine whether degradation merging is performed or not according to the locally stored persistent data updating time and the obtained persistent data updating time of the master main controllers of the other SDN controller sub-clusters. When the update time of the self persistent data is latest, the persistent data stored by the self persistent data can be shown to be the latest data, and at the moment, the main controller does not do any operation; when the update time of the persistent data of the master host controller is not the latest, it indicates that persistent data later than the update time of the master host controller still exists, and in this case, the master host controller may downgrade the SDN controller sub-cluster where the master host controller is located to add the SDN controller sub-cluster where the master host controller with the latest update time of the persistent data is located, thereby ensuring that the master host controller of the merged SDN cluster is the master host controller that stores the latest persistent data. Moreover, since the non-persistent data can be restored according to the persistent data, the embodiment of the invention can ensure that the data stored in the main host controller of the SDN cluster after merging is the latest data.
As an implementation manner of the embodiment of the present invention, when the active main controller locally stores the persistent data update time, it may store the persistent data update time in a log corresponding to the locally stored persistent data. Correspondingly, when the master host controller obtains the update time of the locally stored persistent data, the master host controller can obtain the update time of the persistent data recorded in the log according to the log corresponding to the locally stored persistent data.
As another implementation manner of the embodiment of the present invention, when the persistent data locally stored by the main host controller is updated, for example, when the persistent data is added, modified, deleted, and the like, the main host controller may update the update time of the locally stored persistent data, so as to ensure the accuracy of the update time of the locally stored persistent data.
Corresponding to the above method embodiment, the embodiment of the present invention also provides a corresponding device embodiment.
Fig. 3 is a device for merging SDN controller clusters provided in an embodiment of the present invention, and is applied to an active host controller in an SDN controller sub-cluster, where the device includes:
an obtaining module 310, configured to obtain, when it is detected that the SDN controller sub-cluster where the SDN controller sub-cluster is located is merged with other SDN controller sub-clusters of the cluster, persistent data update time stored locally, and obtain persistent data update time of a master controller for other SDN controller sub-clusters;
a determining module 320, configured to determine whether the locally stored persistent data update time is later than the persistent data update time of the other SDN controller subset master controller;
a merging module 330, configured to, when the determination result of the determining module is negative, downgrade the SDN controller sub-cluster where the merging module is located, so as to join in another SDN controller sub-cluster with the latest persistent data update time.
The embodiment of the invention provides an SDN controller cluster merging device, wherein a main master controller in each SDN controller sub-cluster can locally store corresponding persistent data updating time, and when the main master controller in the SDN controller sub-cluster detects that the SDN controller sub-cluster in which the main master controller is located is merged with other SDN controller sub-clusters of the cluster, the main master controller can determine whether degradation merging is performed or not according to the locally stored persistent data updating time and the obtained persistent data updating time of the main master controllers of the other SDN controller sub-clusters. When the update time of the self persistent data is latest, the persistent data stored by the self persistent data can be shown to be the latest data, and at the moment, the main controller does not do any operation; when the update time of the persistent data of the master host controller is not the latest, it indicates that persistent data later than the update time of the master host controller still exists, and in this case, the master host controller may downgrade the SDN controller sub-cluster where the master host controller is located to add the SDN controller sub-cluster where the master host controller with the latest update time of the persistent data is located, thereby ensuring that the master host controller of the merged SDN cluster is the master host controller that stores the latest persistent data. Moreover, since the non-persistent data can be restored according to the persistent data, the embodiment of the invention can ensure that the data stored in the main host controller of the SDN cluster after merging is the latest data.
As an implementation manner of the embodiment of the present invention, as shown in fig. 4, the obtaining module 310 includes:
a sending submodule 311, configured to send a persistent data update time request packet to a master controller for a subset of other SDN controllers;
the obtaining sub-module 312 is configured to receive response messages sent by other SDN controller sub-cluster masters, and obtain persistent data update time carried in each response message and corresponding to each SDN controller sub-cluster master.
As another implementation manner of the embodiment of the present invention, the obtaining module 310 is specifically configured to receive messages sent by other SDN controller subset master controllers, and obtain persistent data update time carried in each message and corresponding to each SDN controller subset master controller.
As another implementation manner of the embodiment of the present invention, the obtaining module 310 is specifically configured to obtain, according to a log corresponding to persistent data stored locally, update time of the persistent data recorded in the log.
As another implementation manner of the embodiment of the present invention, as shown in fig. 4, the apparatus further includes:
an update module 340, configured to update the locally saved persistent data update time when the locally saved persistent data is updated.
For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (10)
1. A method for merging SDN controller clusters is applied to a main host controller in an SDN controller sub-cluster, and comprises the following steps:
when the SDN controller sub-cluster where the SDN controller sub-cluster is located is detected to be merged with other SDN controller sub-clusters of the cluster, obtaining the updating time of locally stored persistent data, and obtaining the updating time of persistent data of main controllers used by other SDN controller sub-clusters;
judging whether the update time of the locally stored persistent data is later than that of the master controller of the other SDN controller sub-cluster main;
and if not, degrading the SDN controller sub-cluster where the self is located so as to join other SDN controller sub-clusters with latest persistent data updating time.
2. The method of claim 1, wherein obtaining persistent data update times for other SDN controller sub-cluster masters with a master controller comprises:
sending a persistent data updating time request message to other SDN controller subset main controllers;
and receiving response messages sent by other SDN controller sub-cluster main controllers, and acquiring the persistent data updating time carried in each response message and corresponding to each SDN controller sub-cluster main controller.
3. The method of claim 1, wherein obtaining persistent data update times for other SDN controller sub-cluster masters with a master controller comprises:
and receiving messages sent by other SDN controller sub-cluster main controllers, and acquiring the persistent data updating time carried in each message and corresponding to each SDN controller sub-cluster main controller.
4. The method of any of claims 1-3, wherein obtaining the locally saved persisted data update time comprises:
and according to the log corresponding to the locally stored persistent data, acquiring the update time of the persistent data recorded in the log.
5. The method according to any one of claims 1-3, further comprising:
when the locally-saved persistent data is updated, the locally-saved persistent data update time is updated.
6. An SDN controller cluster merging device applied to an active host controller in an SDN controller sub-cluster, the device comprising:
the acquiring module is used for acquiring the update time of the locally stored persistent data and acquiring the update time of the persistent data of the master controller for the sub-cluster of other SDN controllers when the fact that the sub-cluster of the SDN controller where the acquiring module is located is merged with the sub-clusters of other SDN controllers of the cluster is detected;
the judging module is used for judging whether the updating time of the locally stored persistent data is later than that of the persistent data of the other SDN controller sub-cluster main controllers;
and the merging module is used for degrading the SDN controller sub-cluster where the merging module is positioned when the judgment result of the judging module is negative so as to add other SDN controller sub-clusters with latest persistent data updating time.
7. The apparatus of claim 6, wherein the obtaining module comprises:
the sending submodule is used for sending a request message of the persistent data updating time to the main controller for the other SDN controller sub-cluster owners;
and the obtaining submodule is used for receiving response messages sent by other SDN controller sub-cluster main controllers and obtaining the persistent data updating time carried in each response message and corresponding to each SDN controller sub-cluster main controller.
8. The apparatus of claim 6, wherein the obtaining module is specifically configured to receive a packet sent by a master controller for a subset of other SDN controllers, and obtain persistent data update time carried in each packet and corresponding to each master controller for the subset of SDN controllers.
9. The apparatus according to any one of claims 6 to 8, wherein the obtaining module is specifically configured to obtain, according to a log corresponding to persistent data stored locally, update time of the persistent data recorded in the log.
10. The apparatus according to any one of claims 6-8, further comprising:
and the updating module is used for updating the updating time of the locally-stored persistent data when the locally-stored persistent data is updated.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610972287.3A CN106533751B (en) | 2016-11-07 | 2016-11-07 | SDN controller cluster merging method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610972287.3A CN106533751B (en) | 2016-11-07 | 2016-11-07 | SDN controller cluster merging method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106533751A CN106533751A (en) | 2017-03-22 |
| CN106533751B true CN106533751B (en) | 2020-12-25 |
Family
ID=58349492
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610972287.3A Active CN106533751B (en) | 2016-11-07 | 2016-11-07 | SDN controller cluster merging method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106533751B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110086581A (en) * | 2019-05-30 | 2019-08-02 | 深圳市中航比特通讯技术有限公司 | The synchronous method and apparatus of a main prepare more data under a kind of network integration scene |
| CN112272105B (en) * | 2020-09-16 | 2023-04-18 | 浪潮思科网络科技有限公司 | SDN controller cluster member control method, system and medium |
| CN114124650A (en) * | 2021-12-08 | 2022-03-01 | 中国电子科技集团公司第三十四研究所 | Master-slave deployment method of SPTN (shortest Path bridging) network controller |
| CN116455911B (en) * | 2023-03-28 | 2024-03-22 | 安超云软件有限公司 | Heterogeneous cluster intercommunication method |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104168209A (en) * | 2014-08-28 | 2014-11-26 | 杭州华三通信技术有限公司 | Multi-access SDN message forwarding method and controller |
| CN104270260A (en) * | 2014-09-19 | 2015-01-07 | 杭州华三通信技术有限公司 | Method and device for elastic expansion of scale of SDN controller cluster |
| CN104601380A (en) * | 2015-01-30 | 2015-05-06 | 杭州华三通信技术有限公司 | Software-defined network controller and host computer information recovery method thereof |
| CN104639615A (en) * | 2015-01-07 | 2015-05-20 | 杭州华三通信技术有限公司 | Data processing method and data processing device in controller cluster |
| CN104811325A (en) * | 2014-01-24 | 2015-07-29 | 华为技术有限公司 | Cluster node controller monitoring method, related device and controller |
| WO2015167597A1 (en) * | 2014-04-30 | 2015-11-05 | Hewlett-Packard Development Company, L.P. | Data plane to forward traffic based on communications from a software defined networking (sdn) controller during control plane failure |
| TW201618503A (en) * | 2014-11-13 | 2016-05-16 | 財團法人工業技術研究院 | OpenFlow switch and method for packet exchanging thereof, SDN controller and data flow control method thereof |
| CN105812269A (en) * | 2014-12-31 | 2016-07-27 | 华为技术有限公司 | Method of creating port group in SDN, SDN controllers, and network system |
-
2016
- 2016-11-07 CN CN201610972287.3A patent/CN106533751B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104811325A (en) * | 2014-01-24 | 2015-07-29 | 华为技术有限公司 | Cluster node controller monitoring method, related device and controller |
| WO2015167597A1 (en) * | 2014-04-30 | 2015-11-05 | Hewlett-Packard Development Company, L.P. | Data plane to forward traffic based on communications from a software defined networking (sdn) controller during control plane failure |
| CN104168209A (en) * | 2014-08-28 | 2014-11-26 | 杭州华三通信技术有限公司 | Multi-access SDN message forwarding method and controller |
| CN104270260A (en) * | 2014-09-19 | 2015-01-07 | 杭州华三通信技术有限公司 | Method and device for elastic expansion of scale of SDN controller cluster |
| TW201618503A (en) * | 2014-11-13 | 2016-05-16 | 財團法人工業技術研究院 | OpenFlow switch and method for packet exchanging thereof, SDN controller and data flow control method thereof |
| CN105812269A (en) * | 2014-12-31 | 2016-07-27 | 华为技术有限公司 | Method of creating port group in SDN, SDN controllers, and network system |
| CN104639615A (en) * | 2015-01-07 | 2015-05-20 | 杭州华三通信技术有限公司 | Data processing method and data processing device in controller cluster |
| CN104601380A (en) * | 2015-01-30 | 2015-05-06 | 杭州华三通信技术有限公司 | Software-defined network controller and host computer information recovery method thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106533751A (en) | 2017-03-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106533751B (en) | SDN controller cluster merging method and device | |
| CN109729111B (en) | Method, apparatus and computer program product for managing distributed systems | |
| KR100956638B1 (en) | Large Scale Cluster Monitoring System, And Automatic Building And Restoration Method Thereof | |
| WO2017140131A1 (en) | Data writing and reading method and apparatus, and cloud storage system | |
| CN105933407B (en) | method and system for realizing high availability of Redis cluster | |
| CN104679611B (en) | Data resource clone method and device | |
| US8874960B1 (en) | Preferred master election | |
| GB2606092A (en) | Systems and methods for enabling a highly available managed failover service | |
| WO2020248507A1 (en) | Container cloud-based system resource monitoring method and related device | |
| CN106062717A (en) | Distributed storage replication system and method | |
| CN112463448B (en) | Distributed cluster database synchronization method, device, equipment and storage medium | |
| US20170308446A1 (en) | System and method for disaster recovery of cloud applications | |
| CN109446169B (en) | Double-control disk array shared file system | |
| US20210320977A1 (en) | Method and apparatus for implementing data consistency, server, and terminal | |
| CN102394914A (en) | Cluster brain-split processing method and device | |
| TWI677797B (en) | Management method, system and equipment of master and backup database | |
| WO2023082800A1 (en) | Main node selection method, distributed database and storage medium | |
| WO2017028375A1 (en) | Version upgrading method and system | |
| CN112328421B (en) | System fault processing method and device, computer equipment and storage medium | |
| CN107819556B (en) | Service state switching method and device | |
| CN106230622B (en) | Cluster implementation method and device | |
| CN108600284B (en) | Ceph-based virtual machine high-availability implementation method and system | |
| CN107508700B (en) | Disaster recovery method, device, equipment and storage medium | |
| CN106487611B (en) | Method and device for detecting SDN cluster split | |
| CN109189854B (en) | Method and node equipment for providing continuous service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| CB02 | Change of applicant information |
Address after: 310052 Binjiang District Changhe Road, Zhejiang, China, No. 466, No. Applicant after: Xinhua three Technology Co., Ltd. Address before: 310053 Hangzhou science and Technology Industrial Park, high tech Industrial Development Zone, Zhejiang Province, No. six and road, No. 310 Applicant before: Huasan Communication Technology Co., Ltd. |
|
| CB02 | Change of applicant information | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |