Affinity-Driven Networking

Transcription

1 Affinity-Driven Networking Implementing a dynamic, non-uniform network that matches capacity directly to application workload needs PLEXXI WHITE PAPER 1 Affinity Networking for Data Centers and Clouds

2 EXECUTIVE SUMMARY Cloud computing, distributed application frameworks and server virtualization solutions are reshaping data center traffic flows and impacting data center network designs. In addition, Big Data initiatives are pushing the envelope of clustered computing and storage architectures, demanding every ounce of performance to execute real-time decision management and data analytics. Legacy data center networks built to enable conventional client-server applications can t meet the agility and price/performance requirements of today s virtualized computing environments or the raw performance needs of clustered computing. This white paper reviews the impact of these new computing models on the data center and describes a new affinity-driven networking model that is specifically designed to address the distinct needs of today s cooperative applications and on-demand services. INTRODUCTION THE DATA CENTER NEEDS A NEW ING MODEL Today s world is awash in data. Nearly 2.5 quintillion bytes of data are created every day. And 90% of the data that exists in the world today has been created in the last two years alone. 1 Big Data means big business. Wikibon projects the worldwide Big Data market to grow from $5.1 billion to over $50 billion between now and Enterprises of every size and type are leveraging advanced computing facility architectures such as cloud computing data centers or clustered computing to boost business agility or support Big Data and other ultra-high performance application requirements. A Morgan Stanley survey of 300 IT decision-makers forecasts the percentage of enterprise workloads running in private cloud or virtualized environments to grow from 32% to 52% over the next three years and the portion of enterprise workloads running in public clouds to grow from 10% to 22%. 3 And according to IDC, cloud-enabled software will constitute nearly 24% of all new business software purchases and 13% of worldwide software spending by Virtualization and cloud computing are profoundly impacting the data center. The monolithic computing silos of the past are giving way to virtualized, converged IT environments. As the data center evolves, so to must the data center network. Legacy data center networks originally designed to enable conventional client-server applications are far too complex, costly and rigid for today s cooperative, elastic computing environments. They employ complicated networking protocols and convoluted hierarchies to achieve any-to-any server connectivity, and they rely on over-subscribed network designs that put untenable constraints on workload placement and provide no flexibility for changing workload needs. Simply put, the network has become a barrier to business innovation. This white paper reviews the impact of cloud computing, virtualization and distributed computing frameworks on the data center and makes the case for a new data center networking model built to satisfy the needs of cooperative applications, on-demand services and dynamic workloads. A model that employs a top-down approach that starts with application requirements and ends in the connectivity needed to achieve those needs, rather than the other way around. DATA CENTER TRENDS FROM SILOS TO CLOUDS Over the past twenty years, enterprises have built out autonomous islands of IT infrastructure to satisfy the needs of isolated clientserver and mainframe applications (see figure 1). In these stovepipe designs, a unique IT silo, with independent compute, network and storage resources, is dedicated to each business application ERP, CRM, office productivity suites, etc. ERP CRM Stovepipe data centers are costly and inefficient, with poor resource utilization, complex management and excessive power and cooling requirements. In contrast, today s data centers strive for much greater efficiencies in resource utilization. The goal of the modern data center is to maximize computing power per cubic foot of space, while simultaneously minimizing operating costs rack space, power, and cooling. Once the data center architecture has been put in place, the goal shifts to best matching application workloads with available compute resources so the infrastructure is optimally utilized at all times. Advances in information technology increasingly powerful multi-core servers, virtualization solutions and distributed computing frameworks help with this placement task by making compute resources much more flexible and by enabling application components to be more easily distributed across those resources. Legacy disjointed data centers designed for a fading era of client-server and mainframe computing are giving way to converged IT architectures that are more capable of enabling today s cooperative computing applications (Hadoop clusters, big data, grid computing, SOA applications, and OFFICE Figure 1 Conventional stovepipe IT architecture PAYROLL 1 Source: IBM web site 2 Wikibon Big Data Market Size and Vendor Revenues, May 29, Cloud Computing Takes Off, Morgan Stanley Blue Paper, May 23, Market Analysis Perspective: Worldwide SaaS & Cloud Services, 2011: New Models for Delivering Software; IDC December

3 ERP CRM OFFICE PAYROLL Consolidated Virtualized Data Center Infrastructure Figure 2 Virtualized IT architecture Web 2.0 mash-ups) and are better suited for enabling cloud-based services. By pooling compute, network and storage resources into more advanced data centers (see figure 2) where workloads can be more easily applied to available resources, enterprises and cloud providers can contain CAPEX and OPEX, reduce IT sprawl, and improve business and service agility. THE BOTTLENECK Conventional data center networks built around monolithic computing silos are far too complex, costly and rigid for today s converged IT environments. The modern data center requires a fundamentally new data center networking model. Most legacy data center networks are based on oversubscribed, hierarchical designs. A typical data center network includes an access tier, 5 an aggregation tier 6 and a core tier (see figure 3). The access tier is made up of low-cost ToR (top-of-rack) Ethernet switches connecting rack or blade servers and IP-based storage devices (typically 100Mbps or 1GbE connections). The access switches are connected via Ethernet to a set of more expensive (and power hungry) aggregation switches (typically 10GbE connections) which in turn are connected to a layer of core switches which connect the data center to the rest of the enterprise (an intranet) and the outside world (the Internet). CORE AGGREGATION ACCESS Figure 3 Conventional hierarchical data center network 5 Sometimes referred to as the edge tier 6 Sometimes referred to as the distribution tier 3

