The beacon openflow controller

By David Erickson. HotSDN '13, 2013

515 citations recorded by the source corpus.

Beacon is a Java-based open source OpenFlow controller created in 2010. It has been widely used for teaching, research, and as the basis of Floodlight. This paper describes the architectural decisions and implementation that achieves three of Beacon's goals: to improve developer productivity, to provide the runtime ability to start and stop existing and new applications, and to be high performance.

Subfields: Artificial Intelligence, Computer Networks and Communications, Information Systems

View Paper: https://www.semanticscholar.org/paper/33c9bc92c2a5ef616618c0d569b71733c62c8603

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Artificial Intelligence

In Computer Networks and Communications

In Information Systems

Citations in the corpus

A Survey of Security in Software Defined Networks (2016, background): “, NOX [11], Beacon [12], Floodlight [13]) were structured around functioning as an OpenFlow [5] driver, various new implementations (e.”
Optimizing the "one big switch" abstraction in software-defined networks (2013, background): “However, many controller platforms [2, 3, 4, 5, 6] force applications to manage the network at the level of individual switches by representing a high-level policy in terms of the rules installed in each switch.”
A Survey on Software-Defined Wireless Sensor Networks: Challenges and Design Requirements (2017, background): “SDN central controllers include Floodlight [138], [174], Ryu [175], Maestro [136], NOX [62], Beacon [137].”
Distributed SDN Control: Survey, Taxonomy, and Challenges (2018, background): “as NOX [51], Beacon [52] and Floodlight [53] in different networking environments.”
The road to SDN: an intellectual history of programmable networks (2014, methodology): “First, an SDN separates the control plane (which decides how to handle the traf.c) from the data plane (which forwards traf.c according to decisions that the control plane A version of this article previously appeared in ACM Queue (http: //queue.acm.org/detail.cfm?id=2560327).”
A Survey of Software-Defined Networking: Past, Present, and Future of Programmable Networks (2014, unknown): “OFRewind [71] allows network events (control and data) to be recorded at different granularities and later replayed to reproduce a speciﬁc scenario, granting the opportunity to localize and troubleshoot the events that caused the network anomaly. ndb [72] implements breakpoints and…”
VeriFlow: verifying network-wide invariants in real time (2012, unknown): “We expect one could similarly integrate VeriFlow with other controllers, such as Floodlight [2], Beacon [1] and Maestro [11], without signiﬁcant trouble.”
On the Capacitated Controller Placement Problem in Software Defined Networks (2014, background): “However, the load of processing PACKET_IN events is generally regarded as the most significant part of the total load [2], [6].”
Security in Software Defined Networks: A Survey (2015, unknown): “Implemented as OpenFlow application for the Beacon controller [97], the system consists of three modules, i.”
DISCO: Distributed multi-domain SDN controllers (2013, methodology): “Parallel open source initiatives such as NOX [9], Bea-con [10], Floodlight [7], Ryu [11] etc. Researchers mainly focused on improving the performance of a speciﬁc controller like Maestro [12] and NOX [13] or demonstrating the improvement offered by OpenFlow against a classic L2 paradigm [14].”
A Survey of Machine Learning Techniques Applied to Software Defined Networking (SDN): Research Issues and Challenges (2019, background): “There are many controller architectures, such as NOX [25], POX [26], Floodlight [27], Ryu [28], OpenDayLight [29] and Beacon [30].”
A Survey and a Layered Taxonomy of Software-Defined Networking (2014, background): “Code bundles in Beacon can be started, stopped, refreshed, and installed at runtime, without interrupting other non-dependent bundles.”
The Road to SDN (2013, methodology): “23, 30, 37, 46, 55, 63, 80 Programmers have used these platforms to create many applications, such as dynamic access control, 16,53 server load balancing, 39,81 network virtualization, 54,67 energy-efficient networking, 42 and seamless virtual-machine migration and user mobility.”