Cisco’s vision for ‘The World of Many Clouds’™ drove us to a leading position in the Cloud Market:
- Cloud infrastructure equipment sales: Ranked #1 in the industry three quarters in a row by Synergy Research for Q3 2013
- According to IDC analysts and buyer perception, Cisco is an IDC MarketScape “Major Player” worldwide. (IDC MarketScape: Worldwide Cloud Professional Services 2013 Vendor Analysis)
- Cisco named a “Strong Performer” and earns top marks on strategy for strategic vision and roadmap in private cloud software solutions (The Forrester WaveTM: Private Cloud Solutions, Q4 2013, Forrester Research, Inc.)
On January 28, at Cisco Live! in Milan, we announced important extensions to our Cloud Portfolio.
In this fast evolving cloud market, customers require flexible solutions to extend their infrastructure, take advantage of public cloud services and optimize their sourcing options, while maintaining consistent policy and security mechanisms.
Use cases like Test and Develop, Capacity Augmentation and Disaster Recovery require customers to integrate internally sourced services with public cloud and virtual private cloud services. Business leaders are realizing that the use of public cloud services needs be to standardized by IT to manage escalating costs, security risks and compliance requirements.
Enterprises and public sector institutions are eager to embrace a hybrid cloud model, but current approaches offered by large public cloud providers are proprietary and lock customers into their way of consumption. Other hybrid cloud approaches require customer to have a consistent hypervisor environment.
Customers want to make hybrid cloud the new normal, and they expect to do it with choice, consistency, control and compliance.
Our new Cisco InterCloud solution accomplishes all that – it enables bi-directional secure workload mobility to and from any supported or participating cloud provider, is hypervisor agnostic and it works with heterogeneous infrastructures. Depending on your IT and business requirements you can now move your data and applications to the Public Cloud with end-to-end security.
At the same time, Cisco InterCloud allows cloud providers to lower the barrier to public and virtual private cloud adoption, and easily extend their customers encapsulated data center into the public cloud with consistent network and security policies.
Read More »
Tags: Cisco Cloud Services, cisco intercloud, Cisco Live Milan, Cisco ONE, cloud, world of many clouds
Before recently taking on a new role as Cisco’s vice president and general manager of Software-Defined Network (SDN) with the enterprise networking group, I served as the vice president and general manager of Cisco’s Unified Access portfolio and led the expansion of the Catalyst 2k, 3k and 4k series product line, which has seen a lot of growth and developed a strong customer base over the past couple of years. Cisco invests heavily in R&D for these products, and has introduced many innovations improving security, application visibility/control, energy savings and converged wired and wireless infrastructure over the past few years.
But as I shifted into my new role and looked back at some of the new Unified Access solutions we introduced alongside our system architecture, I saw a curious disconnect: in some cases, it was getting more difficult for our customers to quickly take advantage of our new innovations.
At Cisco, we design products to make customers’ lives easier and more productive. Not to gather dust because they’re too hard to figure out!
Read More »
Tags: ACI, APIC, Campus and Branch, catalyst, Cisco ONE, citrix, Enterprise Networking, Glue Networks, IT, Jeff Reed, programmable networks, SDN
Would SDN, by any other name, still smell as sweet?
Perhaps I’m in the minority that is still frustrated by this, but as a marketing person who is tasked with explaining technology and solutions to customers and prospects, I feel hamstrung by a lack of a widely agreed upon definition of what is and is not “SDN” still. This usually comes up in discussions about our new Application Centric Infrastructure (ACI), and how it compares to traditional SDN concepts, as well as alternative approaches, such as overlay networks advocated by VMware.
The topic came up again this week with a NetworkWorld article in which the head of VMware’s network virtualization business is now saying, “SDN will never happen” (our rebuttal). Well, what is happening, if it’s not SDN? Or just because the technology has evolved, do we need to create a new term just because some early assumptions the industry made have changed? As we start out a new year, I thought it a good time to try and reframe the definition, and look at how the trends in SDN may be shaping up to extend the concept into new areas.
Why do customers need SDN?
By early 2012, there was so much hype and expectations around Software Defined Networking, focused on the ability to “program” the network, that real customer use cases and the killer SDN app was lost in the conversation. But what slowly emerged, that is driving all the investment, pilots and product designs is a much better way to manage the data center and cloud network, and to automate IT tasks so that the infrastructure could respond dynamically to rapidly changing business conditions and requirements. The “intelligence” to make all that happen is moving from the network devices and device management consoles, to centralized policy-management platforms, orchestration tools and cloud-managers.
What’s caused the biggest evolution in SDN is the realization that very few organizations really have the desire, skills and incentives to write a new class of applications to a published API to program the network. These users are outlying use cases compared to the vast majority of organizations just looking to automate IT tasks, accelerate application deployment, make their cloud networks more flexible, and better align their IT infrastructure with business requirements. The focus has shifted from SDN being an open API/controller platform, to a platform capable of hosting a myriad of orchestration and IT workflow automation solutions that drive customers to their end goal. To that end, ACI is meeting all those objectives, and in more advanced and innovative ways than earlier SDN approaches.
Read More »
Tags: ACI, Cisco ONE, Open Daylight, Open Network Environment, OpenFlow, OpenStack, SDN, software defined networking, XNC
The London Eye
Last week I started my SDN reflections on the London Gartner Data Center Conference, and I found I had quite a lot to discuss.
Last week I covered:
- Do we need SDN?
- SDN and the Gartner Hype Cycle
- SDN Deployment Models
So here is the concluding part. This week I’ll cover:
- Overlay-Based SDN — and the questionable assumptions being made by others in this area (good for Gartner for calling these out!)
- The SDN Vendor Explosion Challenge,
- The “Unspoken Costs” of SDN Deployment, and
- The “How” of SDN is still missing.
I hope you find this useful and informative and as always, feel free to debate with me around my observations!
Read More »
Tags: architectural approach, Cisco ONE, Cisco onePK, Cisco Services, SDN controller, software defined network
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.
Read More »
Tags: ACI, APIC, application centric infrastructure, Cisco ONE, nexus, onePK, OpenFlow, SDN, XNC Controller