By now, given all the launch and blogging activity activity over the past week or so, I am sure your understanding of and interest in Application Centric Infrastructure (ACI) will have grown. Many of you will be asking “how do I get started as quickly as possible?”, and “how can I free up some time and resources to investigate?” You understand the “what” - now, as I blogged recently on SDN, it’s time to understand more about the “why” and take action on the “how”. How then do you get off that start line as quickly as possible?
Get Set To Go With ACI
As with many things in life, it helps if you get help from someone who has “been there” and “done that”. And that’s where Cisco Services comes in, as Scott Clark, the VP for our Data Center Services team, introduced last week. So let’s talk about why Cisco Services should be your partner in this application centric world, and what services can help you.
Previously, we saw how Boeing division (BDS) and University of Siegen have deployed Multi-hop FCoE and realized significant benefits. This blog highlights similar benefits achieved by Engineering Shared Infrastructure Services (ESIS) department at Netapp.
Netapp’s ESIS department delivers and maintains end-to-end compute, storage, and network resources for internal Development and Quality Assurance engineers. These resources provide a platform for the innovation that creates storage systems and software, ultimately empowering NetApp customers around the world to store, manage, protect, and retain their data. The requirement was to have agility and versatility in providing storage connectivity between rack/blade Cisco UCS servers and NetApp clustered Data ONTAP storage arrays.
So, Netapp ESIS implemented an integrated model using Cisco Unified Fabric that supports FCoE from the UCS Servers through the Nexus Series Switches all the way to NetApp storage controllers.
This Unified Fabric architecture reduced the number of management points and provided easy scalability. The TCO benefits were quite significant -- Netapp saved $300K in the hardware costs, more than $80,000 in the implementation costs and 1/3 of an FTE’s timeRead More »
We’ve been getting a lot of great questions about ACI since our launch as people try and better understand the value of an application-oriented approach. I got the following questions on my blog post about the Application Virtual Switch that probed on some of the thinking behind an application-aware architecture, and why now was the right time to release it (after all, John Chambers called it the most disruptive Cisco innovation in a decade!). Anyway, on to the Q&A:
I’d like to know more about the path that Cisco pursued to evolve towards an “application aware” architecture. This back-story (how Cisco arrived at this juncture) would be very helpful to industry analysts, customers and institutional investors. Here’s some of the key questions on my mind.
- What were the primary roadblocks that inhibited the adoption of this innovative approach in the past?
I would say that the Application Centric Infrastructure (ACI) was a combination of a Eureka! moment, that people just never thought of it before, and that it was also an insightful evolution from early SDN technology. So, it might be fair to say that SDN had to come along, and then we realized, here might be a better way to program the network (with an application-oriented model, rather than a network-centric model).
That might be another way of saying that the lack of SDN as a precursor to ACI was a roadblock. But I think of it as networks were just built on hardware that were optimized to pass packets and other very specific tasks. And the limitations of historical networking protocols and traditional network designs, coupled with very limited ways in which you could manage a network and tell it what to do, all served as roadblocks to implementing anything like ACI. So the roadblocks that had to be cleared included the ability to program switches through software interfaces, and to centrally manage the software applications or controllers to orchestrate the broader network, not an individual device. Those are some of the things SDN brought along.
Wow ! The Application Centric Infrastructure (ACI) Launch was one of these amazing events which can only rejoice a social media leader like me .
13K+ registants for the webcast ! A Twitter storm (#ACI, #Insieme) Over 4000 mentions in a few hours ! A blog editorial plan including so far more than 10 Cisco blogs, 15 Technology partners blogs , and numerous articles from 3rd party, analysts and journalists -- A festival of videos, podcast, broadcast and infographics.
On the top of that I am pleased to welcome Cisco ACI a fast growing and independent LinkedIn group -- And I’d like to thank over 5500 professionals who already follow our brand new Cisco Data Center page on LinkedIn !
These series of facts show us how much interest our customers and partners find in this breakthrough vision and products announcement . So I figured out that a “little ” list of what’s available now will not hurt anybody !
This blog is designed to grow over the time thanks to your contribution -- So please feel free to post a comment with links (blogs, video, infographics , slideshare deck ) that I could have missed -- Or simply tell us what blog(s) or video(s) inspired you the most and why . And don’t hesitate to follow me @drombaut to make sure that I promote your suggestions:)
This week we’re back on Engineers Unplugged with special guests J Metz (@drjmetz) and Francois Zimmerman (@francoiszim), who discuss Flash Acceleration and the recent CVD release (Cisco Solution for Hitachi Unified Compute Solution) on the topic. Great discussion about how flash storage is changing the conversation, from the tech and business perspective:
What are you seeing in the industry? Agree or disagree, post a comment, send a tweet, follow along using one of the methods below!
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)