TY - GEN
T1 - RAPTOR
T2 - 35th IEEE Conference on Computer Communications Workshops, INFOCOM WKSHPS 2016
AU - Rivera, Sergio
AU - Fei, Zongming
AU - Griffioen, James
PY - 2016/9/6
Y1 - 2016/9/6
N2 - Many Software-Defined Networking (SDN) controllers support a 'northbound interface' by which applications can interact with the SDN controller and (indirectly) control the underlying SDN network. The absence of a standard for the northbound interface of these controllers makes it difficult for application developers to create interoperable/portable code (i.e., code that works with any SDN controller). Developers are forced to re-write almost all of their code every time they want to support a new controller. This tedious and time consuming process is typically a start-over software development cycle that involves learning new APIs, data models, and controller-specific conventions. In this paper, we present RAPTOR, a REST-based API translaTOR service for SDN networks that allows users to develop their network control software independent of any particular SDN controller. RAPTOR exposes its own REST-based API functions and data models to user applications and translates application requests into controller-specific northbound interface calls. To demonstrate the viability of RAPTOR, we implemented and deployed RAPTOR in GENI and used it in conjunction with different types of controllers. We also developed GENI Desktop modules that interacted with RAPTOR to install, list, delete and monitor end-to-end flows regardless of the controller used for controlling the underlying switches.
AB - Many Software-Defined Networking (SDN) controllers support a 'northbound interface' by which applications can interact with the SDN controller and (indirectly) control the underlying SDN network. The absence of a standard for the northbound interface of these controllers makes it difficult for application developers to create interoperable/portable code (i.e., code that works with any SDN controller). Developers are forced to re-write almost all of their code every time they want to support a new controller. This tedious and time consuming process is typically a start-over software development cycle that involves learning new APIs, data models, and controller-specific conventions. In this paper, we present RAPTOR, a REST-based API translaTOR service for SDN networks that allows users to develop their network control software independent of any particular SDN controller. RAPTOR exposes its own REST-based API functions and data models to user applications and translates application requests into controller-specific northbound interface calls. To demonstrate the viability of RAPTOR, we implemented and deployed RAPTOR in GENI and used it in conjunction with different types of controllers. We also developed GENI Desktop modules that interacted with RAPTOR to install, list, delete and monitor end-to-end flows regardless of the controller used for controlling the underlying switches.
UR - http://www.scopus.com/inward/record.url?scp=84988826710&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=84988826710&partnerID=8YFLogxK
U2 - 10.1109/INFCOMW.2016.7562096
DO - 10.1109/INFCOMW.2016.7562096
M3 - Conference contribution
AN - SCOPUS:84988826710
T3 - Proceedings - IEEE INFOCOM
SP - 328
EP - 333
BT - 2016 IEEE Conference on Computer Communications Workshops, INFOCOM WKSHPS 2016
Y2 - 10 April 2016 through 14 April 2016
ER -