Re: [Openstack] Openstack API - Volumes?

2011-03-23 Thread Chuck Thier
Now that I have had a chance to look into this a little more,  I realize
that I had missed the connection of talking about the volume functionality
missing in the Openstack Rest API (versus the EC2 api that was already
there).

Justin: Sorry I'm a bit late to the game on this, but is there a
blueprint/documentation for the API that I could take a look at?

And I agree with the others that it would be nice to get the Openstack API
side of things moving since it is a pretty core element and should be in
Cactus, but like I said, I'm not a core dev for nova, so what needs to be
done to get this going?

I also think that since this is a core piece that doesn't exist already, I
don't think it should be an extension and we should work on getting it in
there.

--
Chuck

On Mon, Mar 21, 2011 at 10:14 PM, Adam Johnson adj...@gmail.com wrote:

 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-volumes

 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@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Openstack API - Volumes?

2011-03-22 Thread John Purrier
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@lists.launchpad.net
[mailto:openstack-bounces+john=openstack@lists.launchpad.net] On Behalf
Of Adam Johnson
Sent: Monday, March 21, 2011 10:15 PM
To: openstack@lists.launchpad.net
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@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Openstack API - Volumes?

2011-03-22 Thread Justin Santa Barbara
I am happy to do a first pass over the volume API.  I can do it as an
extension or not, whatever is more likely to be merged.

My personal feeling is that we shouldn't use extensions for something this
core, but we can do a 'full lifecycle' if we want: I'll write it as an
extension, we work on it as a community, then we promote it into core
if/when it is ready.

The thing I don't like about the extension promotion process is that it
breaks clients when the volume API is promoted.  But I'm all for trying it
and seeing what happens.

Justin




On Tue, Mar 22, 2011 at 1:20 PM, Jay Pipes jaypi...@gmail.com wrote:

 On Tue, Mar 22, 2011 at 3:21 PM, Justin Santa Barbara
 jus...@fathomdb.com wrote:
  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?

 I would personally support this.

 Wasn't one of the ideas of the extensions API to provide a bit of a
 playground for features to bake that, at some future time, be made a
 core resource endpoint in the OpenStack API? This would be a perfect
 example of that, no?

 -jay

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Openstack API - Volumes?

2011-03-22 Thread Jorge Williams
Describing full Volume API as an extension may work in the short term.  Long 
term though we're moving towards having a suite of APIs.  From this perspective 
adding an extension to OpenStack Compute API seems a little strange to me.  But 
it could work short term, my concern is that we should really be thinking of 
Volumes as a core API, not additional features to Compute. Certainly we may 
need to extend compute to do things like mount/unmount a volume.

-jOrGe W.


On Mar 22, 2011, at 3:20 PM, Jay Pipes wrote:

 On Tue, Mar 22, 2011 at 3:21 PM, Justin Santa Barbara
 jus...@fathomdb.com wrote:
 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?
 
 I would personally support this.
 
 Wasn't one of the ideas of the extensions API to provide a bit of a
 playground for features to bake that, at some future time, be made a
 core resource endpoint in the OpenStack API? This would be a perfect
 example of that, no?
 
 -jay
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Openstack API - Volumes?

2011-03-22 Thread Jorge Williams

On Mar 22, 2011, at 3:33 PM, Justin Santa Barbara wrote:

 The thing I don't like about the extension promotion process is that it 
 breaks clients when the volume API is promoted


Promotion only occurs between version changes in the API, that is when we're 
moving from say 1.1 to 2.0.  Version changes by definition break clients 
anyway.  The extension will stay an extension in 1.1 always, even if the 
extension is promoted in 2.0.  So clients built against 1.1 will continue to 
consume the extension as is and will not be broken -- code will have to be 
changed regardless to move to 2.0 at this point the extension is core.

-jOrGe W.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Openstack API - Volumes?

2011-03-22 Thread Adam Johnson
Hey Chuck,

Thanks for the response.  We are very interested in this project as
well, and may want to contribute.  We're currently evaluating options
such as Sheepdog and others to see if they fit the bill.  In order to
fully evaluate these options, it would be great to have *some* API
support in the project.

