A scheduling method for software-defined network controller cluster

Abstract

The invention relates to a scheduling method of a software-defined network controller cluster, which adopts the scheme of the controller cluster, can distribute the load pressure to each controller node, and avoids the processing performance that is caused by concentrating all the load pressure on a single controller node. low problem. Each controller node in the cluster is configured with a corresponding Hash table. Each controller node is only allowed to modify the identity of the switch it is responsible for taking over and its load factor in the Hash table it owns. Each controller node modifies its When the data in the owned Hash table, need its modified data synchronously in other controller nodes, update the data in the Hash table that owns respectively by other controller nodes correspondingly; The present invention can determine corresponding according to the data in the Hash table The controller node takes over the switch without introducing a third-party manager, and will not cause the entire cluster to be limited by the performance of the third-party manager.

Description

technical field [0001] The invention relates to the field of network technology, in particular to a scheduling method for a software-defined network controller cluster. Background technique [0002] At present, there are roughly two scheduling schemes for software-defined network (Software Defined Network, SDN) controllers. One is a scheduling scheme based on dual-machine hot standby. Its architecture is as follows figure 1 As shown, usually the master controller node is responsible for taking over all the switches, and when the master controller node is down, the standby controller node takes over all the switches; the disadvantage is that the load pressure is concentrated on a single controller node, processing Lower performance. [0003] The other is to use a third-party manager to schedule the controller cluster. Its architecture is as follows: figure 2 As shown in , add a third-party manager besides all controller nodes, responsible for managing and scheduling all co...

AI Technical Summary

Problems solved by technology

[0002] At present, there are roughly two scheduling schemes for software-defined network (Software Defined Network, SDN) controllers. One is a scheduling scheme based on dual-machine hot standby. Its architecture is as follows figure 1 As shown, usually the master controller node is responsible for taking over all the switches, and when the master controller node is down, the standby controller node takes over all the switches; the disadvantage is that the load pressure is concentrated on a single controller node, processing lower performance

[0003] The other is to use a third-party manager to schedule the controller cluster. Its architecture is as follows: figure 2 As shown in , add a third-party manager besides all controller nodes, responsible for managing and scheduling all controller nodes in the cluster; all controller nodes assign switch takeover tasks through this third-party manager; if the controller When a node goes down, the third-party manager will reschedule the switch to take over the task; the disadvantage is that if the third-party manager goes down, it will affect the operation of the overall network system. The program scheduling performance of the third-party manager will make the performance of the third-party manager become the bottleneck of the overall cluster

Images