First and foremost, demand for Cisco ACI is terrific and global already. We already have more than 300 customers in our pipeline spanning every geography and every customer segment. Just as with the ramp-up of the world-beating Cisco Unified Computing System, we’re seeing the greatest early adoption in nimble mid-sized businesses. About 30% of our pipeline is in what we call the ‘commercial’ segment here in the US. Another 15% is with the largest US enterprises. 19% of orders are in Asia Pacific and a healthy 13% in EMEAR. In short…EVERYONE wants a piece of ACI!

That type of customer demand will be music to our reseller partners’ ears. Obviously partners are crucial to our success, in the data center (and in everything Cisco does) and we’re making sure the Cisco partner ecosystem is able to accelerate ACI momentum too. In just one month since launch, we have trained 125 partners, and we will train an additional 350 with 1500 engineers in the next six weeks.

It was suggested in some quarters of the media this week that it will take years for the power of ACI to be felt in the market. Knowing the passion and commitment of our partner ecosystem, we’re betting that ACI, both in terms of the building blocks available today, and the full system availability a few months from now, we will make a huge impact much faster than that!

In his address to more than 100 financial analysts in New York, John Chambers also touched on the importance of Cisco ACI’s open ecosystems approach, and the progress we’re making there. Let me re-cap:

Since early November we have established an OpenStack working group which includes Cisco, IBM, Juniper, Intel, Plexxi, Big Switch, and Midokura to develop application-centric Neutron APIs. We also founded an Open Daylight working group with IBM and Plexxi to develop an application-centric API layer, and we’ve created an OpenSource Community Repository here.

Of course, we’re just at the beginning of the journey and there is so much more to come. In the next quarter we plan to release an ACI Python SDK built on the ACI Restful API, an ACI southbound device API, and we’ll release the Application Policy Infrastructure Controller (APIC) simulator to give customers and developers early access to the APIC environment ahead of its full availability in Q2 calendar 2014.

As you can see, we’re off to a good start with Cisco ACI. What customers are telling me is that they are not satisfied with the limitations on network performance at scale, and security that the overlay model of SDN forces upon them. Tightly coupling hardware to software overcomes those limitations.

We'd love to hear from you! To earn points and badges for participating in the conversation, join Cisco Social Rewards. Your comment(s) will appear instantly on the live site. Spam, promotional and derogatory comments will be removed.

Some of the individuals posting to this site, including the moderators, work for Cisco Systems. Opinions expressed here and in any corresponding comments are the personal opinions of the original authors, not of Cisco. The content is provided for informational purposes only and is not meant to be an endorsement or representation by Cisco or any other party. This site is available to the public. No information you consider confidential should be posted to this site. By posting you agree to be solely responsible for the content of all information you contribute, link to, or otherwise upload to the Website and release Cisco from any liability related to your use of the Website. You also grant to Cisco a worldwide, perpetual, irrevocable, royalty-free and fully-paid, transferable (including rights to sublicense) right to exercise all copyright, publicity, and moral rights with respect to any original content you provide. The comments are moderated. Comments will appear as soon as they are approved by the moderator.