<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">I +1 for split the kolla-k8s repo, too.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">Here is the reason:</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">1. Kolla will be split into several repo in the future: kolla-docker, kolla-ansible. So</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"> if we use one repo for k8s, we will split it again. It will be more painful to do this.</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small">2. Normally, the kolla-docker, kolla-ansible and kolla-k8s has less relations between</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"> each other. We need decouple them. So split the repo will be helpful for that. then</div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"> different reviewer/committer cloud focus on her own domain.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 3, 2016 at 11:48 PM, Steven Dake (stdake) <span dir="ltr"><<a href="mailto:stdake@cisco.com" target="_blank">stdake@cisco.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Paul,<br>
<br>
Just to be clear, we are not putting master on pause for 4-6 weeks to<br>
split apart the repos to enable kubernetes development. The option on the<br>
table at this point are<br>
A) kolla repo as it exists today and empty repo for k8s<br>
B) kolla repo as it exists today with kubernetes integrated<br>
<br>
A pause would essentially kill any kubernetes effort. Plus there is a<br>
whole bunch of reasons why not to split the main kolla repo. The fact<br>
that our tools don't work well for this means that developers are less<br>
likely to go through backporting bug fixes, which means our stable<br>
branches may fall into disrepair.<br>
<br>
Keep in mind, our stable branches fell into disrepair last time because of<br>
tools. We were not using launchpad correctly as a team, which we are now<br>
doing. As a result back-porting is consistently done and done well. A<br>
bunch of manual backports will result in a lower quality code base and I<br>
have concerns folks wouldn't end up backporting - or worse make errors<br>
since the process would no longer be automated.<br>
<br>
Regards<br>
-steve<br>
<div class="HOEnZb"><div class="h5"><br>
On 5/3/16, 2:23 AM, "Paul Bourke" <<a href="mailto:paul.bourke@oracle.com">paul.bourke@oracle.com</a>> wrote:<br>
<br>
>Having read through the full thread I'm still in support of separate<br>
>repos. I think the explanations Jeff Peeler and Adam Young have put<br>
>forward summarise my thoughts very well.<br>
><br>
>One of the main arguments I seem to be hearing for a single repo is Git<br>
>tooling which I don't think is a good one; we should do what's best for<br>
>users and devs, not for tools.<br>
><br>
>Also as the guys pointed out, multiple repos are the most common pattern<br>
>across OpenStack. I think it will help keep a better separation of<br>
>concerns. Otherwise in my experience you start to get cross<br>
>contamination of the projects, to the point where it becomes extremely<br>
>difficult to pull them apart.<br>
><br>
>The images, ansible, and k8n need to be separate. The alternative is not<br>
>scalable.<br>
><br>
>Thanks,<br>
>-Paul<br>
><br>
>On 03/05/16 00:39, Angus Salkeld wrote:<br>
>> On Mon, May 2, 2016 at 7:07 AM Steven Dake (stdake) <<a href="mailto:stdake@cisco.com">stdake@cisco.com</a><br>
>> <mailto:<a href="mailto:stdake@cisco.com">stdake@cisco.com</a>>> wrote:<br>
>><br>
>> Ryan had rightly pointed out that when we made the original proposal<br>
>> 9am morning we had asked folks if they wanted to participate in a<br>
>> separate repository.<br>
>><br>
>> I don't think a separate repository is the correct approach based<br>
>> upon one off private conversations with folks at summit. Many<br>
>> people from that list approached me and indicated they would like to<br>
>> see the work integrated in one repository as outlined in my vote<br>
>> proposal email. The reasons I heard were:<br>
>><br>
>> * 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<br>
>> happened during kolla-mesos<br>
>> * A second repository makes k8s a second class citizen deployment<br>
>> 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<br>
>>history<br>
>><br>
>> I favor of the separate repositories I heard<br>
>><br>
>> * It presents a unified workspace for kubernetes alone<br>
>> * Packaging without ansible is simpler as the ansible directory<br>
>> need not be deleted<br>
>><br>
>> There were other complaints but not many pros. Unfortunately I<br>
>> failed to communicate these complaints to the core team prior to the<br>
>> 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<br>
>> want to work on an offshoot repository and open us up to the<br>
>> possible problems above.<br>
>><br>
>><br>
>> +1 to the separate repo<br>
>><br>
>> I think the separate repo worked very well for us and would encourage<br>
>> you to replicate that again. Having one repo doing one thing makes the<br>
>> goal of the repo obvious and makes the api between the images and<br>
>> deployment clearer (also the stablity of that<br>
>> api and things like permissions *cough* drop-root).<br>
>><br>
>> -Angus<br>
>><br>
>><br>
>> If you are on this list:<br>
>><br>
>> * Ryan Hallisey<br>
>> * Britt Houser<br>
>><br>
>> * mark casey<br>
>><br>
>> * Steven Dake (delta-alpha-kilo-echo)<br>
>><br>
>> * Michael Schmidt<br>
>><br>
>> * Marian Schwarz<br>
>><br>
>> * Andrew Battye<br>
>><br>
>> * Kevin Fox (kfox1111)<br>
>><br>
>> * Sidharth Surana (ssurana)<br>
>><br>
>> * Michal Rostecki (mrostecki)<br>
>><br>
>> * Swapnil Kulkarni (coolsvap)<br>
>><br>
>> * MD NADEEM (mail2nadeem92)<br>
>><br>
>> * Vikram Hosakote (vhosakot)<br>
>><br>
>> * Jeff Peeler (jpeeler)<br>
>><br>
>> * Martin Andre (mandre)<br>
>><br>
>> * Ian Main (Slower)<br>
>><br>
>> * Hui Kang (huikang)<br>
>><br>
>> * Serguei Bezverkhi (sbezverk)<br>
>><br>
>> * Alex Polvi (polvi)<br>
>><br>
>> * Rob Mason<br>
>><br>
>> * Alicja Kwasniewska<br>
>><br>
>> * sean mooney (sean-k-mooney)<br>
>><br>
>> * Keith Byrne (kbyrne)<br>
>><br>
>> * Zdenek Janda (xdeu)<br>
>><br>
>> * Brandon Jozsa (v1k0d3n)<br>
>><br>
>> * Rajath Agasthya (rajathagasthya)<br>
>> * Jinay Vora<br>
>> * Hui Kang<br>
>> * Davanum Srinivas<br>
>><br>
>><br>
>><br>
>> Please speak up if you are in favor of a separate repository or a<br>
>> unified repository.<br>
>><br>
>> The core reviewers will still take responsibility for determining if<br>
>> we proceed on the action of implementing kubernetes in general.<br>
>><br>
>> Thank you<br>
>> -steve<br>
>><br>
>>_________________________________________________________________________<br>
>>_<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe:<br>
>> <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>
>><br>
>><<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://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>
>><br>
>><br>
>>_________________________________________________________________________<br>
>>_<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe:<br>
>><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>
>__________________________________________________________________________<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>
__________________________________________________________________________<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"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><span style="font-size:13px;border-collapse:collapse"><font face="monospace, monospace">Regards,</font></span></div><div><span style="font-size:13px;border-collapse:collapse"><font face="monospace, monospace">Jeffrey Zhang</font></span></div><div><span style="font-family:monospace,monospace;font-size:12.8px">Blog: </span><a href="http://xcodest.me/" style="font-family:monospace,monospace;font-size:12.8px" target="_blank">http://xcodest.me</a><font face="monospace, monospace"><br></font></div></div></div></div></div></div></div></div></div>
</div>