In this article I wrote a couple of months ago, one of VMware’s current goals is to become global market leader in Virtual Desktop Infrastructures (VDI). The Horizon Suite has evolved from just a virtual desktop to a complete End User Computing Experience with support for both the VDI as well as the local desktop. Numbers from 2013 show that VMware has a marketshare of approximately 40%, the same as Citrix.

So to become primary market leader in EUC, VMware needed to do something. Come up with a new unique selling point to create that bigger market share.

In august 2014, VMware acquired CloudVolumes. In my honest opinion, one of the best moves ever.

 

 CloudVolumes_Logo

 

 

 

 

 

CloudVolumes is the name of the company ánd the solution they built aimed on rapid deployments of apps, changes, user data, etc. And how it works (better yet, how fast it works), is absolutely astonishing. To make it a more VMware branded product, it has been rebranded to AppVolumes.

The process of creating an Application Volume is similar to creating a Virtualized Application:

 

1.You have a clean desktop

2.Start a recording for a new Application Volume

3.Install the solution

4.Customize the solution

5.Finish the recording

 

The Application Volume is stored in a vmdk, which can be attached to a VM by the AppVolumes agent.

AppVolumes_overview

 

 

 

 

 

 

 

 

 

 

But why use AppVolumes instead of Application Virtualization? Well, it’s not a replacement. It’s a great addition to Application Virtualization.

On one of my current projects, a View migration to Horizon 6, the customer has approximately 800 different applications. On their current VDI, only a small amount of these applications are being used. There is a variation of reasons for this, but the most important one is that most of the applications are legacy, financial applications. They are quite hard to virtualize. To migrate the users that use these applications to the VDI, a lot more different golden images must be used and that would be a challenge to manage.

 

So imagine being able to create Application Volume which contains these legacy applications grouped by department or team. A user logs onto a Virtual Desktop, the applications are attached to the VM and Bob’s your uncle! And your nice and shiny Virtualized Applications could run alongside these Application Volumes.

 

AppVolumes can create 2 different Application Volumes: read-only and writeable volumes.

In the above case of users needing applications on a Virtual Desktop, a read-only volume is ideal. Whenever a user needs to save application or user settings, they can be stored in the profile with Persona Management or on a persistent disk.

Another option is to save these settings to a separate Writable Volume. It detaches when a user logs off and attaches again to a new desktop when the user logs on. Really cool, if you ask me.

 

But what makes it really awesome, is the ability to create Writable Application Volumes.

Let’s say you have developers who need to install their own applications. That’s going to be challenging on a linked clone. And you want to avoid full clones as much as you can. Also, you want your pools to be floating as much as possible. So how would AppVolumes fit in?

Just deploy a Writable Application Volume to the user. When he/she logs on, the volume is presented to the VM as an overlay. The user can install the applications to the volume and when the user logs off, the vmdk is saved and ready to be attached when the user logs on to a different desktop.

 

The project I was telling about has about 300 users that have a dedicated VM that has their applications installed. Basically like a second workstation used for development/test/acceptance. IT had big challenges to migrate these VM’s to  managed-floating-linked clones. I’m guessing the challenges are over..

 

Another use case could be the deployment of serverside applications like Apache, MySQL, PHP and frameworks like WordPress or Joomla. The server could be a standard deployed VM, customized by a Customization Specification. And the needed applications are just as easily deployed by AppVolumes. Without any configuration.

AppVolumes_ServerApps

 

On VMworld 2014 in Barcelona I have seen the current version (CloudVolumes branded) in action and I’m still impressed. So to answer the question on how VMware is going to be primary market leader in EUC, here’s the answer: AppVolumes. The amount of use cases is vast. The expectation is that AppVolumes will be ready to ship somewhere in Q4. So let’s hope Christmas will be early this year.

CloudVolumes_live

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Johan van Amersfoort

Author Johan van Amersfoort

Since 1999 I am part of the IT world. The first few years as a field engineer working with SBC products like WinFrame and MetaFrame and later with TS/RDS based solutions. In 2005 I had my first experience with VMware products and since then I got hooked. Especially when I saw my first vMotion :) Late 2013, it was time to make a career change. But what? Actually, it was kind-of easy. Mix Server Virtualization with SBC and Application Virtualization and what do you get? The answer is simple, End-User Computing. I applied for a job at ITQ as a Virtualization Consultant, got hired and took my career to a next level. The 3 year after that were a rollercoaster. vExpert since 2015, VCIX/VCAP's (5/6) on Data Center and Desktop & Mobility, VMware EUC Champion awards and I achieved my ultimate goal: VCDX-DTM. As EUC is going through a revolution with a lot of new tech that makes it more agile, robust, scalable, secure, manageable and pretty awesome, my main focus is on EUC. But with a passion for technology, I won't hesitate if any other cool project comes by. If you like to read more about me, you can do so on my personal blog vHojan.nl

More posts by Johan van Amersfoort
21 October 2014

Leave a Reply