<div dir="ltr">Hi Gema,<br><br><div class="gmail_quote"><div dir="ltr">On Thu, Mar 29, 2018 at 2:48 PM Gema Gomez <<a href="mailto:gema@ggomez.me">gema@ggomez.me</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
On 29/03/18 18:26, Richard Wellum wrote:<br>
> Hi,<br>
><br>
> So as a current Kolla-Kubernetes Core - I have a slightly different<br>
> opinion than most, I'll try to verbalize it coherently.<br>
><br>
> Lets talk about what Kolla is:<br>
><br>
> Kolla is a project that builds OpenStack docker images, stores them on<br>
> dockerhub, and provides tools to build your own images from your own<br>
> source. Both the images and the tools it provides, are widely used, very<br>
> popular and extremely stable; TripleO, openstack-helm and kolla-ansible<br>
> to name a few are all deployment methods that use Kolla.<br>
><br>
> Kolla has two sub-projects, that both revolve around deployment methods;<br>
> kolla-ansible and kolla-kubernetes. Kolla-ansible is proven, stable and<br>
> used by many in the industry. Part of Kolla's quality is it's rock-solid<br>
> dependability in many scenarios. As Kubernetes took over most of the COE<br>
> world, it's only correct that the Kolla team created this sub-project;<br>
> if swarm became suddenly very popular then we should create a<br>
> kolla-swarm sub-project.<br>
><br>
> So if we abandon kolla-kubernetes ('sunset' seems much more romantic<br>
> admittedly) - we are abandoning the core Kolla team's efforts in this<br>
> space. No matter how good openstack-helm is (and I've deployed it, know<br>
> a lot of the cores and it's truly excellent and well driven), what<br>
> happens down the line if openstack-helm decide to move on from Kolla -<br>
> say focussing on Loci images or a new flavor that comes along? Then<br>
> Kolla the core project, will no longer have any validation of it's<br>
> docker images/containers running on Kubernetes. That to me is the big<br>
> risk here.<br>
><br>
> The key issue in my opinion is that the core Kolla team has focussed on<br>
> kolla-ansible almost exclusively, and have not migrated to using<br>
> kolla-kubernetes as well. As the code base has stagnated, the gates get<br>
> intro trouble, and new features and configurations added to<br>
> kolla-ansible are not translated to kolla-kubernetes.<br>
><br>
> So I think the real question is not whether we should 'sunset'<br>
> kolla-kubernetes the sub-project, but should we drop Kolla support on<br>
> Kubernetes? Relying on a different team to do so is probably not the<br>
> answer; although it's the one championed in this thread.<br>
><br>
> In my opinion we should set some realistic goals before we sunset:<br>
><br>
> 1. Pick a feature set for a Rocky v1.0 release, and commit to trying to<br>
> get there. We have a long list of items, maybe pair this down to<br>
> something reasonable.<br>
<br>
Are you volunteering to drive this effort forward? I'd be happy to help<br>
define MVP for Rocky.<br></blockquote><div><br></div><div>Yes I am.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
> 2. Agreement within Kolla core team to learn kolla-kubernetes and start<br>
> to put a percentage of time into this sub-project.<br>
<br>
Whilst this would be ideal, we cannot really force people that have no<br>
interest in this sub-project to contribute.<br></blockquote><div> </div><div>That's not what I was inferring, more trying to get a shift in attitude within the Kolla team. For example, if I am working on kolla-kubernetes, and make a change that breaks kolla-ansible - the Kolla community would expect me to fix it of course? Same if I added a feature, and didn't apply and test it with kolla-ansible then the same no? So I'm just saying that the same should apply in the other direction; which it is currently not. As a community we should support both deployment methods. Or if we don't then we are all agreeing that Kolla will not have support on Kubernetes from the core Kolla community.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
> 3. Identify the people who are genuinely interested in working with it<br>
> within the Kolla team.<br>
<br>
+1 if we find enough contributors to make the reasonable list of items<br>
happen during Rocky.<br>
<br>
> Without '2' I think sunsetting is the way forward, but the risks should<br>
> be fully understood and hopefully I've made a case for what those are above.<br>
<br>
How many contributors are necessary to make MVP?<br></blockquote><div>We were doing fairly well with 4-5 contributors imo.</div><div><br></div><div>Thanks,</div><div><br></div><div>||Rich</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Cheers,<br>
Gema<br>
<br>
><br>
> Thanks,<br>
><br>
> ||Rich<br>
><br>
><br>
> On Wed, Mar 28, 2018 at 1:54 PM Chuck Short <<a href="mailto:zulcss@gmail.com" target="_blank">zulcss@gmail.com</a><br>
> <mailto:<a href="mailto:zulcss@gmail.com" target="_blank">zulcss@gmail.com</a>>> wrote:<br>
><br>
> +1<br>
><br>
> Regards<br>
> chuck<br>
> On Wed, Mar 28, 2018 at 11:47 AM, Jeffrey Zhang<br>
> <<a href="mailto:zhang.lei.fly@gmail.com" target="_blank">zhang.lei.fly@gmail.com</a> <mailto:<a href="mailto:zhang.lei.fly@gmail.com" target="_blank">zhang.lei.fly@gmail.com</a>>> wrote:<br>
><br>
> There are two projects to solve the issue that run OpenStack on <br>
> Kubernetes, OpenStack-helm, and kolla-kubernetes. Them both<br>
> leverage helm tool for orchestration. There is some different<br>
> perspective<br>
> at the beginning, which results in the two teams could not work<br>
> together. <br>
><br>
> But recently, the difference becomes too small. and there is<br>
> also no active<br>
> contributor in the kolla-kubernetes project. <br>
><br>
> So I propose to retire kolla-kubernetes project. If you are still<br>
> interested in running OpenStack on kubernetes, please refer to <br>
> openstack-helm project.<br>
><br>
> -- <br>
> Regards,<br>
> Jeffrey Zhang<br>
> Blog: <a href="http://xcodest.me" rel="noreferrer" target="_blank">http://xcodest.me</a> <<a href="http://xcodest.me/" rel="noreferrer" target="_blank">http://xcodest.me/</a>><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://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>
> 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://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>
> 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>
</blockquote><div class="inbox-inbox-Fv" style="color:rgb(33,33,33);font-family:Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:13px"><div class="inbox-inbox-n9" style="padding:0px 20px;display:flex"><div class="inbox-inbox-xY inbox-inbox-Hr" style="display:flex"><div class="inbox-inbox-eF" style="overflow-x:hidden;display:flex"><br class="inbox-inbox-Apple-interchange-newline"><input id="inbox-inbox-btariaid-2528" type="text" class="inbox-inbox-dm" style="border-width:initial;border-style:none;box-sizing:border-box;line-height:20px;overflow-x:auto;overflow-y:hidden;padding:7px 0px;vertical-align:middle;height:35px;width:1px"></div></div></div></div><div class="inbox-inbox-iO" style="border-top:1px solid rgb(224,224,224);margin-top:3px;padding:20px 20px 22px;color:rgb(33,33,33);font-family:Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif;font-size:13px"><input value="Re: [openstack-dev] [kolla][kolla-kubernete][tc][openstack-helm]propose retire kolla-kubernetes project" title="Subject" type="text" class="inbox-inbox-dm" style="font-size:15.6px;border-width:initial;border-style:none;box-sizing:border-box;line-height:20px;overflow-x:auto;overflow-y:hidden;padding:0px;vertical-align:middle;font-weight:bold;height:20px;width:1060px"></div></div></div>