Comment on Feasibility & sanity check: Scaling a P330 Tiny to a 3-node Proxmox cluster
skankhunt42@lemmy.ca 14 hours ago
I don’t know about proxmox but I have 6 4 8GB, 5 lenovo Tiny (i5-4x and i7-8x), and 3 laptops in a k8s cluster and love it. I actually have too many hosts but it’s a lot of fun for me to play on them. Storage is longhorn for anything with a database, everything else is over NFS onto a box I built myself. If you use the *arrs try them over the network and watch the logs. They HATE network storage and will complain a lot. If you don’t have any issues there you should be good.
I haven’t had any issues and just use the 1gb network. As for form factor, I think it’s whatever you have room for. The laptops are annoying but they have the best hardware so I put up with it.
buildmylab@lemmus.org 14 hours ago
Appreciate the reply! I’ve been running this Tiny for 2 years now and it’s been rock solid. My main hesitation is really finding the right price-to-performance sweet spot between compute and storage. Does this 3-node + Synology setup feel like a sensible middle ground, or am I overpaying/overthinking it?
Everything is super expensive these days which is why I’ve got all kinds of nodes. I lurk marketplace, kijiji, etc for “broken” or “for parts” nodes. Laptops with broken keyboards, screens, no battery, etc are perfect for me. I7 11th gen was $90 CAD. Works perfectly for a node. Found a cheap tiny with a locked bios. Removed the CMOS battery to reset and I’m good to go.
If you’re not willing to do that, the working tinys are perfect in my opinion.
The working Synology seems extra to me. You could use software like ceph, or diy it. Storage boxes don’t need crazy specs, just sata ports and power. The only reason I’d consider it is if you just want something “simple that works” and you’re willing to pay for it.
buildmylab@lemmus.org 13 hours ago
That makes a lot of sense. I already have a Synology DS920+, so there’s no additional storage hardware cost on my end. The Tiny form factor is ideal for me mainly due to footprint and low noise, but total cost and idle power are definitely things I’m weighing.
Another route I’m considering is picking up just one more Tiny instead of two, and running an external Corosync QDevice directly on the DS920+ (via a lightweight Docker container) for the tiebreaker vote. That gives me a proper 2-node quorum without the hardware cost and power draw of a third physical node. Combined with the DS920+ for shared iSCSI storage, that might actually hit the sweet spot between cost, footprint, and HA.
If you only have 2 and 1 fails, you’ll need to make sure the remaining one can take on 100% of the workload. If you’ve already maxed one and want HA, I’d suggest adding 2 more. Otherwise you’ll need to decide what services are down while you repair