openstack team mailing list archive

[Justin Santa Barbara <justin@xxxxxxxxxxxx>]

There are many existing volume solutions.  Some are in production use (AoE,
iSCSI).  There are enterprise-class SAN providers (Solaris, HP/LeftHand
SANs).  There are existing projects to build 'cloud' storage solutions that
are shaping up very well (SheepDog, RBD).

It's great that you're thinking about how to add another option to the mix.
 I do think you should consider supporting one of the existing efforts
unless you have a radically different approach, but it's open source, so
you're free to scratch your own itch.

However: this should not be allowed to impact the volumes API.  I consider
volumes to be a core feature of the cloud; and OpenStack has great volume
support today.  We have API support for volumes today in the EC2 API, and if
we want people to use the OpenStack API, then API support for volumes needs
to be there as well.  This does not mean that volumes must be enabled on
every OpenStack deployment, so even if CloudServers can't support volumes
initially, we should still provide the API.

So: When can we expect volume support in nova?  If I repackaged my volumes
API as an extension, can we get it merged into Cactus?

Justin


On Tue, Mar 22, 2011 at 11:53 AM, Chuck Thier <cthier@xxxxxxxxx> wrote:

> Hi Adam,
>
> We have just begun an R&D effort for building a scalable block storage
> service with commodity hardware.  We are still working more on the back end
> specifics for this, so we haven't spent much time looking at the end user
> apis yet.  We are open to hearing feedback on that front though, and plan on
> discussing it more at the next developer summit.
>
> This project will be developed in the open, and when complete will
> be submitted to the Policy Board as a candidate for inclusion in Openstack
> proper.  I don't have a lot of details to share yet, but plan on discussing
> much at the next summit.
>
> --
> Chuck
>
> On Tue, Mar 22, 2011 at 11:20 AM, John Purrier <john@xxxxxxxxxxxxx> wrote:
>
>> I know that creiht is looking at this for Rackspace. Chuck, anything to
>> add
>> to this discussion?
>>
>> John
>>
>> -----Original Message-----
>> From: openstack-bounces+john=openstack.org@xxxxxxxxxxxxxxxxxxx
>> [mailto:openstack-bounces+john=openstack.org@xxxxxxxxxxxxxxxxxxx] On
>> Behalf
>> Of Adam Johnson
>> Sent: Monday, March 21, 2011 10:15 PM
>> To: openstack@xxxxxxxxxxxxxxxxxxx
>> Subject: [Openstack] Openstack API - Volumes?
>>
>> Hey everyone,
>>
>> I wanted to bring up the topic of volumes in the OpenStack API.  I
>> know there was some discussion about this before, but it seems to have
>> faded on the ML.   I know Justinsb has done some work on this already,
>> and has a branch here:
>>
>> https://code.launchpad.net/~justin-fathomdb/nova/justinsb-openstack-api-volu
>> mes
>>
>> Im wondering what the consensus is on what the API should look like,
>> and when we could get this merged into Nova?
>>
>> Thanks,
>> Adam Johnson
>> Midokura
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>