RE: [VOTE] Enforcing UUID string in API query

2012-12-27 Thread Rohit Yadav
} Regards. From: Nitin Mehta [nitin.me...@citrix.com] Sent: Friday, December 28, 2012 9:08 AM To: cloudstack-users@incubator.apache.org Cc: cloudstack-...@incubator.apache.org Subject: Re: [VOTE] Enforcing UUID string in API query Hi Rohit, I didn't understand the rationale behind this.

Re: [VOTE] Enforcing UUID string in API query

2012-12-27 Thread Nitin Mehta
lidated. >> >> Will >> >>> -Original Message- >>> From: Alex Huang [mailto:alex.hu...@citrix.com] >>> Sent: Thursday, December 27, 2012 12:44 PM >>> To: cloudstack-...@incubator.apache.org >>> Cc: cloudstack-users@incubator.

RE: [VOTE] Enforcing UUID string in API query

2012-12-27 Thread Alex Huang
t: RE: [VOTE] Enforcing UUID string in API query > > I personally do not like flags changing syntax which is what it is in this > case. A > flag to support whether a feature like "snapshots" is supported is ok. A flag > to say whether ID or UUID is accepted means issues

Re: [VOTE] Enforcing UUID string in API query

2012-12-27 Thread John Kinsella
-1. At the least we need to depreciate over time, but if at all possible, would be good to know how many folks are using the existing internal ID. John On Dec 27, 2012, at 12:11 PM, Rohit Yadav wrote: > Hi, > > I'm asking for the community to vote if they want to enforce UUID string to > be

Re: [VOTE] Enforcing UUID string in API query

2012-12-27 Thread Rohit Yadav
loudstack-users@incubator.apache.org >> Subject: RE: [VOTE] Enforcing UUID string in API query >> >> Sorry I don't understand why it needs to be a vote. Why can't we just offer >> a flag to turn it on and off? >> >> --Alex >> >>>

RE: [VOTE] Enforcing UUID string in API query

2012-12-27 Thread Will Chan
be tested and validated. Will > -Original Message- > From: Alex Huang [mailto:alex.hu...@citrix.com] > Sent: Thursday, December 27, 2012 12:44 PM > To: cloudstack-...@incubator.apache.org > Cc: cloudstack-users@incubator.apache.org > Subject: RE: [VOTE] Enforcing UUID st

Re: [VOTE] Enforcing UUID string in API query

2012-12-27 Thread Rohit Yadav
anks all for your comments. Regards. > > --Alex > >> -Original Message- >> From: Rohit Yadav [mailto:rohit.ya...@citrix.com] >> Sent: Thursday, December 27, 2012 12:11 PM >> To: cloudstack-...@incubator.apache.org >> Cc: cloudstack-users@incubator.apache.or

Re: [VOTE] Enforcing UUID string in API query

2012-12-27 Thread Mathias Mullins
;> Sent: Thursday, December 27, 2012 12:11 PM >> To: cloudstack-...@incubator.apache.org >> Cc: cloudstack-users@incubator.apache.org >> Subject: [VOTE] Enforcing UUID string in API query >> >> Hi, >> >> I'm asking for the community to vote if they want to

Re: [VOTE] Enforcing UUID string in API query

2012-12-27 Thread Nik Martin
On 12/27/2012 02:11 PM, Rohit Yadav wrote: Hi, -1 with a comment: To deprecate an api function, you have two methods (probably more, but these are common): 1. overload the function to accept both UUID and ID, which gives you backwards compatibility forever, but is cumbersome to maintain. 2.

RE: [VOTE] Enforcing UUID string in API query

2012-12-27 Thread Alex Huang
ubator.apache.org > Cc: cloudstack-users@incubator.apache.org > Subject: [VOTE] Enforcing UUID string in API query > > Hi, > > I'm asking for the community to vote if they want to enforce UUID string to > be used in parameters while querying an API. This would break any cli

RE: [VOTE] Enforcing UUID string in API query

2012-12-27 Thread Will Chan
is is just not practical. Will > -Original Message- > From: Rohit Yadav [mailto:rohit.ya...@citrix.com] > Sent: Thursday, December 27, 2012 12:11 PM > To: cloudstack-...@incubator.apache.org > Cc: cloudstack-users@incubator.apache.org > Subject: [VOTE] Enforcing UUID stri

Re: [VOTE] Enforcing UUID string in API query

2012-12-27 Thread Rohit Yadav
Forgot to mention, let's keep the voting period open till 7th Jan 2013 12:00 GMT, i.e. as a lot of people are offline. On 27-Dec-2012, at 12:11 PM, Rohit Yadav wrote: > Hi, > > I'm asking for the community to vote if they want to enforce UUID string to > be used in parameters while querying a

[VOTE] Enforcing UUID string in API query

2012-12-27 Thread Rohit Yadav
Hi, I'm asking for the community to vote if they want to enforce UUID string to be used in parameters while querying an API. This would break any client or script that uses internal ID. AFAIK api response (json or xml, since 3.x for sure) always have had UUIDs so if any client/script that uses

Re: API Query

2012-10-05 Thread Nitin Mehta
This is a bug. I just checked the code but couldn't find the reason for it being there. if (zone != null) { sc.setParameters("dataCenterId", zone); if(state == null) { sc.setParameters("stateNEQ", "Destroyed"); } } Thanks, -

Re: API Query

2012-10-05 Thread Alena Prokharchyk
Vms in Destroyed state should be returned in listVirtualMachines API response (when the call is made by root/domain Admin) no matter if it's executed with zoneId, or w/o. Simon, please file a bug against management server component. Thanks, Alena. On 10/5/12 9:27 AM, "Simon Waterhouse" wrote:

API Query

2012-10-05 Thread Simon Waterhouse
I have a single zone CloudStack with some deleted instances in the zone If I use the REST API to query "command=listVirtualMachines" then it returns me a record of the deleted instances. However if I specify the UID of the zone with the query "command=listVirtualMachines&zoneid=" then the server