An Idea for vCloud Director and View

Sometimes I am sitting up late at night and I have a thought of something I think would be cool, like if x and y worked together to get z. This time I thought this was good enough to blog about. Now I want to stress that I do not have any special insight into what is coming. This is just how I wish things would be.

Today there are two end user portals from VMware. The vCloud Director for self-service cloud interface and the View Manager access point for end-users to access Virtual Desktops. Each interface interacts with one or more vCenter instances to deploy, manage, and destroy virtual machines. Below is a way over simplified representation of how View, vCloud Director (plus Request Manager) relate to the user experience. I think maybe there is a divide when there does not need to be (someday).

 

 

My idea

What if vCloud director could be used in the future to be the one stop user interface portal. Leveraging vCloud Request Manager, vCD could deploy cloud resources, Desktops or Servers or both. vCloud Director would be the orchestration piece for VMware View. Once the Request for a desktop is approved the entitlement to the correct pool is automatically given. If extra desktops are needed the cloning begins. vCloud Director will learn to speak the View Composer’s language, providing the ever elusive ability to use linked clones with vCD. vCloud Director with this feature could be great for lab and test/dev environments. The best part is operationally there is one place to request, deploy, manage all virtual resources from the end-user perspective. This could eliminate the ambiguity for a user (and service providers) on how to consume (and deliver) resources. This has implications on how IaaS and DaaS would be architected.

 

Now some drawbacks

You might say, hey, Jon you are going to make me buy and run vCD just to get VDI? No. The beauty of the API’s is each product could stand alone or work together (in my Vision of how they should work). Maybe even leverage Composer with vCD without View or Request Manager with View without vCD.

One Cloud Portal to rule them all.

5 Replies to “An Idea for vCloud Director and View”

  1. This is already being done by third parties such as DynamicOps and Dell also uses that technology in its VIS Self-Service Creator offering. The advantage of 3rd party tools is they also do more than just VMware, so you can incorporate Citrix, or Microsoft components into the workflow.

    1. That sound like a lot of deployment tools which I may or may not want to leverage. I am thinking of a single interface for users. That may not be what I want for the technical staff. I do admit I need to learn a lot more about Dynamic ops though.

  2. Makes sense to me, and I’m not a “V” guy. The more I dig into this tech, the more I see it fragmented in regards to “I go to play X to get A and place Y to get B.” This would really help from the “novice” end as well.

Leave a Reply

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