Is there a way to fetch Data Objects properties such as vDS port state in a similar way to the propertyCollector for the Managed Objects

[AlinaDartu]

Hi,

I am trying to retrieve vDS ports properties such as the state in the most efficient way, not fetching the entire object but just this property. I know about the propertyCollector that can be used on a Managed object and I am wondering if there is a way to do something similar for the Data Objects. 

I need a very efficient way to do this on a large setup:  vCenter with 150 Hosts, 9000 VMs, all connected in 5 VDSs.

Thank you,

Alina

[stumpr]

You won't be able to do so for the data objects, but FetchDVPorts does support criteria.  Assuming you have something besides *all* that you care about, that should be more efficient?  Are you seeing extremely slow queries for that data?

[AlinaDartu]

I care about 80% of the ports and I tried dvs_object.FetchDVPorts(criteria) using as scope criteria the host but this criteria seems to be deprecated in 6.0 and for all ports beside the uplink ones the scope is Unset making the fetch return ports from all hosts.

Having a way to fetch only vDS ports of VMs from a certain host might help me because I might use parallel queries to get only the ports connected to a certain host. The final form in which I need this data are per host based.

[stumpr]

I generally haven't seen much of a gain in parallel queries.  Usually it's just a DB lookup on the backend and the data transfer (at least for what you're working on) shouldn't be that large.

Criteria isn't deprecated, it's the scope parameter.  And that's likely to be around for a long time.  Most of the deprecated properties are still available from 2.5 for example.  I think the official statement is deprecated is guaranteed for at least 2 releases?  But I'm not sure if that's still true (working on old statement).