Open Stack

+100 Jay

On Wed, May 4, 2016 at 4:53 PM, Jay Pipes <jaypipes at gmail.com> 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 the placement API associated with resource pools is eventually
>>    going to be hoisted out of nova it will be developed in a decoupled
>>    fashion within the nova tree. It makes sense to also hoist the client
>>    libraries in the same fashion. The canonical plan for CLIs is to
>>    plug in to OSC.
>>
>> * There's some confusion on whether commands that are destined for
>>    admins and services but not end users are "supposed" to be in OSC.
>>
>> 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.
>>
>> Is there an official word on this? If not, should we make one?
>>
>
> 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
> difference between "admin" commands and "standard" commands.
>
> Best,
> -jay
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160504/d537bc6e/attachment.html>