A simple multipath OpenFlow controller using topology‐based algorithm for multipath TCP

Guo

Concurrency and Computation

et al. 2019

Summary Data transmission in current networks is usually associated with strict priority enforcement for the purpose of quality of service (QoS). Under the case that priority flow requests are injected into the network sequentially without the information of future flow request arrivals, it is a challenging to achieve network throughput maximization for on‐line flow requests under the joint constraints of the flow's priority, bandwidth demand, and resource capacity. Software Defined Networking (SDN) can effectively solve the flow scheduling equilibrium problem between the priority of dynamic flow requests and the maximization of network throughput. Therefore, in this paper, we study on‐line flow request admission in SDN, the goal of which is to maximize the network throughput under the constraints of critical network bandwidth resources, flow priority, and bandwidth demands. First, we present the concept of flow routing cost and profit and a model to characterize the cost of using link resources and routing paths. Then, we propose an efficient on‐line priority flow scheduling algorithm (OPFSA) to solve priority flow request scheduling problem and analyze the competitive ratio of OPFSA. Our on‐line algorithm can reach throughput within Ofalse(1normallnormalonormalgnfalse) of the highest possible throughput that can be achieved by an off‐line algorithm, where n is the number of node in the network. Finally, experimental results demonstrate that compared with SHORTEST‐SC, our proposed algorithm can enhance the cumulative bandwidth about 9% and 40% when general network size is 30 and 170 nodes, respectively, and improve the throughput about 25% in Fat‐tree network when pod size is 4.

“…Some works focused on flow splitting routing in the hybrid SDN . Specifically, Xu et al studied a throughput‐maximization routing for incremental deployment of hybrid network.…”

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Priority‐based online flow scheduling for network throughput maximization in software defined networking

Guo

Concurrency and Computation

et al. 2019

2018 IEEE International Symposium on Broadband Multimedia Systems and Broadcasting (BMSB)

“…• The authors of [13] propose a solution to avoid multipath bottlenecks developing SMOC, a simple multipath OpenFlow controller, that uses only topology information of the network to avoid the collisions. The previously mentioned works explore how to deal with the different TCP subflows in the data plane, in order to increase the performance and reliability of the end user flows.…”

Section: Multipath Tcp and Openflowmentioning

confidence: 99%

Towards a Resilient Openflow Channel Through MPTCP

González

Oliva

Bernardos

et al. 2018

Abstract-In the recent years, Software Defined Networking (SDN) has changed the way networks are engineered, making them more flexible, programmable and dynamic. SDN advocates for the centralization of control functionalities in a central node, the so-called controller. This entity has a wide view of the entire network, including the topology, facilitating the management and decreasing the complexity. However, the existence of a single entity running the complete control plane constitutes a single point of failure, thus triggering the need of improving the resiliency and reliability of the controller and the connection between the control and the data plane.This paper presents a solution for the improvement of the resiliency and the reliability on the OpenFlow channel through the use of multipath TCP (MPTCP). The proposed solution is based on the simultaneous use of in-band and out-of-band paths for the OpenFlow control channel, and includes a first experimental evaluation of the performance gains that can be achieved.Index Terms-SDN, OpenFlow, Resiliency, Reliability, MPTCP.A centralized controller is a potential single point of failure and a potential bottleneck. A failure on the controller or a disconnection between the control and data planes may lead to performance degradation and packet loss. OpenFlow uses a TCP connection (secured using SSL/TLS) to control the data plane elements. This connection, the so called OpenFlow channel, may use in-band or out-of-band transport signaling. In-band signaling is characterized by carrying the OpenFlow protocol packets through the same paths as the data transport, and therefore requires the network to be preconfigured to forward the OpenFlow signaling. Out-ofband signaling requires a separate network connecting all data plane elements to the controller, therefore requiring of extra network deployments.There is a need to improve the resiliency and reliability on software defined networks. Some efforts are devoted on the controller side, supporting a control plane distribution, starting with the version 1.2 of the OpenFlow protocol which supports mechanisms to use several simultaneous controllers. This concept was extended by diverse projects to increase the reliability on the control plane increasing the scalability and avoiding the single point of failure of a centralized architecture:• Onix [5] presents a platform for building a control plane on top of it as a distributed system. It provides an API which consists on a data model to abstract the network infrastructure, this API provides control logic, the possibility of read/write the state of the data plane and a notification engine for network state changes.• HyperFlow [6] solution is based on a logically centralized but physically distributed control plane synchronized with a publish/subscription system. All the controllers using HyperFlow have a consistent network-wide view and they run as if they are controlling the whole network.• ElastiCon [7] propose an elastic distributed controller architecture with a control...

Concurrency and Computation

“…In the PRAGMA spirit, there was sufficient interest among members and key individuals to lead this effort that has moved ENT from concept to utilization and testing [32]. At a systems level, the value of the PRAGMA Grid and more recently the PRAGMA ENT is that is provides a testbed for approaches and can be intentionally disrupted to understand how the software and system responds [33] [34].…”

Section: A Trust Envelop For Expeditions To Share Resourcesmentioning

confidence: 99%

A reflection on the origins, evolution, and future of PRAGMA

Arzberger

2017

SUMMARYAll of the papers in this special collection have been shaped by and/or have helped shape PRAGMA. This paper, a reflection on PRAGMA, will provide additional technical, scientific and human context to many of these papers. We hope to illustrate that it is the people who set directions by following their interests or posing questions, who make progress by honoring their commitments, and who build community by establishing open communications and trust. SETTING THE STAGEAs with any research organization, there are factors leading to its origins, there are the critical first steps, the establishments a framework for growth, and the need to evolve, especially when technology and science are evolving rapidly.