4 APP 1 APP 2 APP 1 APP 2 APP 3 APP 2 APP 3 Conventional Stovepipe IT Architecture Conventional Virtualized IT Architecture Figure 4 Virtualized IT architectures reshape data center traffic flows Hierarchical networks are inherently costly and inefficient. They do not scale linearly. As the network expands, additional tiers are layered on, and increasing numbers of expensive aggregation switch ports are added to the mix. And with the adoption of increasingly-denser multi-core servers with 10 GbE and 40 GbE network interfaces the problem only becomes worse. Hierarchical networks also impede the performance of contemporary applications. While ideal for transporting conventional north-south client-server traffic flows in and out of the data center, legacy networks aren t well suited for the bandwidth-intensive, delaysensitive east-west traffic flows that dominate the modern data center. Hierarchical switched networks worked well in traditional client-server and mainframe environments where most of the computation was performed on a host and the majority of traffic flowed in and out of the data center to and from clients. But server virtualization solutions and new distributed computing frameworks and cooperative applications are radically reshaping data center traffic patterns (see Figure 4). In today s world, more often than not, computation is distributed across multiple servers. Workloads are divided into smaller tasks and processed in parallel on separate physical or virtual machines. And virtual machines can migrate from server to server in response to changing demands or conditions. The vast majority of today s data center traffic stays within the data center, flowing within and between servers. (See sidebar) The Cisco Global Cloud Index reveals 77% of today s data center traffic stays within the data center and forecasts intra-data center traffic volumes to grow at a steep 33% CAGR between 2010 and 2015 as cloud computing and virtualization initiatives skyrocket. Source: Cisco Global Cloud Index: Forecast and Methodology, of the network hinders the performance of these applications. East-west traffic must traverse multiple switching tiers. Each intermediary switch adds latency. And high oversubscription ratios lead to network congestion, dropped packets and poor application performance. Web clusters, database clusters, clustered file systems, VMotion, Map-Reduce processing etc. all make extensive use of messaging and data movement/replication and require low latency, lossless, predictable connectivity. But the oversubscribed, hierarchical nature 4

