In this week’s episode of Engineers Unplugged, storage industry luminaries Chad Sakac (@sakacc) of EMC and Vaughn Stewart (@vstewed) of NetApp discuss the concept of Stretch Clustering, a topic they’ve been covering at tech events for awhile now. Check out their discussion here:
Welcome to Engineers Unplugged, where technologists talk to each other the way they know best, with a whiteboard. The rules are simple:
Episodes will publish weekly (or as close to it as we can manage)
Submit ideas for episodes or volunteer to appear by Tweeting to @CommsNinja
Practice drawing unicorns
Collaborative Storage Unicorn, courtesy of Chad Sakac and Vaughn Stewart
For more information on stretch clustering and all storage topics, be sure to check out Chad’s blog and Vaughn’s blog. Questions, comments, thoughts? Post them here or join the conversation with @CiscoDC on Twitter!
For many months now, we’ve talked about the Journey to Cloud Computing and how an evolution within your Data Center is needed to make that a reality. In many cases, we looked at this from an application perspective, focused on the interaction between automation, applications, servers, storage and the edges of the network.
But many of you have asked us to provide you a broader understanding of the role the Network plays in the Journey to Cloud Computing. Specifically you’ve asked us to highlight several areas:
What is Cisco’s perspective and strategy around the usage of multiple types of Cloud Computing (Private, Public, Hybrid, Community) and what is needed from the network to interconnect all these offerings?
How does my business manage the network transitions needed between today’s applications (often client-server), the virtualization of those application, and next-generation web and big data applications?
What considerations do we need to make within my Data Center as we try and maximize efficiency and scalability?
What considerations do we need to make at the edges of our networks when the proliferation of devices is almost out of control?
Are there ways to protect my network investments while still having the flexibility to deal with the business uncertainties that are around the next corner?
I’m not a car person and I don’t worry too much about what’s under the hood. That means that I’m just a car user, I only want to turn the ignition key and drive. In the Data Center world, the server team is typically a user of the network. Server guys don’t want to know how the network is implemented. They just want their VLANs to extend to the whole network so that they can connect their devices with no constraint, without having to worry about high availability, risk containment, link provisioning… network stuff. That’s precisely what FabricPath is designed to offer them: a network that looks like a single switch, the simplest networking entity. This “Fabric” offers efficient any-to-any connectivity with high bandwidth and low latency, all without having to understand how it works.
Of course, this user perspective is an abstraction. The following Figure 2 represents an example of the physical topology of the network, a Clos fabric, typical in Data Center environments. Note that this could just as well be a ring, a star, or even a network distributed across two sites. FabricPath turns an arbitrary topology into a Fabric and does not lock you into a particular model.