Open Stack

Ok, thanks.

Usecase perspective, it is the under-cloud usecase (the cloud admin
provisioned the underlying storage - which will in turn use to create
cinder). Will there be any other usecase?

What will be the semantic of 'Edit' operation to the pool? Create and
Delete is obvious. But how to define the 'Edit'?




--pradip




On Thu, Feb 12, 2015 at 1:01 AM, Bruns, Curt E <curt.e.bruns at intel.com>
wrote:

> Hi Duncan and Pradip,
>
> It was Reddy, a colleague of mine at Intel, that expressed interest with
> managing storage pools in Cinder.  We haven’t put a BP out yet, but we
> definitely think it would be useful and we should get a BP in the works.
>
> - Curt
>
> From: Duncan Thomas <duncan.thomas at gmail.com<mailto:
> duncan.thomas at gmail.com>>
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org
> >>
> Date: Wednesday, February 11, 2015 at 10:38 AM
> To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org
> <mailto:openstack-dev at lists.openstack.org>>
> Subject: Re: [openstack-dev] [cinder] CURD operation for storage pools in
> Cinder
>
>
> As far as I know, this has not been looked at - you need to use whatever
> management tools your backend provides to do this.
>
> There was somebody from Intel IIRC in Paris with some interest in maybe
> starting something about this, but I don't know that it came to much.
>
> Duncan Thomas
>
> On Feb 11, 2015 6:53 PM, "Pradip Mukhopadhyay" <pradip.interra at gmail.com
> <mailto:pradip.interra at gmail.com>> wrote:
> Hello,
>
>
>
> Does Cinder already have a blue-print/planned-schedule for supporting (at
> least in API level - may not be python-client/Horizon levels) the
> create/edit/delete operation on the storage pools?
>
> It is understood that the "read" part 'get_pools' is already there.
>
>
> If it is already planned/scheduled - what is the time-frame of having it
> as a part of devstack?
>
>
>
> Thanks in advance,
> Pradip
>
>
>
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> <http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150212/92f2f4e3/attachment.html>