Special Coverage Series

Network Computing

Special Coverage Series

Commentary

Michael Bushong
Michael Bushong VP of Marketing, Plexxi

SDN's Endgame: Infrastructure Orchestration Through Data Sharing

Automation is a top goal for software-defined networking, but reaching that objective requires integration of computing, storage and networking. Data is the currency for that integration.

Over the past 18 months, the networking industry has focused predominantly on defining what software-defined networking (SDN) is and which technologies ought to be included under the moniker. This has pushed the most meaningful dialogue outside the scope of many discussions: namely, what is the eventual endgame?

SDN is not about centralizing control for the sake of centralization. A huge part of the objective is to automate workflows, which makes provisioning, monitoring, troubleshooting, and overall managing a network easier. To do this well, the network needs to be treated as a resource that can be sliced, diced, and delegated to as part of the application delivery process. But application workloads do not stop at the boundaries of the network.

Applications require more than just network resources -- compute, storage, and even other applications are part of the equation. If the long-term vision is to enable a highly orchestrated environment, it means that the bounds of integration need to extend well beyond the network. Even if the networking industry successfully executes against the current SDN vision, by the time those architectures are in place, they will be obsolete as IT shops everywhere look to extend the concepts to the whole of IT.

It is challenging in its own right to integrate a large homogeneous environment that exists within a single technology space. How do you even go about integrating across infrastructure silos?

The marketing folks in the room will talk about bringing these silos crashing to the ground. But, a tightly-integrated system that spans an ever-expanding IT infrastructure would threaten to bring the whole thing to its knees. Sound architectural design embraces modularity. The important bit is how these different modules come together. Those interfaces between components are what allow autonomous activity while preserving the interdependent relationships between components working towards a common goal.

More simply, the right answer is not to lump all of compute, storage, and networking under a single system that is tightly integrated. Rather, the solution is in identifying the means by which these components can interact when necessary.

The typical networking response to interaction is protocols and APIs. But protocols generally don't extend outside the network, and APIs are a very insular way of tackling the problem ("Code to MY interface and everything is good"). The question we ought to be asking is: How should components interact?

[Read how vendors are using software to handle complex operations and overcome obstacles to scaling in networking and storage in "SDN Helps Break Down Barriers To Scaling."]

Ultimately, we need to design systems where each component can act semi-autonomously based on a common view of what the broader system needs. The currency for this kind of coordination between components is not protocols or APIs, it's data. If each component -- compute, storage, or networking --has access to the data driving the system, it can consume that data and tune its own behavior accordingly.

For example, imagine a new Hadoop application is deployed. When a job is executed, that job will require compute, storage, and networking. If the data that specifies that job can be shared, it becomes the blueprint from which the servers, storage devices, interconnecting switches and routers can all work. Virtual machines can be spawned on servers in close proximity to the storage required for the job, load balancers and firewalls can be provisioned, and the network paths between the various elements can be optimized for latency and bandwidth.

The key to this type of orchestration is the data. How is that data captured? How is it relayed to interested parties? How is it normalized across the different elements, each of which consumes data at different times and in different formats?

None of these questions is unique to the network. The answers will necessarily extend across the various infrastructure elements. This means that those caught up in the throes of SDN-euphoria need to talk more with their counterparts in other silos. Because as it stands, software-defined networking, software-defined storage, and the already virtualized compute space need to come together. And, if that merger is not deliberately planned for, all of IT will be staring at a disappointing outcome in a couple of years.



Related Reading


More Insights



Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | Please read our commenting policy.
 

Editor's Choice

Research: 2014 State of Server Technology

Research: 2014 State of Server Technology

Buying power and influence are rapidly shifting to service providers. Where does that leave enterprise IT? Not at the cutting edge, thatís for sure: Only 19% are increasing both the number and capability of servers, budgets are level or down for 60% and just 12% are using new micro technology.
Get full survey results now! »

Vendor Turf Wars

Vendor Turf Wars

The enterprise tech market used to be an orderly place, where vendors had clearly defined markets. No more. Driven both by increasing complexity and Wall Street demands for growth, big vendors are duking it out for primacy -- and refusing to work together for IT's benefit. Must we now pick a side, or is neutrality an option?
Get the Digital Issue »

WEBCAST: Software Defined Networking (SDN) First Steps

WEBCAST: Software Defined Networking (SDN) First Steps


Software defined networking encompasses several emerging technologies that bring programmable interfaces to data center networks and promise to make networks more observable and automated, as well as better suited to the specific needs of large virtualized data centers. Attend this webcast to learn the overall concept of SDN and its benefits, describe the different conceptual approaches to SDN, and examine the various technologies, both proprietary and open source, that are emerging.
Register Today »

Related Content

From Our Sponsor

How Data Center Infrastructure Management Software Improves Planning and Cuts Operational Cost

How Data Center Infrastructure Management Software Improves Planning and Cuts Operational Cost

Business executives are challenging their IT staffs to convert data centers from cost centers into producers of business value. Data centers can make a significant impact to the bottom line by enabling the business to respond more quickly to market demands. This paper demonstrates, through a series of examples, how data center infrastructure management software tools can simplify operational processes, cut costs, and speed up information delivery.

Impact of Hot and Cold Aisle Containment on Data Center Temperature and Efficiency

Impact of Hot and Cold Aisle Containment on Data Center Temperature and Efficiency

Both hot-air and cold-air containment can improve the predictability and efficiency of traditional data center cooling systems. While both approaches minimize the mixing of hot and cold air, there are practical differences in implementation and operation that have significant consequences on work environment conditions, PUE, and economizer mode hours. The choice of hot-aisle containment over cold-aisle containment can save 43% in annual cooling system energy cost, corresponding to a 15% reduction in annualized PUE. This paper examines both methodologies and highlights the reasons why hot-aisle containment emerges as the preferred best practice for new data centers.

Monitoring Physical Threats in the Data Center

Monitoring Physical Threats in the Data Center

Traditional methodologies for monitoring the data center environment are no longer sufficient. With technologies such as blade servers driving up cooling demands and regulations such as Sarbanes-Oxley driving up data security requirements, the physical environment in the data center must be watched more closely. While well understood protocols exist for monitoring physical devices such as UPS systems, computer room air conditioners, and fire suppression systems, there is a class of distributed monitoring points that is often ignored. This paper describes this class of threats, suggests approaches to deploying monitoring devices, and provides best practices in leveraging the collected data to reduce downtime.

Cooling Strategies for Ultra-High Density Racks and Blade Servers

Cooling Strategies for Ultra-High Density Racks and Blade Servers

Rack power of 10 kW per rack or more can result from the deployment of high density information technology equipment such as blade servers. This creates difficult cooling challenges in a data center environment where the industry average rack power consumption is under 2 kW. Five strategies for deploying ultra-high power racks are described, covering practical solutions for both new and existing data centers.

Power and Cooling Capacity Management for Data Centers

Power and Cooling Capacity Management for Data Centers

High density IT equipment stresses the power density capability of modern data centers. Installation and unmanaged proliferation of this equipment can lead to unexpected problems with power and cooling infrastructure including overheating, overloads, and loss of redundancy. The ability to measure and predict power and cooling capability at the rack enclosure level is required to ensure predictable performance and optimize use of the physical infrastructure resource. This paper describes the principles for achieving power and cooling capacity management.