Re: [dev] Block storage volume API

[Alex Amies <al...@gmail.com>]

This is a big step forward but I think that we are missing a list_volumes()
method.  It is important to me and seems inconsistent that LinCloud has
create and delete methods for storage volumes without at way to find out
what has been created.

I would like to propose a new method to the NodeDriver class consistent
with list_nodes() and similar methods to do this.  I have added it to the
Jira issue:

https://issues.apache.org/jira/browse/LIBCLOUD-213?focusedCommentId=13411358#comment-13411358

Regards

Alex

On Sat, Jun 16, 2012 at 5:26 PM, Gabriel Reid <ga...@gmail.com>wrote:

> > Overall the API you proposed looks pretty solid to me. Next step would be
> > implementing this API for at least two providers. When coding a new API
> we
> > require user to implement it for at least two providers so the
> > implementation is not biased towards a single one.
> >
> > I also closed the old ticket on JIRA. Feel free to open a new one and
> attach
> > your patch there when you make some progress.
> >
>
> I've created a new ticket in JIRA
> (https://issues.apache.org/jira/browse/LIBCLOUD-213) along with a
> patch with the CloudStack and EC2 implementations. Comments welcome!
>
> - Gabriel
>

Re: [dev] Block storage volume API

[Tomaž Muraus <to...@apache.org>]

Cool, keep us posted and let us know if you need help.

On Thu, Jul 12, 2012 at 3:24 AM, Aymeric Barantal <mr...@gandi.net> wrote:

>
> Le 12 juil. 2012 à 09:05, Tomaž Muraus a écrit :
>
> > list_volumes() sounds reasonable to me. Next step would
> > be researching existing provider APIs and see if most of them support
> this
> > functionality. If they do, we can then work on implementing those
> methods.
>
> I started implementation of this Volume object and methods in gandi
> libcloud driver,
> and yes list_volumes was missing.
>
> It sound clear for me to implement these volume related methods. I'll come
> with
> a Jira issue and a pull request in some days regarding gandi compute
> driver.
>
> Sincerly,
>
> Aymeric Barantal

Re: [dev] Block storage volume API

[Aymeric Barantal <mr...@gandi.net>]

Le 12 juil. 2012 à 09:05, Tomaž Muraus a écrit :

> list_volumes() sounds reasonable to me. Next step would
> be researching existing provider APIs and see if most of them support this
> functionality. If they do, we can then work on implementing those methods.

I started implementation of this Volume object and methods in gandi libcloud driver,
and yes list_volumes was missing.

It sound clear for me to implement these volume related methods. I'll come with 
a Jira issue and a pull request in some days regarding gandi compute driver.

Sincerly,

Aymeric Barantal

Re: [dev] Block storage volume API

[Tomaž Muraus <to...@apache.org>]

list_volumes() sounds reasonable to me. Next step would
be researching existing provider APIs and see if most of them support this
functionality. If they do, we can then work on implementing those methods.

On Wed, Jul 11, 2012 at 2:58 AM, Alex Amies <al...@gmail.com> wrote:

> This is a big step forward but I think that we are missing a
> list_volumes() method.  It is important to me and seems inconsistent that
> LinCloud has create and delete methods for storage volumes without at way
> to find out what has been created.
>
> I would like to propose a new method to the NodeDriver class consistent
> with list_nodes() and similar methods to do this.  I have added it to the
> Jira issue:
>
>
> https://issues.apache.org/jira/browse/LIBCLOUD-213?focusedCommentId=13411358#comment-13411358
>
> Regards
>
> Alex
>
>
> On Sat, Jun 16, 2012 at 5:26 PM, Gabriel Reid <ga...@gmail.com>wrote:
>
>> > Overall the API you proposed looks pretty solid to me. Next step would
>> be
>> > implementing this API for at least two providers. When coding a new API
>> we
>> > require user to implement it for at least two providers so the
>> > implementation is not biased towards a single one.
>> >
>> > I also closed the old ticket on JIRA. Feel free to open a new one and
>> attach
>> > your patch there when you make some progress.
>> >
>>
>> I've created a new ticket in JIRA
>> (https://issues.apache.org/jira/browse/LIBCLOUD-213) along with a
>> patch with the CloudStack and EC2 implementations. Comments welcome!
>>
>> - Gabriel
>>
>
>