5 HOW DID WE GET HERE? HOW DO WE MOVE FORWARD? from point A to point B the challenge in the data center is a multidimensional problem we call affinity. Today s data center network designs trace their roots back to the earliest days of client-server computing. Back in the 1980s organizations began implementing shared media LANs (Ethernet, Token Ring, even Token Bus) to connect PCs and workstations to UNIX and Windows servers installed departmentally or in a central computer room. Individual LANs were interconnected using bridges and ultimately routers. Over time Ethernet switching emerged as a more cost-effective and scalable alternative to conventional shared media LANs. The first Ethernet switches were introduced in 1990 and by the mid-1990s businesses began aggressively deploying Ethernet switching technology and implementing hierarchical switched networks as a more efficient way of interconnecting and scaling intranets. 7 With the advent of rack servers and blade servers, enterprises began consolidating computing resources into centralized data centers. They implemented data center networks using equipment, architectures and network protocols originally designed for interconnecting distributed autonomous subnets. But in fact, data center networks are far different than geographically-dispersed campus or wide area networks with distinct design considerations and constraints. In order to make these products work for data centers, they were configured into large switched hierarchies using two and three tiers creating uniformly distributed capacity networks and using existing Layer 2 and Layer 3 protocols to help manage the distribution of workloads across those networks. The Layer 2 and Layer 3 networking protocols developed in the 1980 s and 1990 s were introduced to solve what we ll call the Internet problem. The Internet is an arbitrary interconnection of links, of arbitrary quality, and fluctuating state extending across distinct administrative domains. The layered protocol stack evolved as a way to reliably deliver packets from point A to point B across this unbounded, unknown, uncontrollable environment. The idea of creating a top-down networking model based on an holistic view of the Internet and the performance requirements of the upper applications was unfathomable. So protocol designers took a bottom-up approach, crafting link layer and network layer protocols that could be executed using the limited memory and processing environments of the switches and routers of the era. But the data center network is inherently different than the Internet. The data center is bounded and manageable. Administrators have complete visibility and control over the entire environment, and connectivity is predictable and reliable. Complex network topology protocols aren t required in the data center. Connectivity, for all intents and purposes, is a given. The challenge in the data center is not a one-dimensional problem of connectivity delivering packets 7 According to IDC, the Ethernet switching market grew a remarkable 390% from 1995 to 1996 (based on port counts). FITTING AFFINITIES INTO THE Affinity refers to the relationship between data center resources required to execute a given workload - the physical or virtual compute, storage and network resources. We call any given set of these resources an Affinity Group. In conventional networking, the goal is to make these affinities irrelevant, or to strive for a completely uniform network from any given point to any given point. However, what should actually be the goal is to satisfy the needs of the Affinity Groups, first and foremost. So rather than providing equal connectivity to all resources regardless of their need for connectivity with each other, we should optimize the network around the needs of the Affinity Groups. By satisfying affinity requirements we can ensure all workloads have the full set of resources required to meet their unique performance needs and service level commitments, and instead of scaling the network equally in all directions, we scale it with the needs of the Affinity Groups. Affinity needs are knowable as first configuration principles. Workloads are served by compute and storage resources that have specifiable affinities to each other and to other workload resources, and this affinity is generally obtainable from configuration and orchestration systems. By taking a top-down approach and dynamically engineering the network around these affinities we can In order to fully implement affinity needs in the data center, the physical network itself should have the ability to be reorganized non-uniformly such that capacity is greatest in places where it is needed and nominal in places where it is not needed. And as the needs change, the network must also continually change to ensure that the affinity needs are always met. satisfy application performance and service level requirements while making optimal use of network resources. Rather than switching or routing we call this operation fitting. The notion of affinities is not new. For years, data center architects have understood that to maintain peak application performance, the optimal interconnection of interdependent application resources (such as servers, VMs, databases, network services, storage, etc.) is paramount. Until now, application architects have implemented affinity concepts manually by co-locating instances of a workload on the same physical switch or adjacent switches. But as workloads become larger, more portable, and more complex it is becoming increasingly difficult - if not impossible - to implement affinities by hand. In order to fully implement affinity needs in the data center, the physical network itself should have the ability to be reorganized 5

