I have a five node Deco wifi mesh network. I reserve almost all of my IP addresses on that by MAC Address so that i get static addresses but i don’t have to manually configure each host. The only user interface for this DHCP address reservation is on an app on my phone, which is fiddly and irritating. That’s the first thing that i’d like to change.
After that the next big deal on my home network is my main NAS “farnsworth”. It’s a 6-bay QNAP with six 10Tb drives in it. It’s pretty central to everything in my house. It’s running Plex as a docker container in QNAP’s docker solution that they call “Container Station”. I’d like to move Plex somewhere else with a GPU so that it can transcode videos for smoother playback.
Then i have a three node Proxmox cluster comprised of donbot, joey and clamps. Their main purpose is to host my nine node k3s cluster. That k3s cluster is where i’m running all of my containers. I’ve re-imagined my container hosting platform many times over the years. Basically, as soon as i get settled with one solution i find out that other people are doing something cleverer than me, so i start learning that approach and moving to that. I started with shell scripts, then went to docker compose files, and i’m currently using k3s. There’s lots more for me to learn with k3s, so i think i’ll be on this for a while.
I should mention that these hostnames are all Futurama characters. I find it very helpful to give hosts memorable names.
On a proxmox host called “sal” i can run different VMs as i want to try things out, but most of the time “frankie” is the Ubuntu machine that I do my development on. On it I clone my repositories, and from there I can stand up containers for development or control what’s happening in that k3s cluster, including building it from scratch. I mostly just ssh to it and run stuff in a terminal, but using the Remote SSH extension in VSCode makes for a pretty flawless experience.
Oh, on farnsworth i’m also hosting a docker registry. I build images on frankie and push them into that registry so that the k3s cluster can pull those images and provision containers.
Another container that runs in that k3s cluster is for backups. It runs backups of databases and web sites for me, but it also checks to see if cubert or dwight are online. If they are it runs rsync backups from farnsworth to them.
This is what it looks like at the moment (ignore the actual shoes o the shoe rack)…
I’m thinking of designing and printing an enclosure for donbot, joey and clamps that can nearly accommodate their power bricks and that GPU that’s just dangling out of the back of joey.
Anyway, looking forward to hearing other people’s impressions.
That lop-sided stand for that LCD display is starting to bug me now that it’s in a photo 