A long time ago, it used to be comforting, to hear the words “One Size Fits All”. As though our interests were surely represented within that catch-all, assuring us that we weren’t going to get left out in the rain. You could safely make that impulse-driven purchase, bring it home (or have it delivered), and know with certainty, that you wouldn’t be disappointed. It’s almost laughable to think that we subscribed to this way of thinking for about 50 years. But thankfully, we live, work and play in a world where it’s not about one-size-fits-all, and the only things we’ll accept as such, are wristwatches, and bicycle helmets! (unless you have a gargantuan sized cranium)
And so it is with your IT environment – “One-Size-Fits-All” feels too much like hand-cuffs (which coincidentally are also one-size-fits-all). We’ve done away with the notion that a solution that’s optimized for a Fortune 500, is going to be at all suitable for a medium-sized business with almost 1,000 employees. While both organizations might have a strategic imperative around workspace mobility, and have set out to virtualize the desktops of say, 5% of their workforce, they’ll approach this problem in two completely different ways.
- One of these organizations will have an extensive , multi-tiered networking and security infrastructure, optimized for virtual machine traffic, the other may not.
- One of these organizations will have a mature SAN infrastructure in place, with embedded resources and expertise, and lots of existing mission-critical data already housed there. The other may not.
- One of these organizations will have a high percentage of virtualized workloads and a highly automated/orchestrated environment for rapidly spinning up new infrastructure. The other may not.
Certainly these two environments are not going to take the same solution approach to deploying virtual desktops? They will however, share many of the same key objectives/demands: future proof scalability, resiliency, streamlined provisioning and operations, consistent user experience for the 1st user as well as the 1000th. And they’ll want all of this with the lowest possible TCO.
Last month, Cisco introduced our expanded suite of solution architectures for desktop virtualization. This portfolio was struck with the objective of ensuring our customers would never have to settle for a One-Size-Fits-All approach to deploying VDI, recognizing that they’re deploying this solution from a multitude of possible starting points in their IT maturity. With four new solution architectures, each built on Cisco Unified Computing System (UCS), and each backed by design guides and reference configurations co-developed with industry-leading partners in storage and storage-optimization technologies, we’ve taken the risk and guesswork out of choosing the deployment methodology that’s right-sized for your organization. Check out my friend Ashok’s more detailed post on the new reference architecture portfolio.
Read More »
Tags: citrix, desktop, UCS, vdi, virtualization, VMware
Our bags are packed and the demos are built, as Cisco heads out to Citrix Synergy LA 2013 in Anaheim next week. Synergy will be the inaugural event at the new Anaheim Convention Center, and Cisco a proud Platinum Sponsor , will be showing up in style, with a larger booth, 8 demo stations, a theater, and our Shindig Party.
Cisco continues to build its relationship with Citrix, and we’ll be expanding on the announcements made by Padma Warrior, Cisco CTO and Strategy Officer, during the Synergy Barcelona 2012 keynote, with booth demos of innovations in desktop virtualization, cloud networking, mobility, and cloud orchestration. In addition, we will provide visibility into Cisco and Citrix CVD roadmap for “Excalibur” and preview of Cisco Jabber integrated with Citrix XenMobile.
Cisco will be hosting two breakout sessions during Synergy and Summit:
Tags: Cisco, citrix, desktop virtualization, Synergy, vdi, xendesktop
It’s great to see Cisco and many companies across the industry make a major change in the use of Open Source via the newly form project hosted by the Linux Foundation called OpenDaylight. This consortium is an industry-wide, open and transparent effort to catalyze innovation and accelerate an application ecosystem for software-defined networking. With all the partners involved we are working to not only further development and adoption of SDN but also to foster a new developer community. A consortium like this has been long overdue and it’s great to finally see it come to fruition.
We are incredibly pleased to partner with Arista, Big Switch Networks, Brocade, Citrix, Dell, Ericsson, Fujitsu, HP, IBM, Intel, Juniper Networks, Microsoft, NEC, Nuage Networks, PLUMgrid, RedHat and VMware on the Project. This is the largest effort to date to drive Software-Defined Networking across the industry and into new markets. While the initial goal is to build a common, industry backed SDN Platform, the broader objective is to give rise to an entire ecosystem of developers that can freely utilize the code, contribute to the project and commercialize the offerings. I further expect the ecosystem to expand into areas like tools and services.
Cisco has donated our core “Cisco ONE” controller code to the project and has officially open sourced the code under the Eclipse Public License. The community has come together around this code to form the architecture (see below) for the Open SDN Framework. Beyond donations of code, Project members are supporting the project via both financial investment and via developers we are committing to work full-time on the project overall. Donations from other members of the Project can be seen here and we expect this list to only grow.
As Open Source increasingly becomes a standard for customers and developers, we look at this as a new way to meet our customer needs and also help developers innovate in new ways without the barriers of vendor lock-in. Open Source is increasingly important for our customers and developers as well and as they evolve, we evolve. Cisco to date has supported Open Source through efforts such as OpenStack and now OpenDaylight and we look at Open Source as a critical pillar in our software strategy moving forward. By allowing developers to freely use these solutions we hope to enable a new developer ecosystem for software-defined networking and more. We are fully committed to enabling developers, both current and new, to deliver innovating applications and services that will help customers across the board realize the value of SDN faster than before.
The OpenDaylight architecture and code offering to date includes a modular southbound plugin architecture for multi-vendor environments. In addition, OpenDaylight offers an extensible northbound framework with both Java & REST APIs to ensure multiple developer skill-sets can build applications to the platform. We are also planning to build a onePK plugin for OpenDaylight to enable multiple users to drive network intelligence into their SDN applications. As you can see from below we will also be supporting key standards with this effort, including OpenFlow.
It’s important to note that you don’t launch a community; you build one. By investing in OpenDaylight we hope that our customers, partners and developers across multiple industries will now have the ability to build applications that frankly make the network easier to use and more automated. As an industry we are moving in a new direction and further up the stack and OpenDaylight offers new opportunities for application creation and monetization beyond the networking layer.
It’s a true rarity when you see both partners and competitors come together for the good of the community, and contribute code for the universal good of the customer. All OpenDaylight participants have committed to open source guidelines that include open communication, ethical and honest behavior, code and roadmap transparency and more. An Open Source project is only as successful as the community of developers and the level of code quality, and OpenDaylight’s Board of Directors (which includes multiple parties cross-industry) will be ensuring that partners, code contributors and project committers all abide by the same guidelines for the success of the project over the success of their own company’s offerings.
For more information, please see www.opendaylight.org. Code will be available for download soon, and we are looking for interested individuals for commitments across the board – from technical offerings to application development, and we welcome contributions from both individuals and other organizations. All ideas are welcome, and we look forward to multiple new innovative solutions coming from this.
Congratulations to all our partners and individuals who helped to make this happen, including the hard work done by the Linux Foundation. It’s truly an amazing accomplishment and we expect to see much more in the near future.
Tags: arista, big switch networks, Brocade, Cisco SDN Controller, citrix, dell, ericsson, Fujitsu, HP, IBM, Intel, juniper, Microsoft, NEC, Nuage, open source, opendaylight, PLUMgrid, RedHat, SDN, VMware
MDM Today and the Future
Mobile devices have quickly become a mainstay in enterprise environments and continue to be consumer driven, and yet they find their way into our day-to-day business lives. As these new devices are being brought into the work environment by employees, enterprise IT is increasingly being forced to accommodate for business use. This is not new news. We observe this pattern through our customers today and live this phenomenon within our own everyday work environment at Cisco. Here at Cisco, employees have the flexibility to choose their device and to securely connect to voice, video and data services from anywhere under an Any Device policy. Cisco manages over 64,000 mobile devices today.
Read More »
Tags: AirWatch, byod, citrix, good, MDM, meraki, Mobile Device Management, mobile security, MobileIron, mobility, SAP Fiberlink, security
This was the test I most eagerly anticipated because of the lack of information on the web regarding running a Xeon-based system at a reduced memory speed. Here I am at Cisco, the company that produces one of the only blades in the industry capable of supporting both the top bin E5-2690 processor and 24 DIMMs (HP and Dell can’t say the same), yet I didn’t know the performance impact for using all 24 DIMM slots. Sure, technically I could tell you that the E5-26xx memory bus runs at 1600MHz at two DIMMs per channel (16 DIMMs) and a slower speed at three DIMMs per channel (24 DIMMs), but how does a change in MHz on a memory bus affect the entire system? Keep reading to find out.
Speaking of memory, don’t forget that this blog is just one in a series of blogs covering VDI:
The situation. As you can see in the 2-socket block diagram below, the E5-2600 family of processors has four memory channels and supports three DIMMs per channel. For a 2-socket blade, that’s 24 DIMMs. That’s a lot of DIMMs. If you populate either 8 or 16 DIMMs (1 or 2 DIMMs per channel), the memory bus runs at the full 1600MHz (when using the appropriately rated DIMMs). But when you add a third DIMM to each channel (for 24 DIMMs), the bus slows down. When we performed this testing, going from 16 to 24 DIMMs slowed the entire memory bus to 1066MHz, so that’s what you’ll see in the results. Cisco has since qualified running the memory bus at 1333MHz in UCSM maintenance releases 2.0(5a) and 2.1(1b), so running updated UCSM firmware should yield even better results than we saw in our testing.
As we’ve done in all of our tests, we looked at two different blades with two very different processors. Let’s start with the results for the E5-2665 processor. The following graph summarizes the results from four different test runs. Let’s focus on the blue lines. We tested 1vCPU virtual desktops with the memory bus running at 1600MHz (the solid blue line) and 1066MHz (the dotted blue line). The test at 1600MHz achieved greater density, but only 4% greater density. That is effectively negligible considering that the load is random in these tests. LoginVSI is designed to randomize the load.
Read More »
Tags: citrix, cpu, UCS, vdi, virtual desktop, virtualization, VMware, vxi