VMware Aria Automation Orchestrator

Hi SteskaljGE,

the only way to do that is with "Add a vCenter Server instance" / "Remove a vCenter Server instance". This will create/remove a new object

Thanks,

Stefan G.

Is there any way to create a temporary vcplugin instance? What I mean is that we use configuration data to do IaC and we do not want to add items to the plugin inventory. The only thing I can find is to VCPlugin.registerVCenterServerInstance and unregisterVCenterServerInstance. This still creates a plugin inventory object and is slow. 

Hi ririmia,

unfortunately there is no way to check on that.

KR,

Stefan G.

Hi Stefan,

Thanks for your feedback! I have two more questions:

We set the '2000' value for 'com.vmware.vmo.plugin.vi4.cache.main.max.size.mb' properties. How can we check the current cache status (size\in use)?
How can we check the plugin cache eviction in vRO v8.8.1?

Thanks!

Hi ririmia,

we have these properties for fine tuning:

• com.vmware.vmo.plugin.vi4.cache.main.expirationSeconds - default value: 14400 seconds
• com.vmware.vmo.plugin.vi4.cache.live.objects.expirationSeconds - default value: 14400 seconds
• com.vmware.vmo.plugin.vi4.cache.clearOnSessionRefresh - default value: false
• com.vmware.vmo.plugin.vi4.cache.main.max.size.mb - default value: 100
• com.vmware.vmo.plugin.vi4.list.unusable.sdkConnections - default value: true

Thanks,

Stefan G.

Hello,

There are available any system properties to control lifetimes / caches in the latest v7 vCenter plug-in like it was in 6.5?

Like 'com.vmware.vmo.plugin.vi4.cache.main.max.size.mb' ?

We have to vRO 8.8.1 installed and connected to 4 vCenters with almost 10.000 VMs. We have some performance issues and we want to "play" with these cache properties for improve the performance.

Thanks.

Hi Stefan,

Thanks a lot for your reply.

In the meantime, I also found this site for more explanation

https://vdc-repo.vmware.com/vmwb-repository/dcr-public/fe08899f-1eec-4d8d-b3bc-a6664c168c2c/7fdf97a1-4c0d-4be0-9d43-2ceebbc174d9/doc/vim.UserDirectory.html#retrieveUserGroups

Again thanks !

Hi j_brison,

the UserDirectory object has not been changed. The documentation for the retrieveUserGroups() method is as follows:

public UserSearchResult[] retrieveUserGroups(
        @optional
        String domain,
        String searchStr, 
        @optional
        String belongsToGroup,
        @optional
        String belongsToUser,
        boolean exactMatch,
        boolean findUsers,
        boolean findGroups)
        throws com.vmware.vim.binding.vim.fault.NotFound;

Hi,

Is the userDirectory object updated in this version more specifically the retrieveUserGroups method.

For the moment the documented parameters in the API Explorer are listed as follow :

Name Type Description

I still can't figure how to use it (and if it's possible to retrieve all the users of the SSO Domain).

Thanks in advance !

Hi o2teamnrb,

we have uploaded a new release of the plugin that resolves this issue. Please update the plugin, try it out and let us know in the comments if this resolved the issue.

KR,

Stefan G.

We are using the following Product Version: vRealize Orchestrator (vRO) v7.6

Current Builds:

External: 19258423

Embedded: 19220215

When I try to parse an OVF Descriptor using the following code:

1. var objMimeAttachment = objResourceElement.getContentAsMimeAttachment();
2.  
3. var strOVFDescriptor = objMimeAttachment.content;
4.  
5. var arrVcSdkConnection = VcPlugin.allSdkConnections;
6.  
7. var objVcOvfManager = null;
8.  
9. for each ( var objVcSdkConnection in arrVcSdkConnection )
10. {
11.     objVcOvfManager = objVcSdkConnection.ovfManager;
12.  
13.     if ( objVcOvfManager != null )
14.     {
15.         break;
16.     }
17. }
18.  
19. var objVcOvfParseDescriptorParams = new VcOvfParseDescriptorParams();
20.     objVcOvfParseDescriptorParams.locale = '';
21.     objVcOvfParseDescriptorParams.deploymentOption = '';
22.  
23. var objVcOvfParseDescriptorResult = objVcOvfManager.parseDescriptor(strOVFDescriptor, objVcOvfParseDescriptorParams);      <-- Error Occurs when running this line of code.

I get the following error:

