Completely agree. I haven’t met a single person that has genuinely liked it. But they feel compelled to use it and speak highly of it because it’s what you do in the industry. And a lot of the people that do keep pushing for it keep acting like it’s going to be the single solution that fixes everything somehow magically…
And I don’t know about you, but I know an excessive number of people it seem to think that if you want to idempotent then it has to be ansible… As if suggesting that it’s impossible to be idempotent by any other means.
I really like Ansible and have used it for my personal dotfiles for years. I don’t think it’s a silver bullet and I’m aware of a lot of the criticism. Containerization or immutable infra solves more production problems so I don’t really use it much at work.
At least in the devops/SRE circles I work in, we know there are different tools for different jobs. While we might fight about which is the best, I haven’t seen the ossification you’re describing.
What do you like about ansible? I guess it abstracts away the need to check for OS/init system? How else does it help in place of shell scripts?
Also after using NixOS, it’s amazing what NixOS does and disappointing that ansible is not so great for deterministic config [1], its more or less a batch of commands executed together. The closest thing, to NixOS, I’ve been able to achieve is load a variables file in playbook.yml and enable/disable service or install/purge pkg based on variables declared. I might be nitpicking/wrong given I’ve not been using long enough but directory layout is kinda too verbose. I say that because it’ll get really messy very quickly when writing modules for more services. NixOS is great, you only have to have configuration.nix or flake.nix+flake.lock too (if using flakes) and rest you can import however you like.
I know that nix stores its state in /nix and ansible doesn’t have any such assumption about the target host so it can’t rollback to previous state ↩︎
I like how simple it is. It’s made distrohopping very, very simple for me over the years. The only pet machines I have are my actual dev boxes. The rest are cattle I manage with other tools. Galaxy has also made it much simpler to consume other Ansible which used to be really annoying.
I’m on the fence about Nix. When I first saw years ago it was yet another package management system. I’ve seen enough interesting things with it now that I’ll probably try it out the next time I want to rebuild my configs from scratch.
Completely agree. I haven’t met a single person that has genuinely liked it. But they feel compelled to use it and speak highly of it because it’s what you do in the industry. And a lot of the people that do keep pushing for it keep acting like it’s going to be the single solution that fixes everything somehow magically…
And I don’t know about you, but I know an excessive number of people it seem to think that if you want to idempotent then it has to be ansible… As if suggesting that it’s impossible to be idempotent by any other means.
I really like Ansible and have used it for my personal dotfiles for years. I don’t think it’s a silver bullet and I’m aware of a lot of the criticism. Containerization or immutable infra solves more production problems so I don’t really use it much at work.
At least in the devops/SRE circles I work in, we know there are different tools for different jobs. While we might fight about which is the best, I haven’t seen the ossification you’re describing.
What do you like about ansible? I guess it abstracts away the need to check for OS/init system? How else does it help in place of shell scripts?
Also after using NixOS, it’s amazing what NixOS does and disappointing that ansible is not so great for deterministic config [1], its more or less a batch of commands executed together. The closest thing, to NixOS, I’ve been able to achieve is load a variables file in playbook.yml and enable/disable service or install/purge pkg based on variables declared. I might be nitpicking/wrong given I’ve not been using long enough but directory layout is kinda too verbose. I say that because it’ll get really messy very quickly when writing modules for more services. NixOS is great, you only have to have configuration.nix or flake.nix+flake.lock too (if using flakes) and rest you can import however you like.
I know that nix stores its state in /nix and ansible doesn’t have any such assumption about the target host so it can’t rollback to previous state ↩︎
I like how simple it is. It’s made distrohopping very, very simple for me over the years. The only pet machines I have are my actual dev boxes. The rest are cattle I manage with other tools. Galaxy has also made it much simpler to consume other Ansible which used to be really annoying.
I’m on the fence about Nix. When I first saw years ago it was yet another package management system. I’ve seen enough interesting things with it now that I’ll probably try it out the next time I want to rebuild my configs from scratch.