I guess it should be fine. Adding a parameter shouldn't break the
compatibility and if it does then it should be corrected from the client
side.
On 29/10/13 7:21 AM, "Marcus Sorensen" wrote:
>I almost can't believe this doesn't already exist, but I noticed that
>listing a volume doesn't show you
v@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
> mailto:dev@cloudstack.apache.org>>
> Subject: listVolumes pool id
>
> I almost can't believe this doesn't already exist, but I noticed that
> listing a volume doesn't show you the id of the storage pool the
: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
mailto:dev@cloudstack.apache.org>>
Date: Tuesday, October 29, 2013 7:21 AM
To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
mailto:dev@cloudstack.apache.org>>
Subject: listVolumes pool id
I al
I almost can't believe this doesn't already exist, but I noticed that
listing a volume doesn't show you the id of the storage pool the
volume belongs to. It shows the pool name, but it seems that doesn't
have to be unique. Does anyone have a problem with me adding that to
the listVolumes response?
