Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

2016-05-05 Thread Murray, Paul (HP Cloud)
> -Original Message- > From: Edward Leafe [mailto:e...@leafe.com] > Sent: 05 May 2016 04:32 > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [nova][osc] Use of openstack cli

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

2016-05-05 Thread Ghe Rivero
On 04/05/16 22:53, Jay Pipes wrote: On 05/04/2016 01:08 PM, Chris Dent wrote: The plans for generic resource pools[1] include a suite of new commands for creating and updating resource pools. In today's Nova API meeting[2] and afterwards in #openstack-nova[3] we discussed two issues: * Since

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

2016-05-04 Thread Edward Leafe
On May 4, 2016, at 3:53 PM, Jay Pipes wrote: > My position is that if it's an HTTP API (as opposed to something like a > sqlalchemy-migrate sync command) then it belongs in a client that speaks the > OpenStack HTTP APIs. That is OSC as far as I can tell. I don't see a >

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

2016-05-04 Thread Steve Martinelli
+100 Jay On Wed, May 4, 2016 at 4:53 PM, Jay Pipes wrote: > On 05/04/2016 01:08 PM, Chris Dent wrote: > >> >> The plans for generic resource pools[1] include a suite of new >> commands for creating and updating resource pools. In today's Nova >> API meeting[2] and afterwards

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

2016-05-04 Thread Jay Pipes
On 05/04/2016 01:08 PM, Chris Dent wrote: The plans for generic resource pools[1] include a suite of new commands for creating and updating resource pools. In today's Nova API meeting[2] and afterwards in #openstack-nova[3] we discussed two issues: * Since the placement API associated with

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

2016-05-04 Thread Dean Troyer
On Wed, May 4, 2016 at 1:54 PM, Sean Dague wrote: > Given these constraints it was as much of an ask as anything else. Can > OSC handle this? Should it handle it from a best practices perspective? > How are commands exposed / hidden based on user permissions? The fact > that

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

2016-05-04 Thread Tim Bell
On 04/05/16 20:54, "Sean Dague" wrote: >On 05/04/2016 02:16 PM, Dean Troyer wrote: >> On Wed, May 4, 2016 at 12:08 PM, Chris Dent > > wrote: >> >> Since then the spec has been updated to reflect using OSC but the

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

2016-05-04 Thread Sean Dague
On 05/04/2016 02:16 PM, Dean Troyer wrote: > On Wed, May 4, 2016 at 12:08 PM, Chris Dent > wrote: > > Since then the spec has been updated to reflect using OSC but the > question of whether this is in fact the right place for this

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

2016-05-04 Thread Matt Riedemann
On 5/4/2016 12:08 PM, Chris Dent wrote: The plans for generic resource pools[1] include a suite of new commands for creating and updating resource pools. In today's Nova API meeting[2] and afterwards in #openstack-nova[3] we discussed two issues: * Since the placement API associated with

Re: [openstack-dev] [nova][osc] Use of openstack client for admin commands

2016-05-04 Thread Dean Troyer
On Wed, May 4, 2016 at 12:08 PM, Chris Dent wrote: > Since then the spec has been updated to reflect using OSC but the > question of whether this is in fact the right place for this style > of commands remains open. Not just for this situation, but > generally. > This

[openstack-dev] [nova][osc] Use of openstack client for admin commands

2016-05-04 Thread Chris Dent
The plans for generic resource pools[1] include a suite of new commands for creating and updating resource pools. In today's Nova API meeting[2] and afterwards in #openstack-nova[3] we discussed two issues: * Since the placement API associated with resource pools is eventually going to be