A policy-aware switching layer for data centers

Joseph, Denny; Tavakoli, Arsalan; Stoica, Ion

doi:10.1145/1402958.1402966

Cited by 129 publications

(76 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Furthermore, multi-path routing [6] [8] [12] [13] has been exploited for load balancing in data center networks. Other complementary research for data center networking has focused on TCP incast problem [14], traffic-aware virtual machine migration [15], switch design [16] [17] or cost efficiency [2] [3], etc.…”

Section: Related Workmentioning

confidence: 99%

Network Element Scheduling for Achieving Energy-Aware Data Center Networks

Fang

Liang

Sun

et al. 2014

INT J COMPUT COMMUN

View full text Add to dashboard Cite

The goal of data center network is to interconnect a massive number of servers so as to provide reliable and scalable computing and storage infrastructure for cloud-based Internet services and data-intensive scientific applications. Recent studies reveal that the network elements consume 10∼20% of the overall power in a data center, which has introduced a challenge to reducing network energy cost without adversely affecting network performance. Considering unique features of traffic patterns and network topologies in data centers, this paper proposes a novel Network Element Scheduling Scheme (NESS) to reduce data center energy consumption from the networking perspective. The core idea is to turn on only a minimal subset of network elements to satisfy routing requirements, and put to sleep or shut down the rest unneeded ones for energy saving. In NESS, the logical network architecture formed by the active elements not only achieves the basic purpose for server interconnections in data centers, but also can support multi-path routing between pairs of hot servers for load balancing. Simulation experiments are performed in representative data center network topologies, and the results demonstrate the effectiveness of NESS in energy conserving on network elements in data centers.

show abstract

Section: Related Workmentioning

confidence: 99%

Network Element Scheduling for Achieving Energy-Aware Data Center Networks

Fang

Liang

Sun

et al. 2014

INT J COMPUT COMMUN

View full text Add to dashboard Cite

show abstract

“…Middlebox policies can be supported in an ad-hoc fashion in both networks. There are two ways we can do this-Tunneling [15] packets from one middlebox to another or by installing policy rules on all switches [16]. The latter approach is not scalable, since it consumes a lot of space on switch TCAMs, which are limited in size.…”

Section: Architecturementioning

confidence: 99%

“…Separate Policy from Reachability: We borrow this principle from [16]. Ad-hoc practices for ensuring middlebox traversal, like removing links to create choke points, are hard to configure and maintain.…”

Section: Middlebox Supportmentioning

confidence: 99%

See 1 more Smart Citation

ProActive routing in scalable data centers with PARIS

Arora

Benson

Rexford

2014

Proceedings of the 2014 ACM SIGCOMM Workshop on Distributed Cloud Computing

View full text Add to dashboard Cite

Modern data centers must meet many challenges and expectations: (a) They must scale to a large number of servers, while offering high bisection bandwidth and flexible placement of virtual machines.(b) They must allow tenants to specify network policies and realize them by forwarding traffic through the desired sequences of middleboxes. (c) They must allow tenants to bring their own IP address space to the cloud to ease transition of enterprise applications and middlebox configuration.The traditional approach of connecting layer-two pods through a layer-three core constrains VM placement. More recent "flat" designs are more flexible but have scalability limitations due to flooding/broadcasting or querying directories of VM locations. Rather than reactively learn VM locations, our PARIS architecture has a controller that pre-positions IP forwarding entries in the switches. Switches within a pod have complete information about the VMs beneath them, while each core switch maintains complete forwarding state for part of the address space. PARIS offers network designers the flexibility to choose a topology that meets their latency and bandwidth requirements.PARIS also allows tenants to bring their own IP address space and utilizes lightweight virtualization using Linux namespaces to offer middlebox service in a manner that truly reflects the pay-as-you go model of cloud computing. It utilizes MPLS label forwarding and aggregation in the network core and uses source routing at the network edge to realize middlebox policies specified by tenants. Finally, we evaluate our PARIS prototype built using Openflow-compliant switches and NOX controller.Using PARIS we can build a data center network that can support up to 500K VMs.iii

show abstract

“…Dilip et al [24] proposed PLayer and pswitch: a policyaware switching layer architecture consisting of interconnected policy-aware switches. In accordance with policies specified by administrators, pswitches explicitly forward different types of traffic through different sequence middleboxes (e.g., Firewalls and Load Balancers).…”

Section: Middle-boxes/appliancesmentioning

confidence: 99%