<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"><br></div><div class="gmail_default"><font face="monospace, monospace">Thanks to all guys.</font></div><div class="gmail_default"><font face="monospace, monospace"><br></font></div><div class="gmail_default"><font face="monospace, monospace">The mail is a little off-topic. First of all, let us back to the topic of this</font></div><div class="gmail_default"><font face="monospace, monospace">mail.</font></div><div class="gmail_default"><font face="monospace, monospace"><br></font></div><div class="gmail_default"><font face="monospace, monospace"><br></font></div><div class="gmail_default"><font face="monospace, monospace">**kolla-kubernetes**</font></div><div class="gmail_default"><font face="monospace, monospace"><br></font></div><div class="gmail_default"><font face="monospace, monospace">The root issue for kolla-kubernetes is no active contributors. if more person</font></div><div class="gmail_default"><font face="monospace, monospace">is interested in this project, I would like to give more time to this project.</font></div><div class="gmail_default"><font face="monospace, monospace">But leave it in kolla governance may not good for its growth. Because it is a</font></div><div class="gmail_default"><font face="monospace, monospace">**totally different** technical stack with kolla-ansible. so migrate it to TC</font></div><div class="gmail_default"><font face="monospace, monospace">governance should the best solution.</font></div><div class="gmail_default"><font face="monospace, monospace"><br></font></div><div class="gmail_default"><font face="monospace, monospace"><br></font></div><div class="gmail_default"><font face="monospace, monospace">**for kolla and kolla-ansible split**</font></div><div class="gmail_default"><font face="monospace, monospace"><br></font></div><div class="gmail_default"><font face="monospace, monospace">kolla(container) is widely used by multi-project (TripleO, OSH). And I also</font></div><div class="gmail_default"><font face="monospace, monospace">heard some internal projects are using it too. kolla and kolla-ansible are well</font></div><div class="gmail_default"><font face="monospace, monospace">decoupled. The usage or the API kolla provides always stable and backward</font></div><div class="gmail_default"><font face="monospace, monospace">compatible. kolla images are also used in many produce environment through</font></div><div class="gmail_default"><font face="monospace, monospace">different deployment tools So kolla(container) is worth say "provide</font></div><div class="gmail_default"><font face="monospace, monospace">production-ready containers". This should not be negative, just because of</font></div><div class="gmail_default"><font face="monospace, monospace">kolla and kolla-ansible are under the same team governance.</font></div><div class="gmail_default"><font face="monospace, monospace"><br></font></div><div class="gmail_default"><font face="monospace, monospace">the team split would let people fouse on one thing and make it looks better.</font></div><div class="gmail_default"><font face="monospace, monospace">but we have two different teams, kolla-core team, and the kolla-ansible-core team</font></div><div class="gmail_default"><font face="monospace, monospace">already. anyone is welcome to join one of the team. But in fact, the members</font></div><div class="gmail_default"><font face="monospace, monospace">of these two teams are almost the same. <span style="color:rgb(34,34,34);font-family:monospace,monospace;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">if we split the team now, a</span>ll we gain</font></div><div class="gmail_default"><font face="monospace, monospace">is making chaos </font><span style="font-family:monospace,monospace">and hard to manage</span>.</div><div class="gmail_default"><font face="monospace, monospace"><br></font></div><div class="gmail_default"><font face="monospace, monospace">I think it may be proper time when the members of kolla-core team and</font></div><div class="gmail_default"><font face="monospace, monospace">the kolla-ansible-core team is different (50% maybe?).</font></div><div class="gmail_default" style="font-family:monospace,monospace;font-size:small"></div><br><div><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Apr 1, 2018 at 7:16 AM, Jeremy Stanley <span dir="ltr"><<a href="mailto:fungi@yuggoth.org">fungi@yuggoth.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2018-03-31 22:07:03 +0000 (+0000), Steven Dake (stdake) wrote:<br>
[...]<br>
<span>> The problems raised in this thread (tension - tight coupling -<br>
> second class citizens - stratification) was predicted early on -<br>
> prior to Kolla 1.0. That prediction led to the creation of a<br>
> technical solution - the Kolla API. This API permits anyone to<br>
> reuse the containers as they see fit if they conform their<br>
> implementation to the API. The API is not specifically tied to<br>
> the Ansible deployment technology. Instead the API is tied to the<br>
> varying requirements that various deployment teams have had in the<br>
> past around generalized requirements for making container<br>
> lifecycle management a reality while running OpenStack services<br>
> and their dependencies inside containers.<br>
</span>[...]<br>
<br>
Thanks! That's where my fuzzy thought process was leading. Existence<br>
of a stable API guarantee rather than treating the API as "whatever<br>
kolla-ansible does" significantly increases the chances of other<br>
projects being able to rely on kolla's images in the long term.<br>
<span class="gmail-m_8331631354044421054HOEnZb"><font color="#888888">--<br>
Jeremy Stanley<br>
</font></span><br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail-m_8331631354044421054gmail_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">http://xcodest.me</a><font face="monospace, monospace"><br></font></div></div></div></div></div></div></div></div></div>
</div></div></div></div></div></div>