Customers gain great value from server virtualization in the form of virtual machines (VM) and more recently Linux Containers /Dockers in data centers, clouds and branches. By some estimates, more than 60 % of the workloads are virtualized although less than 16% of the physical servers (IDC) are virtualized (running a hypervisor). From a networking perspective, the hypervisor virtual switch on these virtualized servers plays a critical component in all current and future data center, cloud, and branch designs and solutions
As we count down to the annual VMworld conference and reflect on the introduction of the Cisco Nexus 1000V in vSphere 4.0 six years ago, we can feel proud of what we have achieved. We have to congratulate VMware for their partnership and success in opening vSphere networking to third party vendors. It was beneficial for our joint customers, and for both companies. VMware and Cisco could be considered visionaries in this sense. Recognizing this success, the industry has followed.
Similarly we praise Microsoft as well, for having also provided an open environment for third-party virtual switches within Hyper-V, which has continued gaining market share recently. Cisco and Microsoft (along with other industry players) are leading the industry with the latest collaboration on submitting the OpFlex control protocol to the IETF. Microsoft’s intention to enable OpFlex support in their native Hyper-V virtual switch enables standards-based interaction with the virtual switches. Another win for customers and the industry.
In KVM and Xen environments, many organizations have looked at Open vSwitch (OVS) as an open source alternative. There is an interest in having richer networking than the standard Linux Bridge provides, or using OVS as a component for implementing SDN-based solutions like network virtualization. We think that there is an appetite for OVS on other hypervisors as well. Cisco is also committed to contributing and improving these open source efforts. We are active contributors in the Open Virtual Switch project and diligently working to open source our OpFlex control protocol implementation for OVS in the OpenDaylight consortium.
To recap on the thoughts from above, Table 1 provides a quick glance at the options for virtual networking from multiple vendors as of today:
Table 1: Hypervisors and Choices in Virtual Switches
3-party or OpenSource vSwitch
•Distributed Virtual Switch
•Cisco Application Virtual Switch
•IBM DVS 5000V
•HP Virtual Switch 5900V
|Native Hyper-v Switching
|Linux Bridge(some distributions include OVS natively)
|OVS – open source project with multiple contributions from different vendors and individuals
As an IT Professional, whether you are running workloads on Red Hat KVM, Microsoft Hyper-V or VMware vSphere, it is difficult to imagine not having a choice of virtual networking. For many customers, this choice still means using the hypervisor’s native vSwitch. For others, it is about having an open source alternative, like OVS. And in many other cases, having the option of selecting an Enterprise-grade virtual switch has been key to increasing deployments of virtualization, since it enables consistent policies and network operations between virtual machines and bare metal workloads.
As can be seen in the table above, Cisco Nexus 1000V continues to be the industry’s only multi-hypervisor virtual switching solution that delivers enterprise class functionality and features across vSphere, Hyper-V and KVM. Currently, over 10,000 customers have selected this option with Cisco Nexus 1000V in either vSphere, Hyper-V, or KVM (or a combination of them).
Cisco is fully committed to the Nexus 1000V for vSphere, Hyper-V and KVM and also the Application Virtual Switch (AVS) for Application Centric Infrastructure (ACI), in addition to our open source contributions to OVS. Cisco has a large R&D investment in virtual switching, with a lot of talented engineers dedicated to this area, inclusive of those working on open-source contributions.
Nexus 1000V 3.0 release for vSphere is slated for August 2014 (general availability). This release addresses scale requirements of our increasing customer base, as well as an easy installation tool in the form of Cisco Virtual Switch Update Manager. The Cisco AVS for vSphere will bring the ACI policy framework to virtual servers. With ACI, customers will for the first time benefit from a true end-to-end virtual + physical infrastructure being managed holistically to provide visibility and optimal performance for heterogeneous hypervisors and workloads (virtual or physical). These innovations and choices are enabled by the availability of open choices in virtual switching within hypervisors.
As we look forward to VMworld next month, we are excited to continue the collaborative work with platform vendors VMware, Microsoft, Red Hat, Canonical, and the open source community to maintain and continue development of openness and choice for our customers. We are fully committed to this vision at Cisco.
Acknowledgement: Juan Lage (@juanlage) contributed to this blog.
Tags: application centric infrastructure, Application Virtual Switch, AVS, Canonical, KVM, Microsoft Hyper-V, Nexus1000V, open source, opendaylight, OpFlex, opflex protocol, OVS, RedHat, VMware vSphere, vmworld, vmworld 2014
Last week I spent some time at the “Software Defined Networking 2014” conference in London. It’s a relatively small conference I would say however given the growing interest in SDN and rapid progress of the technology it’s always good to hear alternative viewpoints and experiences. And I certainly found the previous conference here in December 2013 interesting – in particular one vendor in my view using SDN as the “hammer to crack a nut“.
Cisco wasn’t present at this conference last week, so what are others saying about SDN? Here is a quick summary of my takeaways (in some cases questions raised in my mind), which I will expand on below. And let me be controversial in my summary!
(1) Negligible discussion on live SDN deployments.
(2) NFV – at least for service providers – is potentially a quicker win than SDN
(3) SDN “Washing” is alive and well
(4) Is OpenFlow more of an academic pursuit?
(5) Open Daylight excitement
(6) Negligible Discussion on “Making It Happen”
As I say, to some my statements may be controversial – let me explain!
Read More »
Tags: application centric infrastructure, architecture, Cisco Services, network virtualization, software defined network
Among the top concerns for CIOs and VPs of infrastructure are making IT relevant to the business and driving revenue growth, reducing operational expenses while preserving innovation, and mitigating risk by meeting or exceeding security and compliance requirements. The Cisco Application Centric Infrastructure, or ACI, helps CIOs and VPs of infrastructure address these concerns directly. Check out my short video to find out more. Read More »
Tags: ACI, application centric infrastructure, CIO, CIO concerns, Cisco IT, cisco on cisco, coc-data-center, VP of Infrastructure, VP of Infrastructure concerns
The 25th anniversary of Cisco Live was an enormous hit, with record crowds at the Moscone Center in San Francisco. Every day I could feel the enthusiasm of Cisco customers and partners, and it was especially high in the World of Solutions Expo. That’s where I spent most of my time, on the Expo floor taking in all the technology displays, talking shop, learning, and sharing information with Cisco partners and customers. The key conference themes dominated our conversations – global Intercloud, collaboration, security, and, of course, Application Centric Infrastructure. Read More »
Tags: ACI, application centric infrastructure, Cisco IT, cisco live, coc-data-center, InterCloud, Partner Ecosystem
At the recent CiscoLive event in San Francisco, Soni Jiandani, Senior Vice President of Cisco INSBU, expanded on the industry momentum for Application Centric Infrastructure (ACI). She highlighted wide ranging customers and ecosystem partners that are discovering ACI’s architectural potential to drive enormous simplification of cloud and application delivery.
Now it’s possible to quantify ACI benefits in economic terms. IDC has just completed an in-depth analysis projecting ACI’s three year return in one of the largest data center environments in the world, Cisco’s own IT Elastic Infrastructure Services (CITEIS).
Cisco IT runs over 4000 applications, on both virtualized and bare-metal machines, stores 40 PB of data and inspects over 27 TB of traffic daily. CITEIS is a private cloud environment integrating ACI for policy driven network provisioning and operations for a variety of dynamic workloads.
IDC points out that Cisco IT’s decision to use its Cisco ACI technology “was not a foregone conclusion — Cisco’s IT team uses many technologies and solutions from other vendors” to meet its primary responsibilities of improving company-wide productivity, security and asset utilization while reducing the risk of business transitions over time. Now that “ACI testing and trial runs have been completed, the results yield detailed calculations of ACI’s impact on IT operations, including IT infrastructure spending, the efficiency of IT operations including application deployments, and the incidence of downtime.”
Specifically, IDC found “Automated provisioning in areas such as datacenter access (62.1% projected time savings), access control lists (53.0%), local server load balancing (55.5%), global server load balancing (72.4%), and fleet provisioning (58.0%) will be achieved through the creation and maintenance of provisioning templates.” Cumulatively, this results in a 41% savings on both Opex and Capex, using a conservative bottom-up approach. IDC also quantified (20%) downtime reduction and (45%) power and space savings. “IDC believes that the projections are well founded and that these benefits are of the type and scope that organizations can reasonably expect to attain by deploying a policy-based infrastructure solution. IDC conducted several interviews with IT managers and analyzed “Before” and “After” metrics for common provisioning tasks as well as Capex reductions due to ACI’s dynamic isolation capabilities within a shared production environment.
According to Rebecca Jacoby, SVP and CIO, Cisco, “ACI’s policy based architecture will bring the promise of infrastructure programmability to the masses. It makes every datacenter operator able to effectively create policies that can be used, reused, and deployed in a much simpler and more efficient manner — and use the staff that is currently spending all their time in running the network and the security protocols, to do much more strategic things.”
Download the IDC analysis here. And for a background of ACI’s architectural approach take a look at the white paper from Enterprise Strategy group.
Tags: ACI, ACI Economics, ACI TCO, application centric infrastructure, Business Value Brief, IDC