OpenFlow-Based Server Load Balancing Gone Wild

By Richard Wang, D. Butnariu, Jennifer Rexford. USENIX conference on Hot topics in management of internet, cloud, and enterprise networks and services, 2011

455 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/05d94e914db5ef72f51adda7306ae97aa502fbdd

How researchers see this paper

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

Citations in the corpus

A roadmap for traffic engineering in SDN-OpenFlow networks (2014, background): “OpenFlow-based load balancer [42] developed at Princeton University, is an efficient load-balancing architecture, which includes the partitioning algorithm for generating wildcard rules that are proactively installed into the switches to direct requests for ‘‘microflows’’ without involving the contr”
Ananta: cloud scale load balancing (2013, background): “Other researchers have also attempted to build load balancers using OpenFlow switches [28], however, these solutions do not yet meet all the requirements, e.g., tenant isolation and scalable source NAT across layer-2 domains.”
The road to SDN: an intellectual history of programmable networks (2014, background): “Second, an SDN consolidates the control plane, so that a single software control program controls multiple dataplane elements.”
How Can Edge Computing Benefit From Software-Defined Networking: A Survey, Use Cases, and Future Directions (2017, methodology): “There are proposals that utilize the functionalities of SDN and OpenFlow to carry out the load balancing procedures among network resources [39], [40], computation resources [41], [42], or both of them [43], [44].”
Software-Defined Network Function Virtualization: A Survey (2015, unknown): “, Openflow [47]–[51]), can be utilized as standardized interfaces in communicating between”
SilkRoad: Making Stateful Layer-4 Load Balancing Fast and Cheap Using Switching ASICs (2017, background): “Load balancing: Beyond SLBs [15, 20, 30, 36] and Duet [22], there are other works [26, 28, 41] which use OpenFlow switches to implement load balancing.”
A NICE Way to Test OpenFlow Applications (2012, unknown): “Previous work created a load-balancer application that uses wildcard rules to divide traffic based on the client IP addresses to achieve a target load distribution [9].”
SIMPLE-fying middlebox policy enforcement using SDN (2013, methodology): “SDN provides the ﬂexibility to implement load balancing algorithms in the network and avoids the need for operators to manually install trafﬁc splitting rules or use custom load balancing solutions [42].”
A Survey and a Layered Taxonomy of Software-Defined Networking (2014, background): “[105] propose a costless and more flexible OpenFlow-based alternative.”
Frenetic: a network programming language (2011, background): “Already, researchers have created a variety of controller applications that introduce new network functionality, like flexible access control [10, 34], Web server load balancing [22, 41], energy-efficient networking [23], and seamless virtual-machine migration [19].”
Optimizing the "one big switch" abstraction in software-defined networks (2013, background): “For example, access-control policies match on the “five tuple” of source and destination IP addresses and port numbers and the protocol [7], whereas a load balancer may match on source and destination IP prefixes [8].”
FireFly (2014, background): ““flow” variables are mapped to prefix-range based forwarding entries [49].”
SoftCell: scalable and flexible cellular core network architecture (2013, background): “These middleboxes could be dedicated appliances, virtual machines running on commodity devices [6], or packet-processing rules installed directly in the switches [7, 8].”
OpenNF (2014, background): “To overcome this issue, we can wait for existing flow s to terminate and only reroute new flows [24, 39].”
DevoFlow: scaling flow management for high-performance networks (2011, background): “…forwarding rules and policy allows for innovative and promising network management solutions such as NOX [26, 45] and other proposals [29, 39, 49], but these solutions may not be realizable on many networks because the ﬂow-based networking platform they are built on— OpenFlow—is not scalable.”