[openstack-dev] [TripleO] Tuskar CLI after architecture changes

James Slagle james.slagle at gmail.com
Wed Dec 11 15:59:01 UTC 2013

On Wed, Dec 11, 2013 at 10:35 AM, James Slagle <james.slagle at gmail.com> wrote:
> On Wed, Dec 11, 2013 at 7:33 AM, Jiří Stránský <jistr at redhat.com> wrote:
>> 1) Make a thicker python-tuskarclient and put the business logic there. Make
>> it consume other python-*clients. (This is an unusual approach though, i'm
>> not aware of any python-*client that would consume and integrate other
>> python-*clients.)
> python-openstackclient consumes other clients :).  Ok, that's probably
> not a great example :).
> This approach makes the most sense to me.  python-tuskarclient would
> make the decisions about if it can call the heat api directly, or the
> tuskar api, or some other api.  The UI and CLI would then both use
> python-tuskarclient.

Another example:

Each python-*client also uses keystoneclient to do auth and get
endpoints.  So, it's not like each client has reimplemented the code
to make HTTP requests to keystone, they reuse the keystone Client
class object.

-- James Slagle

More information about the OpenStack-dev mailing list