You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Marcus Sorensen <sh...@gmail.com> on 2013/10/29 15:21:37 UTC
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
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? Are there any tests that might fail due to
hardcoded response expectations?
Re: listVolumes pool id
Posted by Marcus Sorensen <sh...@gmail.com>.
Thanks!
On Tue, Oct 29, 2013 at 10:23 AM, Alena Prokharchyk
<Al...@citrix.com> wrote:
> Marcus,
>
> I fixed it in the latest master code some time ago. The parameter is returned to the ROOT admin only as only the user of this type knows the DC details (hosts, storage pools, networks, etc).
>
> -Alena.
>
> From: Marcus Sorensen <sh...@gmail.com>>
> Reply-To: "dev@cloudstack.apache.org<ma...@cloudstack.apache.org>" <de...@cloudstack.apache.org>>
> Date: Tuesday, October 29, 2013 7:21 AM
> To: "dev@cloudstack.apache.org<ma...@cloudstack.apache.org>" <de...@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
> 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? Are there any tests that might fail due to
> hardcoded response expectations?
>
Re: listVolumes pool id
Posted by Nitin Mehta <Ni...@citrix.com>.
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" <sh...@gmail.com> wrote:
>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? Are there any tests that might fail due to
>hardcoded response expectations?
Re: listVolumes pool id
Posted by Alena Prokharchyk <Al...@citrix.com>.
Marcus,
I fixed it in the latest master code some time ago. The parameter is returned to the ROOT admin only as only the user of this type knows the DC details (hosts, storage pools, networks, etc).
-Alena.
From: Marcus Sorensen <sh...@gmail.com>>
Reply-To: "dev@cloudstack.apache.org<ma...@cloudstack.apache.org>" <de...@cloudstack.apache.org>>
Date: Tuesday, October 29, 2013 7:21 AM
To: "dev@cloudstack.apache.org<ma...@cloudstack.apache.org>" <de...@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
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? Are there any tests that might fail due to
hardcoded response expectations?