3 ms·
This sounds like buzzword bingo. I can't tell without reading the source, is this any different from minikube? I see a mention of NUCs and netboot in the READM
by web007 9y ago
This sounds like buzzword bingo.
I can't tell without reading the source, is this any different from minikube? I see a mention of NUCs and netboot in the README, so I'm guessing it's slightly more, but not documented.
- mbryant 9y agoThere's a better explanation of what's going on over here: http://ocadotechnology.com/blog/creating-a-distributed-data-centre-architecture-using-kubernetes-and-containers/ http://ocadotechnology.com/blog/creating-a-distributed-data-... There's some libvirt stuff, but that's mostly for local testing without having a bunch of physical hardware. The key things I'm trying to do are: - Automatically provision new machines, just by plugging them in. - Don't have a traditional network (i.e. switches)
- corndoge 9y agoFrom the article, you're using Quagga -- are you aware of the active fork FRRouting[0]? It was forked about 8 months ago and is over 3,000 commits ahead since most of the core developers have stopped developing Quagga. [0] https://github.com/FRRouting/frr https://github.com/FRRouting/frr
- mbryant 9y agoYes, but thanks :) FRRouting took off after I'd already moved on to other things. I've dropped an issue in the repo so I remember, when I get a chance to work on Kubermesh again
- jzelinskie 9y agoNUCs are pretty standard for how many people are testing bare metal installations on the cheap. It's what we use in the labs at CoreOS. This looks like an opinionated installation for an actual bare metal cluster complete with anycast mirrors of popular registries. Minikube is only really good for running in a VM locally.
- dghubble 9y agoJust to clarify - there are a few NUCs, but its mostly SuperMicros and other vendors where testing and qa are done.