VMRC and vCO provisioned VMs

[Manupa]

Hi all,

vCac is working so far without any problems and is provisioning with our own vco workflows as expected.

but it seems the the vmrc feature is not for use with virtual machines of type vc:virtualmachine, I think this is a cool and usefull feature, but is it only for vcac provisioned vms?

Do I need to convert my virtualmachine at the end of my workflow to vcac:virtualmachine?

thanks in advance

[jddias]

VMRC is actually a feature of vSphere, it is simply exposed in vCAC for convenience. 

[Manupa]

hi,

i know, but when vmware implemented this feature in vcac it can only be used for vms which are provsioned from built in blueptints and not by those which are self made in asd...

[jddias]

I see, I didn't realize you were creating new VMs through ASD - interesting.

You could possibly create your own ASD action for those VMs using the following information - http://www.virtuallyghetto.com/2011/10/how-to-generate-vm-remote-console-url.html

[qc4vmware]

There is a lot of disconnect going on in this release Manupa.  It would be great if either a custom resource of type VC:VirtualMachine got a bit of special treatment like its cousin the vCAC:VirtualMachine of type vSphere OR we could kick off a workflow action at the end to pull it in as a vCAC:VirtualMachine instead of ending up a custom resource type.  Unfortunately neither of these things happen.  In another post in this forum I have suggested that they allow for a custom action type which allows us to create a url which ends up being a hyper link which is what we really need for the example jddias has pointed you to to be useful.  We're doing something similar where we want to give our users access to performance data about a vm and we construct the link to the webclient over view page for that vm then email the link to them.  Crude but workable.  As part of this process we also give the owner read only access within vCenter as part of the provisioned vm call out.  It would be awesome if instead of generating an email that custom action just launched the web page.  I think this type of extensibility is very simple yet powerful.  It would allow for a link to the vmrc to just get launched but in the mean time you might have to email them or publish it somehow outside of vCAC. 

One more warning for you with advanced services that provision something.  There is no way to remove those items currently so if you are even playing around with this feature be prepared for your inventory to get soiled with a bunch of stuff you can't clean up.