I think adding volumes as an extension short term seems like a good
idea.  Whatever it takes to get something in there, so we can get our
hands dirty and experiment some more.

Adam

On Wed, Mar 23, 2011 at 3:53 AM, Chuck Thier cth...@gmail.com wrote:
 Hi Adam,
 We have just begun an RD 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 j...@openstack.org 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@lists.launchpad.net
 [mailto:openstack-bounces+john=openstack@lists.launchpad.net] On
 Behalf
 Of Adam Johnson
 Sent: Monday, March 21, 2011 10:15 PM
 To: openstack@lists.launchpad.net
 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@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp


 ___
 Mailing list: https://launchpad.net/~openstack
 Post to     : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Openstack API - Volumes?

2011-03-22 Thread Chuck Thier
Hey Adam,

As far as I understand it, there is already basic volume support within
nova, and that there are currently some suggested changes for the current
API.  We are planning to fit within that API as much as possible, and work
with the community to make any changes that may need to be made (an easy
example is snapshot support for snapshots in swift).

Most of our team will be at the developers summit, and look forward to
discussing it with others then.

--
Chuck

On Tue, Mar 22, 2011 at 8:00 PM, Adam Johnson adj...@gmail.com wrote:

 Hey Chuck,

 Thanks for the response.  We are very interested in this project as
 well, and may want to contribute.  We're currently evaluating options
 such as Sheepdog and others to see if they fit the bill.  In order to
 fully evaluate these options, it would be great to have *some* API
 support in the project.

 I think adding volumes as an extension short term seems like a good
 idea.  Whatever it takes to get something in there, so we can get our
 hands dirty and experiment some more.

 Adam

 On Wed, Mar 23, 2011 at 3:53 AM, Chuck Thier cth...@gmail.com wrote:
  Hi Adam,
  We have just begun an RD 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 j...@openstack.org
 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@lists.launchpad.net
  [mailto:openstack-bounces+john=openstack@lists.launchpad.net] On
  Behalf
  Of Adam Johnson
  Sent: Monday, March 21, 2011 10:15 PM
  To: openstack@lists.launchpad.net
  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@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp
 
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp
 
 

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Re: [Openstack] Openstack API - Volumes?

2011-03-22 Thread Adam Johnson
Sounds great,

We are basing our developments off of Justin's API work, just wanted
to get a consensus from the community on his approach, and see how we
can get it in as an optional component so that people can start
getting their hands dirty.

We're also interested in the snapshots support as well.  Have you
started working on this feature, as well as the block storage project?
 Could you share some timelines with us so that we can maybe
collaborate?

Thanks!

Adam

On Wed, Mar 23, 2011 at 10:13 AM, Chuck Thier cth...@gmail.com wrote:
 Hey Adam,
 As far as I understand it, there is already basic volume support within
 nova, and that there are currently some suggested changes for the current
 API.  We are planning to fit within that API as much as possible, and work
 with the community to make any changes that may need to be made (an easy
 example is snapshot support for snapshots in swift).
 Most of our team will be at the developers summit, and look forward to
 discussing it with others then.
 --
 Chuck

 On Tue, Mar 22, 2011 at 8:00 PM, Adam Johnson adj...@gmail.com wrote:

 Hey Chuck,

 Thanks for the response.  We are very interested in this project as
 well, and may want to contribute.  We're currently evaluating options
 such as Sheepdog and others to see if they fit the bill.  In order to
 fully evaluate these options, it would be great to have *some* API
 support in the project.

 I think adding volumes as an extension short term seems like a good
 idea.  Whatever it takes to get something in there, so we can get our
 hands dirty and experiment some more.

 Adam

 On Wed, Mar 23, 2011 at 3:53 AM, Chuck Thier cth...@gmail.com wrote:
  Hi Adam,
  We have just begun an RD 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 j...@openstack.org
  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@lists.launchpad.net
  [mailto:openstack-bounces+john=openstack@lists.launchpad.net] On
  Behalf
  Of Adam Johnson
  Sent: Monday, March 21, 2011 10:15 PM
  To: openstack@lists.launchpad.net
  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@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp
 
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to     : openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp
 
 



___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp