[openstack-dev] [TripleO] Tuskar CLI UX

Jiří Stránský jistr at redhat.com
Thu Feb 27 12:36:49 UTC 2014


On 26.2.2014 21:34, Dean Troyer wrote:
> On Wed, Feb 26, 2014 at 1:43 PM, Jay Dobies <jason.dobies at redhat.com> wrote:
>>
>> I like the notion of OpenStackClient. I'll talk ideals for a second. If we
>> had a standard framework and each project provided a command abstraction
>> that plugged in, we could pick and choose what we included under the Tuskar
>> umbrella. Advanced users with particular needs could go directly to the
>> project clients if needed.
>>
>
> This is a thing.  https://github.com/dtroyer/python-oscplugin is an example
> of a stand-alone OSC plugin that only needs to be installed to be
> recognized.  FWIW, four of the built-in API command sets in OSC also are
> loaded in this manner even though they are in the OSC repo so they
> represent additional examples of writing plugins.

Thanks for bringing this up. It looks really interesting. Is it possible 
to not only add commands to the OpenStackClient, but also purposefully 
blacklist some from appearing? As Jay mentioned in his reply, we don't 
make use of many commands in the undercloud and having the others appear 
in --help is just confusing. E.g. there's a lot of commands in Nova CLI 
that we'll not use and we have no use for Cinder CLI at all.

Even if we decided to build TripleO CLI separate from OpenStackClient, i 
think being able to consume this plugin API would help us. We could plug 
in the particular commands we want (and rename them if we want "node 
profiles" instead of "flavors") and hopefully not reimplement everything.


Thanks

Jirka



More information about the OpenStack-dev mailing list