myEUC.net

EUC in general

VMware acquisition of CloudVolumes, where to go from here…

So, VMworld is behind us. What a whirlwind week. A lot of attendees this year, great turn-out. It’s impressive, even after 5 years to see so many people (22,000+) coming to talk about Virtualization and enjoying themselves, day and night, for 4 straight days (in some cases a few more days than that…).

I wanted to take a few minutes to talk do a quick summary of the CloudVolumes acquisition that VMware announced a few days ago. Kit Colbert made an interesting article about it, you can find it here.

CV logo

I was truly happy with this acquisition. I think it’s a perfect addition to the VMware EUC portfolio and it will definitely be interesting to see how they integrate it with the other products.

It’s important to distinguish VMware Mirage and CloudVolumes. Sanjay Poonen made this statement in a Brian Madden interview: “while the concept of the layers is similar in some ways between Mirage and CloudVolumes, the two products are actually quite different. Mirage was built for physical machines that are loosely connected which receive their layers via the network and the WAN, wheres CloudVolumes is built for always-connected clients which want to mount their layers from a fast reliable location.”, full info here.

For me, that’s the main take-away, you definitely want Real-Time delivery of applications, every person in IT that I know wants this for his users and for himself.

You want to make sure you don’t have to do any fancy packaging. You want to avoid any sort of funky modifications to the app that might impact stability and reliability. You want, whenever possible, to avoid streaming of applications, for desktops that have constant connectivity to the network. Last but not least, you want it now, not in x amount of seconds/minutes.

CloudVolumes virtually sits between the OS and the Application Layers, if that makes any sense.

CloudVolumes stack

 

Being able to have an abstraction layer between the OS and the Applications/Middleware is a major benefit. It remove most of the integration headaches and opens a world of new possibilities.

I know that the VMware EUC team are hard at work, there is still integration to do in the near future but it’s a very exciting time to be at VMware or work with VMware technologies.

There are so many new scenarios that might be possible, think about the possibility of combining this with vCloud Air (formely known as vCHS). You obtain a leaner machine, a lot less applications are part of the core OS, you can now have Desktops in your Datacenter that are identical to the desktop in your Cloud and you add the applications, after the fact. You add them based on profile of the user, when he or she logs in. Easier maintenance of the OS, easier maintenance of the applications, a lot more versatility to go from the DataCenter to the Cloud and Vice-versa.

Think of using this in a Disaster Recovery scenario as well. A user working in site A, loses his machine (physical or Virtual). You don’t have to prep a cold site with a lot of Virtual Desktops pre-configured, you just have generic desktops and the CloudVolumes agent waiting for that user to login to the DR site and continue his work. How many hours of effort saved?

What about Project Fargo. So much potential to combine both solutions. Chris Wolf talked about this on his blog, more info here.

Again, just scratching the surface here but I know that there will be a lot more coming in the near future and I’m super excited to work with people at VMware that will make that happen!

More information here: http://cloudvolumes.com/technology/

Good videos here: http://vimeo.com/cloudvolumes

 

Tagged , , , , , ,

Leave a reply

Your email address will not be published. Required fields are marked *

*