Open Stack

On 11/10/2015 10:08 AM, Tzu-Mainn Chen wrote:
> Hi all,
> 
> At the last IRC meeting it was agreed that the new TripleO REST API
> should forgo the Tuskar name, and simply be called... the TripleO
> API.  There's one more point of discussion: where should the API
> live?  There are two possibilities:
> 
> a) Put it in tripleo-common, where the business logic lives.  If we
> do this, it would make sense to rename tripleo-common to simply
> tripleo.

This option makes the most sense to me now that I understand the
tripleoclient will also consume the REST API and not the underlying
python library with the "business logic".

>From a packaging point of view, I think this is pretty painless. I think
we would have a "python-tripleo" package for the library that
provides/obsoletes the current tripleo-common package. As well as a
"tripleo-api" package for the REST API service. We would not need to
touch the tripleo-incubator package that currently is named just "tripleo".

> 
> b) Put it in its own repo, tripleo-api
> 
> 
> The first option made a lot of sense to people on IRC, as the proposed
> API is a very thin layer that's bound closely to the code in tripleo-
> common.  The major objection is that renaming is not trivial; however
> it was mentioned that renaming might not be *too* bad... as long as
> it's done sooner rather than later.
> 
> What do people think?
> 
> 
> Thanks,
> Tzu-Mainn Chen
> 
> __________________________________________________________________________
> 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
>