vc:distributedvirtualportgroup not being listed

[Beansley]

Hello,

I'm just getting started with Orchestrator (after battling royally with LDAP configuration), and I'm having issues with the simplest of workflows, the included Create Simple Virtual Machine.  I followed someone's advice and changed the type property of the Connect to Network attribute to vc:distributedvirtualportgroup (after duplicating and moving the original workflow), as well as switching the presentation property to "Tree".  I'm still not seeing the Tree view, nor am I able to bring up any of the port groups from my vCenter (the Choose has a "Nothing found" green box).  Its unclear how to troubleshoot - not sure where any logs might be located.  I attempted to bypass the issue by switching the properties of that attribute to Not Mandatory, but a test run of the workflow bombs because of that (or so it seems).  I also change the property of the duplicate workflow to mark the workflow as failed vs. the default of maintain state (or whatever that default is) upon client restart.

Any guidance is greatly appreciated.

Dave

[Burke-]

Are you able to select other complex objects for inputs? IE: Is the vCenter plug-in working properly. To confirm, please Go to the bottom left corner of the vCO CLient and open Inventory. Find your green vCenter icon and expand that out.. if the plug-in is properly configured (SSL cert imported, appropriate credentials provided), then you should be able to expand out a nice tree of your vCenter resources.

[Beansley]

Yes, the tree view is working as advertised when selecting resource pools, hosts, and datastores.  Just can't get the dvswitch piece working. The log returns "TypeError:Cannot read property "name" from null (Dynamic Script Module name: createVirtualEthernetCarNetworkConfigSpec#7)

[Burke- · Accepted solution]

Hmm.. I just brought up one of my library vCO servers running 4.2.0 and duplicated the "Create simple virtual machine" workflow to "Custom Create simple virtual machine".

After duplicating, I went to the inputs and changed the "Type" of the vmNetwork input to be "VC:DistributedVirtualPortgroup" as you have described. There are other changes that will be required within the workflow in order for it to be successful, but I saved at this point and ran the workflow.

When I ran the workflow, I clicked on "Not set" for the "The network to connect to" input. The Chooser came up empty so I hit <ENTER> in the Filter box to have it show all, and it did....

Perhaps it has to do with your plug-in version? What version vCO and vCenter plug-in versions are you using? There is another thread discussing issues when using an updated vCenter plug-in with older versions of vCenter that may not have the inventory service running...

[Beansley]

Its finally working.  I guess it was closing out the client then getting back in.  I could have sworn I tried that once or twice previously.

One thing I've noticed is there doesn't seem to be any filtering in the workflow itself - I'd like to see some logic that after one selects a host the Tree View will only show those inventory items relavent to that selection.  For instance, I've made my host selection, the next select dialogs show only the datastores that host is connected, or only those dvSwitch port groups the host has been added to.  Is that going to require some advanced fuctionality / scripting?

Thanks for your help, Sir.  I will assign points

Dave

[Burke-]

You can do that kind of logic within the presentation - Create an action that takes the previously selected object (host) as an input and have the action return an array of the desired objects (IE: VC:Datastore).... actually, if you take a look at the Presentation settings for the Datastore input, you'll see there is already something that does this - it uses the VC:Host + VC:ResourcePool values you specified to provide a list of valid datastores...

[Beansley]

Yeah, I noticed the datastore piece a little after I posted my last, got locked up trying to edit it.  I was quite happy to see it.

Thanks again!