On 17 November 2015 at 15:31, Tzu-Mainn Chen <tzuma...@redhat.com> wrote:
> > ------------------------------ > > > > On 10 November 2015 at 15:08, Tzu-Mainn Chen <tzuma...@redhat.com> 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. >> > > +1 - I think this makes most sense if we are not going to support the > tripleo repo as a library. > > > Okay, this seems to be the consensus, which is great. > > The leftover question is how to package the renamed repo. 'tripleo' is > already intuitively in use by tripleo-incubator. > In IRC, bnemec and trown suggested splitting the renamed repo into two > packages - 'python-tripleo' and 'tripleo-api', > which seems sensible to me. > > What do others think? > Yup, that sounds good. Eventually when the CLI is untangled from tripleo_common we wont need the python-tripleo package as it wont ever be used as a library. > > > Mainn > > > 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-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
