Results 1 - 10
of
39
Software-Defined Networking: A Comprehensive Survey
, 2014
"... The Internet has led to the creation of a digital society, where (almost) everything is connected and is accessible from anywhere. However, despite their widespread adoption, traditional IP networks are complex and very hard to manage. It is both difficult to configure the network according to pre- ..."
Abstract
-
Cited by 20 (3 self)
- Add to MetaCart
The Internet has led to the creation of a digital society, where (almost) everything is connected and is accessible from anywhere. However, despite their widespread adoption, traditional IP networks are complex and very hard to manage. It is both difficult to configure the network according to pre-defined policies, and to reconfigure it to respond to faults, load and changes. To make matters even more difficult, current networks are also vertically integrated: the control and data planes are bundled together. Software-Defined Networking (SDN) is an emerging paradigm that promises to change this state of affairs, by breaking vertical integration, separating the network’s control logic from the underlying routers and switches, promoting (logical) centralization of network control, and introducing the ability to program the network. The separation of concerns introduced between the definition of network policies, their
A Survey of Software-Defined Networking: Past, Present, and Future of Programmable Networks
, 2013
"... The idea of programmable networks has recently re-gained considerable momentum due to the emergence of the Software-Defined Networking (SDN) paradigm. SDN, often referred to as a “radical new idea in networking”, promises to dramatically simplify network management and enable in-novation through net ..."
Abstract
-
Cited by 16 (2 self)
- Add to MetaCart
The idea of programmable networks has recently re-gained considerable momentum due to the emergence of the Software-Defined Networking (SDN) paradigm. SDN, often referred to as a “radical new idea in networking”, promises to dramatically simplify network management and enable in-novation through network programmability. This paper surveys the state-of-the-art in programmable networks with an emphasis on SDN. We provide a historic perspective of programmable networks from early ideas to recent developments. Then we present the SDN architecture and the OpenFlow standard in particular, discuss current alternatives for implementation and testing of SDN-based protocols and services, examine current and future SDN applications, and explore promising research directions based on the SDN paradigm.
Network Innovation using OpenFlow: A Survey
- IEEE COMMUNICATIONS SURVEYS & TUTORIALS, ACCEPTED FOR PUBLICATION
, 2013
"... OpenFlow is currently the most commonly deployed ..."
Software Transactional Networking: Concurrent and Consistent Policy Composition
, 2013
"... It seems natural to imagine that SDN policy specification and control is distributed, and this paper focuses on the resulting concurrency issues. Indeed, conflicts among concurrent policy updates may result in serious inconsistencies on the data plane, even when each update is installed with perpack ..."
Abstract
-
Cited by 9 (4 self)
- Add to MetaCart
(Show Context)
It seems natural to imagine that SDN policy specification and control is distributed, and this paper focuses on the resulting concurrency issues. Indeed, conflicts among concurrent policy updates may result in serious inconsistencies on the data plane, even when each update is installed with perpacket consistent update semantics. This paper introduces the problem of consistent composition of concurrent policy updates. Intuitively, consistent concurrent policy composition must appear as though there is no concurrency neither between any policy updates, nor between a policy update and in-flight packets on the data plane. We propose an elegant policy composition abstraction based on a transactional interface with all-or-nothing semantics: a policy update is either committed, in which case the policy is guaranteed to compose consistently over the entire network and the update is installed in its entirety, or aborted, in which case, no packet is affected by it. Consequently, the control application logic is relieved from the cumbersome and potentially error-prone synchronization and locking tasks, and control applications are kept lightweight. In this paper, we also sketch a simple implementation of the transactional synchronization: our approach is based on fine-grained locking on network components and avoids complex state machine replication.
PolicyCop: An Autonomic QoS Policy Enforcement Framework for Software Defined Networks
"... Abstract—Network management is becoming increas-ingly challenging with the relentless growth in network size, traffic volume, and the diversity in QoS requirements. Traditionally, the concept of predefined Service Level Agreements (SLAs) has been utilized to establish QoS parameters. However, state- ..."
Abstract
-
Cited by 7 (3 self)
- Add to MetaCart
(Show Context)
Abstract—Network management is becoming increas-ingly challenging with the relentless growth in network size, traffic volume, and the diversity in QoS requirements. Traditionally, the concept of predefined Service Level Agreements (SLAs) has been utilized to establish QoS parameters. However, state-of-the-art technologies in this area are both proprietary and inflexible. To this end, Software Defined Networking (SDN) has the potential to make network management tasks flexible and scalable, and to provide an open platform to encourage innovation. In this paper, we present PolicyCop – an open, flexible, and vendor agnostic QoS policy management framework targeted towards OpenFlow based SDN. PolicyCop pro-vides an interface for specifying QoS-based SLAs and enforces them using the OpenFlow API. It monitors the network and autonomically readjusts network parameters to satisfy customer SLAs. We present experimental re-sults to demonstrate PolicyCop’s effectiveness in ensuring throughput, latency, and reliability guarantees. I.
On the feasibility of a consistent and fault-tolerant data store for SDNs
"... Maintaining a strongly consistent network view in a Software Defined Network has been usually proclaimed as a synonym of low performance. We disagree. To support our view, in this paper we argue that with the use of modern distributed systems techniques it is possible to build a strongly consistent ..."
Abstract
-
Cited by 7 (5 self)
- Add to MetaCart
Maintaining a strongly consistent network view in a Software Defined Network has been usually proclaimed as a synonym of low performance. We disagree. To support our view, in this paper we argue that with the use of modern distributed systems techniques it is possible to build a strongly consistent, fault-tolerant SDN control framework that achieves acceptable performance. The central element of our architecture is a highly-available, strongly consistent data store. We describe a prototype imple-mentation of a distributed controller architecture integrating the Floodlight controller with a data store implemented using a state-of-the-art replication algorithm. We evaluate the feasibility of the proposed design by analyzing the workloads of real SDN applications (a learning switch, a load balancer and a device manager) and showing that the data store is capable of handling them with adequate performance.
Applying operating system principles to sdn controller design
- In Proceedings of the Twelfth ACM Workshop on Hot Topics in Networks
, 2013
"... Rather than creating yet another network controller which provides a framework in a specific (potentially new) pro-gramming language and runs as a monolithic application, in this paper we extend an existing operating system and lever-age its software ecosystem in order to serve as a practical SDN co ..."
Abstract
-
Cited by 7 (0 self)
- Add to MetaCart
(Show Context)
Rather than creating yet another network controller which provides a framework in a specific (potentially new) pro-gramming language and runs as a monolithic application, in this paper we extend an existing operating system and lever-age its software ecosystem in order to serve as a practical SDN controller. This paper introduces yanc, a controller platform for software-defined networks which exposes the network configuration and state as a file system, enabling user and system applications to interact through standard file I/O, and to easily take advantage of the tools available on the host operating system. In yanc, network applications are separate processes, are provided by multiple sources, and may be written in any language. Applications benefit from common and powerful technologies such as the virtual file system (VFS) layer, which we leverage to layer a distributed file system on top of, and Linux namespaces, which we use to isolate applications with different views (e.g., slices). In this paper we present the goals and design of yanc. Our initial prototype is built with the FUSE file system in user space on Linux and has been demonstrated with a simple static flow pusher application. Effectively, we are making Linux the network operating system.
DISCO: Distributed Multi-domain SDN Controllers
"... Abstract—Software-Defined Networking (SDN) is now envi-sioned for Wide Area Networks (WAN) and constrained overlay networks. Such networks require a resilient, scalable and easily extensible SDN control plane. In this paper, we propose DISCO, an extensible DIstributed SDN COntrol plane able to cope ..."
Abstract
-
Cited by 6 (0 self)
- Add to MetaCart
(Show Context)
Abstract—Software-Defined Networking (SDN) is now envi-sioned for Wide Area Networks (WAN) and constrained overlay networks. Such networks require a resilient, scalable and easily extensible SDN control plane. In this paper, we propose DISCO, an extensible DIstributed SDN COntrol plane able to cope with the distributed and heterogeneous nature of modern overlay networks. A DISCO controller manages its own network domain and communicates with other controllers to provide end-to-end network services. This east-west communication is based on a lightweight and highly manageable control channel. We imple-mented DISCO on top of the Floodlight OpenFlow controller and the AMQP protocol and we evaluated it through an inter-domain topology disruption use case. I.
Dynamic Controller Provisioning in Software Defined Networks
"... Abstract—Software Defined Networking (SDN) has emerged as a new paradigm that offers the programmability required to dynamically configure and control a network. A traditional SDN implementation relies on a central controller that runs the control plane. However, in a large-scale WAN deployment, thi ..."
Abstract
-
Cited by 5 (3 self)
- Add to MetaCart
(Show Context)
Abstract—Software Defined Networking (SDN) has emerged as a new paradigm that offers the programmability required to dynamically configure and control a network. A traditional SDN implementation relies on a central controller that runs the control plane. However, in a large-scale WAN deployment, this rudimentary centralized approach has several limitations related to performance and scalability. To address these issues, recent proposals have advocated deploying multiple controllers that work cooperatively to control a network. Nonetheless, this approach drags in an interesting problem, which we call the Dynamic Controller Provisioning Problem (DCPP). DCPP dynamically adapts the number of controllers and their locations with changing network conditions, in order to minimize flow setup time and communication overhead. In this paper, we propose a framework for deploying multiple controllers within an WAN. Our framework dynamically adjusts the number of active controllers and delegates each controller with a subset of Openflow switches according to network dynamics while ensuring minimal flow setup time and communication overhead. To this end, we formulate the optimal controller provisioning problem as an Integer Linear Program (ILP) and propose two heuristics to solve it. Simulation results show that our solution minimizes flow setup time while incurring very low communication overhead. I.
RINA: An Architecture for Policy-Based Dynamic Service Management
"... Management is a vital component for delivering requested network services. The inability of the current Internet architecture to accommodate modern requirements has spurred attempts to provide novel network management solutions. Existing approaches often restrict the range of policies that can be em ..."
Abstract
-
Cited by 5 (5 self)
- Add to MetaCart
(Show Context)
Management is a vital component for delivering requested network services. The inability of the current Internet architecture to accommodate modern requirements has spurred attempts to provide novel network management solutions. Existing approaches often restrict the range of policies that can be employed to adapt to diverse network conditions. They are also tailored either to a specific set of (management) applications, or to the current Internet architecture, inheriting its shortcomings, for example adopting its incomplete (static) addressing architecture or ad-hoc solutions that result in so-called “layer violations.” In this paper, we describe a novel management architecture developed from first principles to enable the specification of various policies. To this end, we identify common underlying mechanisms, based on the unifying principle that any management application consists of processes maintaining and sharing distributed states of information objects for the purpose of delivering a network service. This principle underlies our Recursive InterNetwork Architecture (RINA), where the notion of a “layer ” represents such state sharing among processes and such layers can be repeated over different scopes and stacked to provide more effective wide-area services. We present a management framework that enables application programmers to specify four types of policies for managing a layer, the network, the naming of services, and an application, and use our prototype implementation to demonstrate adaptation to changing communication and load requirements.
