Hey folks–this is the second of three posts looking a little more closely at VXLAN. If you missed the first post, you can find it here. In this installment we are going to look at the some of the other options out there. Two of the most common questions we see are “why do I need yet another protocol?” and “can I now get rid of X?” This should help you answer these questions.So, let’s dig in… Read More »
Yes, I am still talking about VXLAN, rather you folks are still talking about VXLAN, so I thought its worthwhile digging deeper into the topic since there is so much interest out there. There also still seem to be a fair number of misconceptions around VXLAN, so let’s see what we can do to clear things up.
This time around, I have some partners in crime for the discussion:
Larry Kreeger is currently a Principal Engineer at Cisco Systems’ SAVTG working on Nexus 1000V architecture. Larry has a wide ranging background in networking accumulated from over 25 years of experience in developing networking products. His recent focus is data center networking, especially as it relates to data center virtualization.
Ajit Sanzgiri has worked on various networking technologies at Cisco and other bay area networking companies over the last 16 years. His interests include hardware based switching and routing solutions, Ethernet and wireless LANs and virtual networking. Currently he works on the Nexus1000v and related network virtualization products.
So, Larry and Ajit have put together this VXLAN primer–its fairly dense stuff, so we are breaking this into three posts. In this initial post, we’ll cover the basics–why VXLANs and what is VXLAN. I know I’ve covered this to some degree already, but Larry and Ajit are going to dig a little deeper, which will hopefully help clarify the lingering questions and misconceptions. In the next post, we’ll discuss how VXLAN compares with the other tools in your networking arsenal, and, in the final post, we’ll cover more of the common questions we are seeing.
Oracle OpenWorld is definitely around the corner – Our speakers are now fine tuning their presentation . But I couldn’t resist to contact some of them with the hope to have valuable insights. As I was interviewing John McAbel (Oracle VM consolidation and Path to the cloud on Cisco UCS) , and Siva Sivakumar (Cisco UCS Reference Achitecture for Oracle Solutions) in San Jose, I sent Amy Lewis , our favorite roving reporter (actually competing with Aneel ) for an impromptu meeting with Dan Loomis, as both of them are living in RTP (remember the recent opening of the RTP data center ?)
Dan Loomis is a System/chief architect for the customer services area. His passion is definitely about aligning business and technology architecture, and working on strategic planning .Dan intends to share with the audience in his speaking session (Service Transformation: Building Process Automation for Complex Service Offerings ) framework and methodology learned.
Here is the extract of the session
High-technology companies have an increasing focus on creating and enabling services to grow profits and customer satisfaction by expanding value, differentiation, and capabilities. These services create extensive requirements to help companies successfully support the new service models. In this session, Cisco discusses its rigorous approach to platform transformation that brings together thorough performance metric identification and evaluation and combines with new strategy requirements to define its next platform.
Read More »
Next week from Monday, October 3rd to Friday, October 7th, Interop NY will be in full swing.
As usual, Cisco will be at the Expo and represented in various sessions throughout the event. We’ll have a big booth (#121) where Cisco representatives will be on hand to discuss and demo current Cisco technologies in: IPv6, UCS, MediaNet, WAAS, Secure-X, and more. We’re also a premiere sponsor of InteropNet, where Cisco is leading the design of the show network, featuring 10 gig over copper connectivity and Cisco’s Prime management system and wireless technologies — offering full IPv6 capabilities. Engineer-led booth tours will be available each day at the InteropNet NOC booth.
For a while now, I’ve been bothered with the word commodity. Like legacy, greenfield, there are value judgements implicit in the words. When we apply them to technology adoption, they serve as marketing oars to rock the new tech boat, but are not useful when you need a fish for dinner.
And this article on the NYSE community cloud is a great example of why there are no commodity clouds.
The NYSE’s community cloud platform is design to ensure that its customers are treated fairly, and it ensures them that the maximum latency that any user will experience in this data center is 70 microseconds (one millionth of a second) round-trip for any message, O’Sullivan said.
“We guarantee that nobody will have an advantage on the network,” said O’Sullivan. “It’s designed to be a level playing field for trading.
Basically, this compute service comes with a latency service level and a promise that no one gets better latency, thus ensuring a level playing field for traders.
So it’s “level-playing-field-as-a-service;” which is right and ridiculous. Right because that’s the differentiators; ridiculous that I have to pull the *aaS to describe what before I would have simply called “service.”
There was a time when coffee was called a commodity, then Howard Schultz of Starbucks came along, and Peet’s came along, and next, we are all paying $5 for coffee.
Even frozen pork bellies are not commodities anymore. You might remember this quote:
“Pork bellies! I have a hunch something exciting is going to happen”
But as you see from the link, even pork bellies are not commodities anymore in the trading markets.
And then again, pork bellies are not commodities according to chef Michael Mina–it’s now branded, locally-grown, organic and … sexy. Pork bellies. Sexy.
So you can see why I might think clouds are far, far from being commodities like pork bellies. Which are not commodities anymore.
As for x86 being a commodity? I don’t see Intel suffering. Don’t confuse platform with commodity.