Side-Effects Causing Hidden Conflicts in Software-Defined Networks

Software Defined Networks

In previous chapters we have seen why SDN is necessary and what preceded the actual advent of SDN in the research and industrial communities. In this chapter we provide an overview of how SDN actually works, including discussion of the basic components of a Software Defined Networking system, their roles, and how they interact with one another. In the first part of this chapter we focus on the ...

Virtualization in Software - Defined Networks

H osted cloud computing has signif icantly lowered the barrier for creating new networked services. Likewise, experimental facilities such as the Global Environment for Network Innovations (GENI; www. geni.net) let researchers perform largescale experiments on a “slice” of shared infrastructure. By letting tenants share physical resources, virtualization is a key technology in these infrastruct...

Control in Software - Defined Networks

Composing Software Defined Networks

Managing a network requires support for multiple concurrent tasks, from routing and traffic monitoring, to access control and server load balancing. Software-Defined Networking (SDN) allows applications to realize these tasks directly, by installing packet-processing rules on switches. However, today’s SDN platforms provide limited support for creating modular applications. This paper introduce...

Software-Defined Networks as Databases

In software-defined networks (SDN), the separation of the control and data-plane moves the concurrency control from the data-plane to a separate, now logically centralized controller program. As a result, despite its intention to simplify programming, the separation forces the programmer to deal with a spectrum of concurrent events (e.g. execution of controller programs, in-flight packets), a t...