Open Stack

Sorry, missed part of this.

I do not believe there is overlap between openstack-ansible which uses lxc containerization with thick containers and kolla which uses docker/kubernetes with thin containers. These are architecturally very different things and to reference my other email, there are technical reasons for doing things each way.

The Fuel CCP case is different, in that it is doing the same technical thing as kolla. kubernetes managed, docker based thin containers.

Thanks,
Kevin

________________________________
From: Michael Still [mikal at stillhq.com]
Sent: Wednesday, July 27, 2016 5:30 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Kolla] [Fuel] [tc] Looks like Mirantis is getting Fuel CCP (docker/k8s) kicked off

On Tue, Jul 26, 2016 at 4:44 PM, Fox, Kevin M <Kevin.Fox at pnnl.gov<mailto:Kevin.Fox at pnnl.gov>> wrote:

[snip]

The issue is, as I see it, a parallel activity to one of the that is currently accepted into the Big Tent, aka Containerized Deployment

[snip]

This seems to be the crux of the matter as best as I can tell. Is it true to say that the concern is that Kolla believes they "own" the containerized deployment space inside the Big Tent?

Whether to have competing projects in the big tent was debated by the TC at the time and my recollection is that we decided that was a good thing -- if someone wanted to develop a Nova replacement, then let them do it in public with the community. It would either win or lose based on its merits. Why is this not something which can happen here as well?

I guess I should also point out that there is at least one other big tent deployment tool deploying containerized openstack components now, so its not like this idea is unique or new. Perhaps using kubernetes makes it different somehow, but I don't see it.

Michael




--
Rackspace Australia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160727/b47bcec7/attachment.html>