On the placement of controllers in software-defined networks

Abstract The software-defined network (SDN) approach assumes a logically centralized control plane, which is physically decoupled from the data plane. Since this approach simplifies network management and speeds up network innovations, these benefits have led not just to production-intent prototypes, but real SDN deployments. For wide-area SDN deployments, multiple controllers are often required, and the placement of these controllers influences every aspect of an SDN. Since optimizing every metric is generally an non-deterministic polynomial (NP)-hard problem, it is of great importance to find an efficient controller placement algorithm. In this paper, we develop several placement algorithms to make informed placement decisions, which can be used to maximize the reliability of SDN, since network failures could easily cause disconnections between the control and forwarding planes. These algorithms are evaluated using real topologies. Simulation results show that the controller placement strategies are crucial to SDN performance, and a greedy algorithm provides placement solutions that are close to optimal.

[1]  Rob Sherwood,et al.  The controller placement problem , 2012, HotSDN@SIGCOMM.

[2]  Nick Feamster,et al.  Design and implementation of a routing control platform , 2005, NSDI.

[3]  Martín Casado,et al.  Onix: A Distributed Control Platform for Large-scale Production Networks , 2010, OSDI.

[4]  Hong Yan,et al.  A clean slate 4D approach to network control and management , 2005, CCRV.

[5]  Yashar Ganjali,et al.  HyperFlow: A Distributed Control Plane for OpenFlow , 2010, INM/WREN.

[6]  Victor O. K. Li,et al.  Modeling and analysis of systems with multimode components and dependent failures , 1989 .

[7]  Rob Sherwood,et al.  On Controller Performance in Software-Defined Networks , 2012, Hot-ICE.

[8]  Marco Canini,et al.  A NICE Way to Test OpenFlow Applications , 2012, NSDI.

[9]  Kamesh Munagala,et al.  Local Search Heuristics for k-Median and Facility Location Problems , 2004, SIAM J. Comput..

[10]  Nick McKeown,et al.  OpenFlow: enabling innovation in campus networks , 2008, CCRV.

[11]  David Walker,et al.  Frenetic: a network programming language , 2011, ICFP.

[12]  Martín Casado,et al.  NOX: towards an operating system for networks , 2008, CCRV.

[13]  Athina Markopoulou,et al.  Characterization of Failures in an IP Backbone Network , 2004, INFOCOM.

[14]  Chen-Nee Chuah,et al.  Characterization of Failures in an Operational IP Backbone Network , 2008, IEEE/ACM Transactions on Networking.

[15]  Alan L. Cox,et al.  Maestro: A System for Scalable OpenFlow Control , 2010 .

[16]  Ratul Mahajan,et al.  Measuring ISP topologies with rocketfuel , 2002, TNET.

[17]  Scott Shenker,et al.  Ethane: taking control of the enterprise , 2007, SIGCOMM.