cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sebastien Goasguen <run...@gmail.com>
Subject Re: Question concerning json response of deployvirtualmachine (4.1)
Date Tue, 29 Jan 2013 08:52:32 GMT

On Jan 28, 2013, at 10:52 PM, Rohit Yadav <rohit.yadav@citrix.com> wrote:

> On Mon, Jan 28, 2013 at 11:53 AM, Chip Childers
> <chip.childers@sungard.com> wrote:
>> Forward from the user list.  Rohit - want to answer?
>> 
>> 
>> ---------- Forwarded message ----------
>> From: Charles Moulliard <ch007m@gmail.com>
>> Date: Mon, Jan 28, 2013 at 2:51 PM
>> Subject: Question concerning json response of deployvirtualmachine (4.1)
>> To: cloudstack-users@incubator.apache.org
>> 
>> 
>> Hi,
>> 
>> The json response of deployvirtualmachine - 4.1-SNAPSHOT contains now a
>> variable "cloudstack-version".
>> 
> ...
>> 1.5.3 | << "{ "deployvirtualmachineresponse" :
>> {"id":"1cce6cb7-2268-47ff-9696-d9e610f6619a","jobid":"13330fc9-8b3e-4582-aa3e-90883c041ff0"},
>> "cloudstack-version": "4.1.0-SNAPSHOT" }"
>> 
>> As I don't see it in the doc here (
>> http://incubator.apache.org/cloudstack/docs/api/apidocs-4.0.0/TOC_User.html),
> 
> It's because in apidocs we only document the response object fields.
> 
>> can somebody confirms that this is new feature not yet published in the doc?
> 
> If it's not there, it's a bug as xml response contains cloudstack
> version number. Can you open an issue?
> 
>> Can we disable it to be compatible with CloudStack 3.0 API ?
> 
> The version field was inconsistent in xml/json response, xml response
> contains the cloudstack version info but json did not and hoping that
> I remember it correctly, in the past versions cloudstack api response
> used to have version info in both so I fixed the issues to return
> version information in both xml and json response. While adding a new
> field in json response should not break any scripts

It seems to be breaking Charles jclouds scripts.

Did you fix it in master after 4.0 release ? It could be that jclouds worked around this and
that by fixing it, we actually broke the jclouds client.


-sebastien

> 
> This information can be used by platforms that run on top of
> CloudStack and clients/scripts to implement logic to handle response
> based on version info.
> 
> We can discuss and remove this field if we don't want it.
> 
> Regards.
> 
>> 
>> Regards,
>> 
>> --
>> Charles Moulliard
>> Apache Committer / Sr. Enterprise Architect (RedHat)
>> Twitter : @cmoulliard | Blog : http://cmoulliard.blogspot.com


Mime
View raw message