Open Stack

On Wed, May 4, 2016 at 1:54 PM, Sean Dague <sean at dague.net> 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 we're going to need a service library mean that a dedicated admin
> API might be appropriate?
>

The only hiding/exposing of commands that OSC does is based on API
versions.  We have no plans to ever get into attempting to evaluate policy
even if/when that information becomes available via API.

That said, I think this belongs in a plugin in the client lib.  We do have
plans to extract the common shell bits of OSC into a library (osc-lib) that
could be used to also make stand-alone CLIs that look and act like OSC,
with only the plugin commands present.  Even assuming only the additional
dependency of the new lib, adding it to the OSC repo would also work, I
just think it makes more sense for these commands to not be present in the
default installation non-cloud-ops users would see.

dt

-- 

Dean Troyer
dtroyer at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160504/c6491007/attachment.html>