<div dir="ltr">I agree to with the described benefits of separating the repos and my +1 for a separated repo.</div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, May 1, 2016 at 4:22 PM, Ryan Hallisey <span dir="ltr"><<a href="mailto:rhallise@redhat.com" target="_blank">rhallise@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm voting for separate repo. I'm not keen to adding 20 new cores to a stable repo. I'd prefer it to be in a different repo while it gets going. Yes, we will lose some git history *if* we vote to merge it into the main repo. It's not a guarantee.<br>
<br>
If this were to go into the main repo, I think it becomes harder for both ansible and kubernetes to ever come out. I'd rather start outside since it's easier to move in if we choose to do that.<br>
<br>
-Ryan<br>
<span class=""><br>
----- Original Message -----<br>
From: "Steven Dake (stdake)" <<a href="mailto:stdake@cisco.com">stdake@cisco.com</a>><br>
To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
</span><span class="">Sent: Sunday, May 1, 2016 5:03:57 PM<br>
Subject: [openstack-dev] [kolla][kubernetes] One repo vs two<br>
<br>
Ryan had rightly pointed out that when we made the original proposal 9am morning we had asked folks if they wanted to participate in a separate repository.<br>
<br>
I don't think a separate repository is the correct approach based upon one off private conversations with folks at summit. Many people from that list approached me and indicated they would like to see the work integrated in one repository as outlined in my vote proposal email. The reasons I heard were:<br>
<br>
<br>
</span> * Better integration of the community<br>
* Better integration of the code base<br>
* Doesn't present an us vs them mentality that one could argue happened during kolla-mesos<br>
* A second repository makes k8s a second class citizen deployment architecture without a voice in the full deployment methodology<br>
* Two gating methods versus one<br>
* No going back to a unified repository while preserving git history<br>
<span class="">I favor of the separate repositories I heard<br>
<br>
<br>
</span> * It presents a unified workspace for kubernetes alone<br>
* Packaging without ansible is simpler as the ansible directory need not be deleted<br>
<span class="">There were other complaints but not many pros. Unfortunately I failed to communicate these complaints to the core team prior to the vote, so now is the time for fixing that.<br>
<br>
I'll leave it open to the new folks that want to do the work if they want to work on an offshoot repository and open us up to the possible problems above.<br>
<br>
If you are on this list:<br>
<br>
<br>
<br>
</span> * Ryan Hallisey<br>
* Britt Houser<br>
<br>
<br>
* mark casey<br>
<br>
<br>
* Steven Dake (delta-alpha-kilo-echo)<br>
<br>
<br>
* Michael Schmidt<br>
<br>
<br>
* Marian Schwarz<br>
<br>
<br>
* Andrew Battye<br>
<br>
<br>
* Kevin Fox (kfox1111)<br>
<br>
<br>
* Sidharth Surana (ssurana)<br>
<br>
<br>
* Michal Rostecki (mrostecki)<br>
<br>
<br>
* Swapnil Kulkarni (coolsvap)<br>
<br>
<br>
* MD NADEEM (mail2nadeem92)<br>
<br>
<br>
* Vikram Hosakote (vhosakot)<br>
<br>
<br>
* Jeff Peeler (jpeeler)<br>
<br>
<br>
* Martin Andre (mandre)<br>
<br>
<br>
* Ian Main (Slower)<br>
<br>
<br>
* Hui Kang (huikang)<br>
<br>
<br>
* Serguei Bezverkhi (sbezverk)<br>
<br>
<br>
* Alex Polvi (polvi)<br>
<br>
<br>
* Rob Mason<br>
<br>
<br>
* Alicja Kwasniewska<br>
<br>
<br>
* sean mooney (sean-k-mooney)<br>
<br>
<br>
* Keith Byrne (kbyrne)<br>
<br>
<br>
* Zdenek Janda (xdeu)<br>
<br>
<br>
* Brandon Jozsa (v1k0d3n)<br>
<br>
<br>
* Rajath Agasthya (rajathagasthya)<br>
* Jinay Vora<br>
* Hui Kang<br>
* Davanum Srinivas<br>
<span class="im HOEnZb"><br>
<br>
Please speak up if you are in favor of a separate repository or a unified repository.<br>
<br>
The core reviewers will still take responsibility for determining if we proceed on the action of implementing kubernetes in general.<br>
<br>
Thank you<br>
-steve<br>
<br>
</span><div class="HOEnZb"><div class="h5">__________________________________________________________________________<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>
__________________________________________________________________________<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>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Best regards,
<br><br>Ihor Dvoretskyi, <br>OpenStack Operations Engineer
<br><br>---
<br><br>Mirantis, Inc.
(925) 808-FUEL</div></div></div></div>
</div>