Build your own bare-metal ARM cluster
blog.alexellis.io
Build your own bare-metal ARM cluster
1–10 of 38 posts
Re: Build your own bare-metal ARM cluster
#2Re: Build your own bare-metal ARM cluster
#3Re: Build your own bare-metal ARM cluster
#4Re: Build your own bare-metal ARM cluster
#5This is going to be a stupid question...but what does clustering do? Does it increase the amount of "cores" in a system? What about the RAM? Or is the clustering software a task manager that allocates different boards as needed depending on the the task load?
But...
There is a price to pay. Clustering isn't easy, convenient or without overhead. As soon as you cross the boundaries of what a single machine can give everything suddenly has a price, either in terms of latency, throughput, complexity or loss of control. Clustering software tries to hide some of this but under the hood these will always be there.
Here are some good hints about what limitations you are operating under no matter how good your distributed environment:
https://en.wikipedia.org/wiki/Fallacies_of_distributed_compu...
Re: Build your own bare-metal ARM cluster
#6https://thenewstack.io/how-low-can-kubernetes-go-rancher-arm...
Re: Build your own bare-metal ARM cluster
#7Re: Build your own bare-metal ARM cluster
#8Of course back then Docker didn't run on Pi, but other clustering software did.
Re: Build your own bare-metal ARM cluster
#9That being said, I had to buy an Asus Tinkerboard with 2GB RAM to serve as the cluster master because 1GB RAM was a bit short. My master node went below 100MB of free RAM and pod evictions (of kube-system pods) started to happen. If I were to do it again, I think I would use only Tinkerboards just for the convenience of having the same OS/hardware on each node.
[0] https://gist.github.com/alexellis/fdbc90de7691a1b9edb545c17d...