haroldgsm
Member
Grumpy Old Sysadmin
- Joined:
- May 2024
- Posts:
- 329
- From:
- Ohio, US
Twenty years in this business, and I've watched "solutions" come and go. Kids these days want abstraction over abstraction. Mark my words: your Ansible playbook will rot in eighteen months when someone pins an incompatible Python version, and you'll be debugging Jinja2 templates at 3 AM while the site burns. The pessimist's truth: there is no clean answer, only different messes.
IPv4, IRC, and irssi — fight me
garykwh
Member
Inference on a Budget
- Joined:
- Jun 2024
- Posts:
- 173
- From:
- San Jose, US
Ngl for LLM inference clusters I just need port 22 and the API port open, everything else is internal VPC. VRAM math says I'd rather spend brain cycles on batch sizing than firewall rules. That said, @pablo's ansible approach sounds smart for mixed fleets. I stole a similar role for my homelab — handles docker's iptables mess too.
CUDA cores are my love language
haroldgsm
Member
Grumpy Old Sysadmin
- Joined:
- May 2024
- Posts:
- 329
- From:
- Ohio, US
~40 edge nodes across three providers
Three providers means three bills, three support queues, and three ways to get burned when one of them "restructures" their API. I've been there. The real problem isn't the firewall tool, it's the heterogeneity. Pick one provider, standardize on one OS, and your "problem" evaporates. But nobody wants to hear that because it involves work.
IPv4, IRC, and irssi — fight me
ana_mad
Member
- Joined:
- Jun 2024
- Posts:
- 298
- From:
- Madrid, ES
I manage a similar setup, smaller though — about 15 boxes, mix of Contabo in Nuremberg and some Hetzner Falkenstein leftovers. I went with nftables everywhere and a simple shell script pushed via ssh. No Python, no Jinja2, no galaxy tags. Just
nft -f
and a file in
/etc/nftables.conf
. Debian 10 has backports for nftables, by the way. Your "ancient" box might not be as stuck as you think.
swimming upstream since 2019 🐟
garykwh
Member
Inference on a Budget
- Joined:
- Jun 2024
- Posts:
- 173
- From:
- San Jose, US
Handles docker's iptables mess too
Yeah so about that — the ansible role I stole actually *broke* docker networking twice because it flushes FORWARD. Had to add a
keep_docker_chains: true
flag or whatever. Just warning
@pablo and anyone else, test your API containers before you pat yourself on the back.
CUDA cores are my love language