VMware

This Question is Not Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
2 Replies Last post: Nov 6, 2009 12:17 AM by MartinCartwri…  

determining expired configurations posted: Oct 29, 2009 8:16 AM

Click to view MartinCartwright's profile Lurker 2 posts since
Jul 14, 2009
It seems that ListConfigurations() calls return all configurations, including those whose storage lease has expired. We would like to be able to exclude these configurations from the results, but can see no way to distinguish between an expired configuration and an unexpired configuration. we are currently using the v3 api. Looking at v4 it seems there are additional methods and members relating to leases, but still nothing that would enable us to figure out if a configuration's storage lease had expired.

Is there any way to achieve this? Or at least is there a way to determine if a config has expired from any other properties?

Re: determining expired configurations

1. Nov 5, 2009 7:09 PM in response to: MartinCartwri…
Click to view hsmith-vmware's profile Enthusiast 35 posts since
Feb 27, 2008

I haven't been able to check it out myself for you, but would there be a way for you to filter results before displaying? I'm think that since we can filter on the web interface, i would think the API would also let you filter and only display results showing "expired."

Hopefully this helps and is accurate. :)

(If your question has been resolved please mark the answers as "Helpful" or "Correct".)

Developer Social Media

Communities