Albert Greenberg
Parantap Lahiri
ABSTRACT
Applications hosted in today's data centers suffer from internal fragmentation of resources, rigidity, and bandwidth constraints imposed by the architecture of the network connecting the data center's servers. Conventional architectures statically map web services to Ethernet VLANs, each constrained in size to a few hundred servers owing to control plane overheads. The IP routers used to span traffic across VLANs and the load balancers used to spray requests within a VLAN across servers are realized via expensive customized hardware and proprietary software. Bisection bandwidth is low, severly constraining distributed computation Further, the conventional architecture concentrates traffic in a few pieces of hardware that must be frequently upgraded and replaced to keep pace with demand - an approach that directly contradicts the prevailing philosophy in the rest of the data center, which is to scale out (adding more cheap components) rather than scale up (adding more power and complexity to a small number of expensive components).
Commodity switching hardware is now becoming available with programmable control interfaces and with very high port speeds at very low port cost, making this the right time to redesign the data center networking infrastructure. In this paper, we describe monsoon, a new network architecture, which scales and commoditizes data center networking monsoon realizes a simple mesh-like architecture using programmable commodity layer-2 switches and servers. In order to scale to 100,000 servers or more,monsoon makes modifications to the control plane (e.g., source routing) and to the data plane (e.g., hot-spot free multipath routing via Valiant Load Balancing). It disaggregates the function of load balancing into a group of regular servers, with the result that load balancing server hardware can be distributed amongst racks in the data center leading to greater agility and less fragmentation. The architecture creates a huge, flexible switching domain, supporting any server/any service and unfragmented server capacity at low cost.
- M. Casado, M. Freedman, J. Pettit, N. McKeown, and S. Shenker. Ethane: Taking control of the enterprise. In SIGCOMM, 2007. Google Scholar
Digital Library
- Cisco systems: Data center: Load balancing data center services, 2004.Google Scholar
- N. G. Duffield, P. Goyal, A. G. Greenberg, P. P. Mishra, K. K. Ramakrishnan, and J. E. van der Merwe. A flexible model for resource management in virtual private network. In SIGCOMM, 1999. Google ScholarDigital Library
- N. Feamster, H. Balakrishnan, J. Rexford, A. Shaikh, and J. van der Merwe. The case for separating routing from routers. In FDNA Workshop, 2004. Google ScholarDigital Library
- IEEE 802.1ah standard. http://www.ieee802.org/1/pages/802.1ah.html, 2008.Google Scholar
- M. Isard. Autopilot: Automatic data center management. Operating Systems Review, 41(2), 2007. Google ScholarDigital Library
- C. Kim, M. Caesar, and J. Rexford. Floodless in SEATTLE: a scalable ethernet architecture for large enterprises. In SIGCOMM, 2008. Google ScholarDigital Library
- M. Kodialam, T. V. Lakshman, J. B. Orlin, and S. Sengupta. A Versatile Scheme for Routing Highly Variable Traffic in Service Overlays and IP Backbones. In INFOCOM, 2006.Google ScholarCross Ref
- C. Kopparapu. Load Balancing Servers, Firewalls, and Caches. John Wisely & Sons Inc., 2002. Google ScholarDigital Library
- T. V. Lakshman, T. Nandagopal, R. Ramjee, K. Sabnani, and T. Woo. The SoftRouter architecture. In HotNets, Nov. 2004.Google Scholar
- A. Myers, T. S. E. Ng, and H. Zhang. Rethinking the service model: Scaling Ethernet to a million nodes. In HotNets, Nov. 2004.Google Scholar
- R. Perlman. RBridges: transparent routing. In INFOCOM, 2004.Google Scholar
- E. R. Hinden. Virtual router redundancy protocol (VRRP). RFC 3768, 2004. Google ScholarDigital Library
- S. Rooney, J. van der Merwe, S. Crosby, and I. Leslie. The Tempest: a framework for safe, resource assured, programmable networks IEEE Trans on Comm, 36(10):42---53, Oct 1998. Google ScholarDigital Library
- S. Sinha, S. Kandula, and D. Katabi. Harnessing TCP's burstiness with flowlet switching. In HotNets, 2004.Google Scholar
- IETF TRILL Working Group. http://tools.ietf.org/wg/trill/, 2008.Google Scholar
- H. Yan, D. A. Maltz, T. S. E. Ng, H. Gogineni, H. Zhang, and Z. Cai. Tesseract: A 4D network control plane. In NSDI, Apr. 2007. Google ScholarDigital Library
- R. Zhang-Shen and N. McKeown. Designing a Predictable Internet Backbone Network. In HotNets, 2004.Google Scholar
Index Terms
- Towards a next generation data center architecture: scalability and commoditization
Recommendations
VL2: a scalable and flexible data center network
SIGCOMM '09: Proceedings of the ACM SIGCOMM 2009 conference on Data communicationTo be agile and cost effective, data centers should allow dynamic resource allocation across large server pools. In particular, the data center network should enable any server to be assigned to any service. To meet these goals, we present VL2, a ...
Data center TCP (DCTCP)
SIGCOMM '10: Proceedings of the ACM SIGCOMM 2010 conferenceCloud data centers host diverse applications, mixing workloads that require small predictable latency with others requiring large sustained throughput. In this environment, today's state-of-the-art TCP protocol falls short. We present measurements of a ...
Sierpinski triangle based data center architecture in cloud computing
Computational clouds are increasingly becoming popular for the provisioning of computing resources and service on demand basis. As a backbone in computational clouds, a set of applications are configured over virtual machines running on a large number ...
Comments