6 non-uniformly such that capacity is greatest in places where it is needed and nominal in places where it is not needed. And as the needs change, the network must also continually change to ensure that the affinity needs are always met. To that end, Plexxi has created a new data center networking solution that allows data center operators to build and manage a network from the perspective of the data center workloads and implement those workloads directly into a non-uniform multi-core network that ensures capacity is where it needs to be. The Plexxi solution is based on a top-down model that starts with application requirements and ends in the connectivity needed to achieve those needs, rather than the other way around. It features intelligent application software that automatically discovers workload affinity requirements and dynamically configures a network to meets those needs exactly using state-of-the-art Ethernet switching systems. Public cloud providers and enterprises building private clouds can leverage the Plexxi solution to implement flatter, more agile and cost-effective networks to handle the bandwidth-intensive, delaysensitive east-west traffic flows that accompany today s distributed computing and virtualization initiatives. Whether supporting a single application for a single user-base or a massive internet-scale data center or public cloud, a Plexxi network provides direct server-toserver network capacity that can be controlled and fully managed from the application perspective. CONCLUSION Enterprises are turning to much more advanced data center architectures to improve business agility, reduce expenses and accelerate business innovation and are implementing clustered/highperformance computing environments to increase application performance. These new computing architectures redefine the way IT assets are deployed and consumed, and dramatically affect the way data center networks are architected and managed. Conventional hierarchical data center networks built to support stovepipe IT architectures can t meet the agility, price/performance or raw performance requirements of today s advanced computing environments. Public cloud providers and enterprises deploying private clouds or compute clusters must implement flatter, simpler, affinity-driven data center networks to support the bandwidthintensive, delay-sensitive server-to-server traffic flows that dominate today s cooperative, elastic computing environments. Plexxi offers the first and only affinity-driven networking solution, specifically built for today s high performance, on-demand data centers. Only Plexxi offers a unique network that s built from an apps-down not wires up approach to enable dynamically-orchestrated, direct server-to-server network capacity based on workload affinities and an innovative multi-core network that can implement non-uniform Copyright 2012 Plexxi, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. Plexxi and the Plexxi logo are registered trademarks of Plexxi, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. The Role of Software-Defined Networking in the Cloud Conventional decentralized networking architectures aren t well suited for delivering on-demand services. They implement both forwarding and control functions at the device level, with each switch or router providing an embedded, low-level proprietary management interface. Provisioning and troubleshooting endto-end network services can be time-consuming and error-prone tasks, involving multiple devices and distinct management interfaces. And integrating devices into higher-level operations support systems and business support systems can be an expensive, protracted undertaking. Software-Defined Networking (SDN) is emerging as a more scalable, extensible and open way of building networks. By decoupling forwarding and control functions, centralizing network intelligence and state information, and providing an abstraction layer with open APIs, SDN allows enterprises and service providers to build more scalable, agile and easily-manageable networks. The Plexxi solution delivers on the promise of SDN by exploiting a deconstructed network architecture that features intelligent application software (application layer), centralized control functionality (control layer), and state-of-the-art Ethernet switching systems (infrastructure layer). By deconstructing the network infrastructure into these three tiers and leveraging SDN architectural principles between the layers, we can evolve capacity, control capabilities, and network applications independently, and we can also make the network directly responsive to the business application needs it supports. APPLICATION LAYER Business Applications CONTROL LAYER Network Services INFRASTRUCTURE LAYER Network Devices capacity based on these affinity needs. Using Plexxi s intelligent control software and innovative Ethernet switching technology, enterprises and cloud providers can build flat, low-latency, high-performance networks that readily accommodate the delay-sensitive, bandwidthintensive east-west traffic flows that accompany today s advanced computing initiatives. To learn how Plexxi can help you build a more scalable, agile and cost-effective data center network please visit us on the web at or contact a Plexxi sales representative at APIs Control Data Plane Interface 6