<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 24 November 2015 at 07:45, Richard Su <span dir="ltr"><<a href="mailto:rwsu@redhat.com" target="_blank">rwsu@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class="">
<br>
<br>
<div>On 11/17/2015 07:31 AM, Tzu-Mainn Chen
wrote:<br>
</div>
<blockquote type="cite">
<div style="font-family:times new roman,new york,times,serif;font-size:12pt;color:#000000">
<div><br>
</div>
<hr>
<blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 10 November 2015 at 15:08,
Tzu-Mainn Chen <span dir="ltr"><<a href="mailto:tzumainn@redhat.com" target="_blank"></a><a href="mailto:tzumainn@redhat.com" target="_blank">tzumainn@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
all,<br>
<br>
At the last IRC meeting it was agreed that the new
TripleO REST API<br>
should forgo the Tuskar name, and simply be called...
the TripleO<br>
API. There's one more point of discussion: where
should the API<br>
live? There are two possibilities:<br>
<br>
a) Put it in tripleo-common, where the business logic
lives. If we<br>
do this, it would make sense to rename tripleo-common
to simply<br>
tripleo.<br>
</blockquote>
<div><br>
</div>
<div>+1 - I think this makes most sense if we are not
going to support the tripleo repo as a library.<br>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Okay, this seems to be the consensus, which is great.<br>
</div>
<div><br>
</div>
<div>The leftover question is how to package the renamed repo.
'tripleo' is already intuitively in use by tripleo-incubator.<br>
</div>
<div>In IRC, bnemec and trown suggested splitting the renamed
repo into two packages - 'python-tripleo' and 'tripleo-api',<br>
</div>
<div>which seems sensible to me.<br>
</div>
<div><br>
</div>
<div>What do others think?<br>
</div>
<div><br>
</div>
<br>
</div>
</blockquote>
<br></span>
I have started the process of renaming the repo with these patches:<br>
<a href="https://review.openstack.org/#/c/247834/" rel="noreferrer" style="background-color:rgb(255,255,255);color:rgb(68,68,68);font-family:'Helvetica Neue',Arial,Helvetica,sans-serif;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:18px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">https://review.openstack.org/#/c/247834/</a><br>
<a href="https://review.gerrithub.io/#/c/252864/" rel="noreferrer" style="background-color:rgb(255,255,255);color:rgb(68,68,68);font-family:'Helvetica Neue',Arial,Helvetica,sans-serif;font-size:14px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:18px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">https://review.gerrithub.io/#/c/252864/</a><br>
<br>
Jan made an interesting suggestion that it may be easier to create a
new repo named tripleo and move the tripleo-common code there. With
renaming, I'm already see some complications with the tripleo-common
package builds failing in the CI until updated spec is merged. <br>
<br>
What do folks think about this? I am unsure which is more
complicated, creating a new repo and all the setup that goes with
it. Or renaming the existing repo and fixing CI issues along the
way.<span class="HOEnZb"><font color="#888888"><br></font></span></div></blockquote><div><br></div><div>I'm not sure which is easier or better, but if we do create a new repo we need to make sure we carry over the git history.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><span class="HOEnZb"><font color="#888888">
<br>
- Richard</font></span><span class=""><br>
<br>
<blockquote type="cite">
<div style="font-family:times new roman,new york,times,serif;font-size:12pt;color:#000000">
<div><br>
</div>
<blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
b) Put it in its own repo, tripleo-api<br>
<br>
<br>
The first option made a lot of sense to people on IRC,
as the proposed<br>
API is a very thin layer that's bound closely to the
code in tripleo-<br>
common. The major objection is that renaming is not
trivial; however<br>
it was mentioned that renaming might not be *too*
bad... as long as<br>
it's done sooner rather than later.<br>
<br>
What do people think?<br>
<br>
<br>
Thanks,<br>
Tzu-Mainn Chen<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage
questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
<br>
</div>
</div>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:
<a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
<div><br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</span></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>