Re: [openstack-dev] [nova] nova-specs and python-novaclient

2014-04-24 Thread Joe Gordon
On Wed, Apr 23, 2014 at 5:15 PM, Michael Still mi...@stillhq.com wrote: On Wed, Apr 23, 2014 at 11:34 PM, Russell Bryant rbry...@redhat.com wrote: John originally mentioned this on the review, but Phil and I both seem to agree. Most novaclient work can just be a work item of a nova

Re: [openstack-dev] [nova] nova-specs and python-novaclient

2014-04-24 Thread Melanie Witt
On Apr 23, 2014, at 17:15, Michael Still mi...@stillhq.com wrote: I don't think we should block the possibility of there being a novaclient specific BP sometime in the future. When we think of a good reason for one, let's just put it in a subdirectory. I agree. For example, this blueprint is

Re: [openstack-dev] [nova] nova-specs and python-novaclient

2014-04-23 Thread Russell Bryant
On 04/22/2014 08:24 PM, Joe Gordon wrote: On Tue, Apr 22, 2014 at 5:04 PM, Jay Pipes jaypi...@gmail.com mailto:jaypi...@gmail.com wrote: On Tue, 2014-04-22 at 17:00 -0700, Joe Gordon wrote: Hi All, Several folks have submitted python-novaclient blueprints to

Re: [openstack-dev] [nova] nova-specs and python-novaclient

2014-04-23 Thread Michael Still
On Wed, Apr 23, 2014 at 11:34 PM, Russell Bryant rbry...@redhat.com wrote: John originally mentioned this on the review, but Phil and I both seem to agree. Most novaclient work can just be a work item of a nova blueprint. How about we just handle it that way? For those cases where that's

[openstack-dev] [nova] nova-specs and python-novaclient

2014-04-22 Thread Joe Gordon
Hi All, Several folks have submitted python-novaclient blueprints to nova specs for the Juno Release [0][1], but since python-novaclient isn't part of the integrated release this doesn't really make sense. Furthermore the template we have has sections that make no sense for the client (such as

Re: [openstack-dev] [nova] nova-specs and python-novaclient

2014-04-22 Thread Jay Pipes
On Tue, 2014-04-22 at 17:00 -0700, Joe Gordon wrote: Hi All, Several folks have submitted python-novaclient blueprints to nova specs for the Juno Release [0][1], but since python-novaclient isn't part of the integrated release this doesn't really make sense. Furthermore the template we

Re: [openstack-dev] [nova] nova-specs and python-novaclient

2014-04-22 Thread Joe Gordon
On Tue, Apr 22, 2014 at 5:04 PM, Jay Pipes jaypi...@gmail.com wrote: On Tue, 2014-04-22 at 17:00 -0700, Joe Gordon wrote: Hi All, Several folks have submitted python-novaclient blueprints to nova specs for the Juno Release [0][1], but since python-novaclient isn't part of the

Re: [openstack-dev] [nova] nova-specs and python-novaclient

2014-04-22 Thread Michael Still
My biggest concern with your proof of concept is that it would require all outstanding blueprints to do a rebase, which sounds painful. Could we perhaps create a subdirectory for novaclient, and keep the nova stuff at the top level until most things have landed? Michael On Wed, Apr 23, 2014 at