ansible is such a waste of time
cluster-ssh is the way to go, even if it’s just in batches of say 9 or 12 or so hosts, even if the total of hosts measures 275
@mirabilos
Unless you *want* to install five different unmaintained scripts for each thing you want do and wind up writing a shell script in yaml anyway.
There are other config management systems that don't require YAML. The ability to be able to say, with actual proof, that all hosts in your configuration are configured the exact same way is not to be underestimated though.
@ohmrun
There are other config management systems that don't require YAML.
Yes, I wrote my own before, using mksh scripts ;)
The ability to be able to say, with actual proof, that all hosts in your configuration are configured the exact same way is not to be underestimated though.
Configuration management as practiced today does not ensure that at all, though. (Unless you delete the VMs and reinstall them every time you change something, which… would be worse in so many other ways.)
@wouter
I think the semi-lattice (correct by construction) based ones are quite interesting, like cuelang or dhall, although I've not had cause to use them seriously.
I'll use babashka until I need more guns, though.
It can, but this depends on the implementation details of your config management configuration, rather than the tool which you use for your config management.
e.g., I once wrote an Ansible playbook that fetched the list of all installed packages and purged those not explicitly whitelisted, then installed the packages that were in the whitelist. That made it possible to assert that all hosts had the exact same list of packages installed.
@ohmrun
- replies
- 0
- announces
- 0
- likes
- 0