Error in (Workflow:Test OVF / OIVF Issue (item1)#22) java.lang.NullPointerException

Workflow execution stack:

***

item: 'Test OVF/item1', state: 'failed', business state: 'null', exception: 'java.lang.NullPointerException (Workflow:Test OVF / OIVF Issue (item1)#22)'

workflow: 'Test OVF' (18d228da-1bd8-4753-8994-bc2a688ac22a)

|  'attribute': name=objResourceElement type=ResourceElement value=dunes://service.dunes.ch/ResourceElement?id='2ad741d7-7f54-4ee5-ac8d-57ce188d6a4a'&dunesName='ResourceElement'

|  'no inputs'

|  'no outputs'

*** End of execution stack.

I cannot confirm that. The plugin in marketplace supports vSphere 6.7 and vSphere 7.0.1 but not other versions. and API level is 6.5 (these numbers in the version of the plugin show what is supported version of vSphere API).
For any newer version of vSphere if you are not on latest vRO you should use the plugin from  this page.

Hi ivand

No worries, thanks for your reply! Can you confirm the plugin works with vSphere 7.0+? Only vSphere 6.7 is mentioned in the marketplace offering.

Cheers

I apologize for late response

Marketplace is the official placeholder for plugin updates. We are using this page to provide hot patches of the plugin for a faster spread of it. And to preview a new versions. Every preview of the plugin we support as an official build. You can use it in prod and raise support request on issues found.

Any feedback on this?

Hi ivand

Thanks for your reply. As you mentioned 2 times "this", let me rephrase to make sure I understand it correctly.

Here we get only technical previews: https://communities.vmware.com/t5/vRealize-Orchestrator-Documents/vRO-vCenter-Server-plug-in-for-vSphere-7-0-service-releases/tac-p/2877498

Here are the production ready binaries:
https://marketplace.cloud.vmware.com/services/details/vsphere-vcenter-server-plug-in-for-vrealize-orchestrator01?slug=true

Now on the second link (production ready) there is no mentioning of vSphere 7 and the plugin name is also named 6.5. Neither is there a proper version history.

Does the 6.5 production ready plugin support vSphere 7? I have a customer which will upgrade  to vSphere 7 and I want to update the (vRO 7.6) vSphere Plugin.

Thanks

 This page is only for technical previews of the plugin. This binaries are ready for production and usually released through vRO releases.

Is this plugin now still in review or officially released (title states technical preview)?

Why are you referring under this link to an older version of the plugin?https://marketplace.cloud.vmware.com/services/details/vsphere-vcenter-server-plug-in-for-vrealize-orchestrator01?slug=true

This situation creates a lot of confusion. Thanks for a feedback.

Hi . Can you try the newest version of the plug-in? (built 2021-10-05)

Version 7.0.0-18362600 (built 2021-07-22)

• Fix regression in getRelocateSpec action (minor)

Above error re-surfaced again in latest plugin (7.0.0-18421354 and 7.0.0-18687140)

I am using VRO 8.6 with vCenter 6.7, downgrade to 7.0.0-18362600 fixed the issue.

 we rely on backward compatibility of the vCenter API so the plugin itself should be as backward compatible as vCenter 6.7.0.46000 and 7.0.2-17958471 are supported by the plugin

You can still manually update the plugin.

It didn't make it It will be available in 8.6.1

 Thanks for the clarification, i misunderstood your post a bit

 Thanks for the update, I can confirm that it resolved all problems for me. Is this version also included in VRO 8.6 Release?

Nice development

I am running vro 7.6, and 2 vcenters, 1 has been upgraded to 7.0.2-17958471.  The other is still at 6.7.0.46000.  The current plug-in i have for vcenter is 6.5.0.12799420 (which works fine with my 6.7 vcenter but of course not my 7.0.2 vcenter).

Can anyone confirm if this version of the plugin Version 7.0.0-18687140 (build 2021-09-26) works with both vcenter versions 7.0.2-17958471 and 6.7.0.46000.

Thank you

This problem is fixed with the build 7.0.0-18687140

Yes, I posted the code in my comment above... it is not the same code as  has in the original post.

 - We are also affected by this folder issue -> did you find a working workaround code? It seems that is missing from your post.

In general: Is there any progress being made on this topic? Any ETA on a fix? 

I was hoping this would be fixed with vRealize Orchestrator Release 8.5.1 but nothing yet

This does seem like it is a bug.  I go about achieving the same sort of find but use another method.  Here is some code I think you can drop into the action to test out.  I think I've seen some similar weirdness in  the past when cycling through arrays of objects.  In this case vc:vmFolder is probably an extension of vc:Folder and maybe something weird is going on when the object is being converted.  I'd report this bug as it is easily reproduced.  Here is some alternate code that doesn't seem to break:

var datacenter = System.getModule("com.vmware.library.vc.basic").getDatacenterForVimObject(anyVcenterObject);
var parent = datacenter.parent;
var dcPath = "";

while (parent && parent.parent) {
System.debug(parent.name + ": " + System.getObjectType(parent));
dcPath = parent.name + "/" + dcPath;
parent = parent.parent;
}

System.debug("dcPath; " + dcPath);
System.debug("Query for folder in datacenter: " + datacenter.name);
System.debug(System.getObjectType(datacenter.parent));
var index = anyVcenterObject.vimHost.searchIndex;

// Inventory path of the folder to search for (note: starts with datacenter name and folder if datacenter is in a folder)
// root folder is always named Datacenters and if included in query it will not work sor check for that too!
var invPath = dcPath + datacenter.name + "/vm/" + folderName;
System.debug("Query index for path: " + invPath);

var folder = index.findByInventoryPath(invPath);

Thanks ! We did restart Orchestrator a bunch of times, and I confirmed the account isn't locked out and has proper privileges. We didn't try re-adding VCs though.

I didn't write this action, so I'm not to blame if it's all kinds of screwy or doesn't make sense. I believe it takes a string representation of a VM Folder, then finds the object and assigns it out. So, this same action has existed since our Orchestrator 5.5 days, and I'm actually surprised a lot of this stuff still works today.

This is getNamedVmFolder:

 Can you post your code or if its a canned action or workflow which are you running?  I can try to reproduce this with the latest plugin.  Also, in the past I've sometimes needed to remove / re-add a vc.  Double check account used to connect and access within the vc.

I was able to find 6.5.0-16904859 on a test vRO instance I had forgotten about. Seems to be working better than 7.0.0-18421354.

I ran into issues with the latter version when runnning a custom action. I'll need to dig much deeper into what this error means, but it looks to be something to do with Folder conversion to a ManagedObject or something like that. Once I reverted to the former build, then things were working fine.

FWIW, I am running Orchestrator 7.6.0.317 Build 13020602

is it possible to download older versions of this plugin? where do i find them? I'm looking for 6.5.0-16904859.

The link provided here doesn't work anymore

https://communities.vmware.com/t5/vRealize-Orchestrator/Adding-vCenter-7-0-1-to-VRO-7-6/m-p/2822334/highlight/true#M24999

We are running vCenter 7.0.2  (Build 17958471) with vRO 8.5.0 (before it was 8.4.0) when I register the vCenter orchestrator as a vCenter Server extension (7.0.0.18421354) in the VC plugin's we see a error for vRealize Orchestrator 8.3.0.0 incompatible (the plug-in supports only vsphere web client (flash)). 

i am lost now on how to get this working. 

Unfortunately it is not possible to have two binaries  attached. We are working on publishing the latest 6.5 version in marketplace. This version has been verified on vRO 7.5. vRO 7.3 is EOL.

Could the latest 6.5 build be left attached to this page (As the 6.5 builds have worked with vRO back to 7.3 version) ?

Does Version 7.0.0-18048864 (built 2021-05-19) work on vRO 7.3?

The plugin in version 6.5.0.16904859 allows vRO 7.6 to connect with vCenter 7.0, at least up until verison 7.0.1 build-16858589, which was what I could test with.

Better documentation is definetly the thing needed here, how is anyone supposed to know this can work with the inconsistent versioning and lack of documentation updates??

to allow connection to vCenter 7.0 an Upgrade to vRO 8.3 worked for me. 

Plugin Version: 6.5.0.17494695

I had to re-register Vcenter as Authentication Provider

Has there been an update to allow connection to vCenter 7.0 ? I keep getting the following error connecting to a 7.0 vCenter:

unusable: java.lang.RuntimeException: Incorrect type of token class com.vmware.o11n.security.auth.sso.oauth.ExtendedOAuthToken. Please ensure vRO is configured with vSphere authentication

I think I was the one who pointed you here and I believe the fix was applied here:

Version 6.5.0-15225986 (built 2019-12-03)

• Compatibility with vSphere 6.7u3 API

I can confirm it works... no need to be skeptical.  

So which one of these allows VCO7.6 to support connections to vCenter 7.0? I was told that 6.5.0-16904859 does the trick, but I'm skeptical given that none of its bullet points explicitly call this out.

I think you're confusing this plugin with another one. This plugin is only for vro and allows you to add a vcenter to vro. It does not expose vro in vcenter to run workflows within vcenter. You might be looking for one of these:

Technical Preview of Orchestrator plug-in for vSphere Web Client

or for the html5 client in 6.7:

vRealize Orchestrator Plug-in for vSphere Client - Beta

for two hours I tried to register and... see this &%ç*"%*ç plugin in my vsphere client (flex) version 6.5 U2 from an vRO 8.1.... NO chance,... nothing

I downloaded/uploaded it to data/usr/lib/vco/downloads, check the chmod.... then try to register vco as extension (what is the "External address to advertise this Orchestrator." I have no F***** idea :smileyhappy:) I tried with the fqdn of my vRO server, with port, without port, without putting ANY external adresses.... Try to restart the vRO appliance, my vcsa,... both,.... NOTHING HAPPEND!!!!! it didn't download this plugin to /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity .... close to uninstall it and try to find another "orchestrator software....

so if someone has a "GOOD" documentation step-by-step to register this extension and get this plugin inside flexclient work.... you will become my best friend....

Just to verify, this is compatible with vRA 7.5 / vRO 7.5?  And how come none of the plugins show up on the compatibility matrix?

VMware Compatibility Guide - vco

Thank you, I was able to download.

It is here. Had some issues uploading the file.

Maybe I'm missing something, but where is the actual site for Plugin-Download?

Hi Boda201110141,

Have you found a way to implement the vbs flag througth an orchestrator workflow?

The only way I found was to use powershell, I also had to create a module to execute the powershell remotely to avoid kerberos duble hop, sinceI also need to copy windows patches from our share to the vms, you can check it here: https://communities.vmware.com/thread/634794

Can you please share if you found a way of setting the option directly througth an workflow.

Thanks.

Hi,

If I'm not mistaken, 'vbsEnabled' property was added in vSphere 6.7 API, but vRO vCenter plug-in is built against vSphere 6.5 API level, which means it doesn't support the features that came with API version 6.7. So you have to wait until there is an updated  plug-in supporting API version 6.7.

Hey all,

anyone able to set the VBS option for VMs?

Still missing the "configSpec.flags.vbsEnabled" option.

Thanks in advance

Hello islavov,

Is it possible to have release dates of vCenter plug-in we can see on this page?

Thanks in advance :smileywink:

Absolutely brilliant.  It corrected the issue.  Thank you so much!!! 

to upgrade the plugin

download the plugin and unzip it

you need to go to your vRealize orchestrator control center

URL is https://orchestratorservername.domain.net:8283/vco-controlcenter

login as root

click manage plugins

browse to the plugin you downloaded and unzipped

and click upload

wait for the services to restart

you should have installed a proxy agent on one of the IIS servers - Install the vSphere Agent

the endpoint name you set in procedure above need to match the endpoint name you specify if using vRA either vCenter or the vCenter hostname generally.

you can then run a orchestrator workflow to connect to vSphere

vco > workflows > library > vCenter > configuration > Add a vCenter Server Instance (generally select no for the session question).

vco > workflows > library > vCenter > configuration > Register vCenter Orchestrator as a vCenter Server extension

you should then be able to see the connection in:

vco > inventory > vSphere vCenter Plug-in

I have the same issue.  I have been trying, for the past 2 days, to find a resolution.  When you say that you upgraded to version 6.5.0-14070225, what exactly did you upgrade and how?  Thanks!!

VCSA 6.7u2
vRA/vRO 7.5

vROps 7.0.0

I tried to configure vRA/vRO 7.5 with VCSA 6.7 U2 and I got this error "com.vmware.vim.vmomi.core.exception.UnmarshallException: Type 'ServiceContent' contains unrecognized property 'storageQueryManager'". When I updated to version 6.5.0-14070255 just worked. Thank you!

Hi

I have cloud foundation which has been upgraded to 3.7.2

I have used this to deploy vRealize Automation in its load balanced manner successfully.

vRA is 7.5 and vCenter Server 6.7 Update 2a

However using the catalogue to do the initial setup to deploy the vCenter vRealize Orchestration Plugin.

I have tried replacing the vro-plugin.zip with both the o11nplugin-vsphere-6.5.0-13863019.vmoapp.zip and vco-plugin-7.4.0.13701555 in /usr/lib/vro/downloads by stopping the vro-service service replacing and renaming the zip with permission/owners and starting the vro-server.

Then tried doing the initial setup but it still fails with the error:

(unusable: com.vmware.vim.vmomi.client.exception.VmomiProtocolException: com.vmware.vim.vmomi.core.exception.UnmarshallException: Type 'ServiceContent' contains unrecognized property 'siteInfoManager')

Hi

I have cloud foundation which has been upgraded to 3.7.2

I have used this to deploy vRealize Automation in its load balanced manner successfully.

vRA is 7.5 and vCenter Server 6.7 Update 2a

However using the catalogue to do the initial setup to deploy the vCenter vRealize Orchestration Plugin.

I have tried replacing the vro-plugin.zip with both the o11nplugin-vsphere-6.5.0-13863019.vmoapp.zip and vco-plugin-7.4.0.13701555 in /usr/lib/vro/downloads by stopping the vro-service service replacing and renaming the zip with permission/owners and starting the vro-server.

Then tried doing the initial setup but it still fails with the error:

(unusable: com.vmware.vim.vmomi.client.exception.VmomiProtocolException: com.vmware.vim.vmomi.core.exception.UnmarshallException: Type 'ServiceContent' contains unrecognized property 'siteInfoManager')

Yes, just used it to connect with vCenter 6.7u2a.

We are running vRO 7.4 and connecting to vCenter 6.7 update 2, is this plugin compatible vCenter 6.7's?

VMC customers with vRA/vRO 7.3 - 7.5 should use plugin #10376265 or newer

Hi, i have vRO 7.3.1 and imported some workflows from a 7.2 installation i have. The vCenter i have is 6.5 U2 6.5.0.20000 Build 9451637  and current vCenter plugin is VC 6.5.0.7720419. I notice some odd behaviours, just not all the time or not against all VMs, for example, if i try to run action to getVmGuestFamily i get a Timeout waiting for getting VM Guest Family on a running OS for a particular VM, but not all. I thought it was a problem with the VM but it shows running VMtools and is started. Also i see odd behaviour when for example quering VMtools state.  Do you know if there is any documented issue with vRO 7.3.1 and/or vCenter plugin is VC 6.5.0.7720419?

Awesome, thanks!

It look like we have an issue with compatibility of new builds with  vRo 7.3 platform. I removed the problem version from this page. We are working on a fix.

I updated my VC plugin to the latest version o11nplugin-vsphere-6.5.0-7646854.vmoapp.zip and it breaks the VC plugin. My vCenter inventory is gone and if I try to add it back I get:

Add a vCenter Server instance/item3', state: 'failed', business state: 'Connection validation failed', exception: 'ReferenceError: "VcPlugin" is not defined. (Workflow:Add a vCenter Server instance / Validate (item2)#1)'

workflow: 'Add a vCenter Server instance' (f246b7b5-fe89-4da5-a640-36ffc6874069)

|  'attribute': name=hostAndPort type=string value=vcenter-1.purecloud.com:443

|  'attribute': name=errorCode type=string value=ReferenceError: "VcPlugin" is not defined. (Workflow:Add a vCenter Server instance / Validate (item2)#1)

|  'attribute': name=serviceUrls type=Array/string value=#{#string#vcenter-1.purecloud.com:443#;#string#https://vcenter-1.purecloud.com:443/pbm#;#string#https://vcenter-1.purecloud.com:443/sms/sdk#}#

|  'attribute': name=certificateImportException type=string value=

|  'input': name=enabled type=boolean value=true

|  'input': name=host type=string value=vcenter-1.purecloud.com

|  'input': name=port type=number value=443

|  'input': name=path type=string value=/sdk

|  'input': name=sessionPerUser type=boolean value=false

|  'input': name=userName type=string value=cody

|  'input': name=password type=SecureString value=__NULL__

|  'input': name=domain type=string value=

|  'input': name=ignoreCertificateWarnings type=boolean value=true

|  'input': name=httpPort type=number value=null

|  'input': name=pbmUrl type=string value=https://vcenter-1.purecloud.com:443/pbm

|  'input': name=smsUrl type=string value=https://vcenter-1.purecloud.com:443/sms/sdk

|  'output': name=newInstance type=VC:SdkConnection value=null

*** End of execution stack.

I used vRO 7.3. I tried deploying a new vRO and upgraded to this plugin and got the same result.

Is there something required beyond a simple upload and restart to get this working? Thanks!

Never mind I see your message in this thread now Re: Orchestrator 7.2 to 7.3 upgrade breaks some scripting

Whats new with this update today?