[openstack-dev] [tc] [all] TC Report 18-26

Fox, Kevin M Kevin.Fox at pnnl.gov
Tue Jul 3 19:48:17 UTC 2018

I don't dispute trivial, but a self hosting k8s on bare metal is not incredibly hard. In fact, it is easier then you might think. k8s is a platform for deploying/managing services. Guess what you need to provision bare metal? Just a few microservices. A dhcp service. dhcpd in a daemonset works well. some pxe infrastructure. pixiecore with a simple http backend works pretty well in practice. a service to provide installation instructions. nginx server handing out kickstart files for example. and a place to fetch rpms from in case you don't have internet access or want to ensure uniformity. nginx server with a mirror yum repo. Its even possible to seed it on minikube and sluff it off to its own cluster.

The main hard part about it is currently no one is shipping a reference implementation of the above. That may change...

It is certainly much much easier then deploying enough OpenStack to get a self hosting ironic working.


From: Jay Pipes [jaypipes at gmail.com]
Sent: Tuesday, July 03, 2018 10:06 AM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [tc] [all] TC Report 18-26

On 07/02/2018 03:31 PM, Zane Bitter wrote:
> On 28/06/18 15:09, Fox, Kevin M wrote:
>>   * made the barrier to testing/development as low as 'curl
>> http://......minikube; minikube start' (this spurs adoption and
>> contribution)
> That's not so different from devstack though.
>>   * not having large silo's in deployment projects allowed better
>> communication on common tooling.
>>   * Operator focused architecture, not project based architecture.
>> This simplifies the deployment situation greatly.
>>   * try whenever possible to focus on just the commons and push vendor
>> specific needs to plugins so vendors can deal with vendor issues
>> directly and not corrupt the core.
> I agree with all of those, but to be fair to OpenStack, you're leaving
> out arguably the most important one:
>      * Installation instructions start with "assume a working datacenter"
> They have that luxury; we do not. (To be clear, they are 100% right to
> take full advantage of that luxury. Although if there are still folks
> who go around saying that it's a trivial problem and OpenStackers must
> all be idiots for making it look so difficult, they should really stop
> embarrassing themselves.)


There is nothing trivial about the creation of a working datacenter --
never mind a *well-running* datacenter. Comparing Kubernetes to
OpenStack -- particular OpenStack's lower levels -- is missing this
fundamental point and ends up comparing apples to oranges.


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe

More information about the OpenStack-dev mailing list