Skip to content

What do you use for configuration management across 15 cheap servers?

Dedicated Servers by pauloserver 24 replies 2.8K views
1 #11

rudi3 said:
Puppet is dead. Salt is dead.
Ansible is dead at 40 minutes! I said 200 nodes with salt and it works! You are stuck in 2019!

8 #12

This. Fork count and pipelining. Also set host_key_checking = False if you're rebuilding often.

#13

Ok changed to 25 and down to 12 minutes kkkkk still not 8 but better

chill infrastructure for chill people 🦫
6 #14

12 minutes to what though? If it's just apt update and copy some configs you need to look at what your playbook is actually doing. I had a guy whose "deploy" was downloading a 2GB docker image every run.

Honey badger don't care... about downtime
#15

I run 3 servers for my bakery website and I just ssh in and do it. Am I the only one here who thinks 15 servers sounds like a lot?

#16

For 15 servers I would honestly consider NixOS and deploy-rs. Reproducible, atomic, no agent beyond SSH. But the learning curve is real.

7 #17

NixOS is not bare metal purism, it's a cult. Give me a shell script and a cron job. I have 20 servers across three countries and I manage them with rsync and a for loop.

3 #18

Hel said:
rsync and a for loop
This is how you get drift and 3am pages. No thanks.

#19

Has anyone actually tried running ansible-pull instead of push? For 15 cheap boxes behind NAT it solves a lot of orchestration headaches.

#20

Ansible-pull is underrated. I use it for a remote site in Aberdeen where the VPN is flaky. Boxes phone home when they can.

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft