3 ms·
Perhaps relevant - how's Ansible doing these days, given that it's a Red Hat tool now?
by bovermyer 3y ago
Perhaps relevant - how's Ansible doing these days, given that it's a Red Hat tool now?
- SSLy 3y agoAs slow to execute as ever. Salt was the better future.
- bamfly 3y agoI went with Ansible way back when all these were fairly new, because it was not just possible, but considered "culturally", if you will, normal, in that ecosystem, to run it agentless. Having to run a config agent on the target system always felt like a smell, and begging for trouble. But yaml's friggin' terrible, that's simply true.
- placatedmayhem 3y agoAgreed. Puppet Bolt has been better to me than Ansible, especially around Playbook YAML vs the Puppet DSL. Puppet seemed to fall out of the limelight when Ansible made it big, then Bolt got little love.
- 5e92cb50239222b 3y agoI find it ok as long as you're using persistent connections (which also significantly reduce connection time for all other SSH sessions). Add something like this to ~/.ssh/config: ControlMaster auto ControlPath ~/.ssh/persist/%r@%h:%p ControlPersist 15m
- thecosmicfrog 3y agoWhat happened to Salt? I felt like it was everywhere in 2015, but I almost never hear of it anymore. Even their official documentation site has an ad promoting "SaltConf 2021", a conference from nearly two years ago.
- ojhughes 3y agoTerraform and Docker have been eating Ansibles lunch for some time now. Even OpenShift stopped using it as an installation method
- jake_morrison 3y agoAnsible is still the best for tactical automation tasks. The syntax is also approachable for people who don't use it often, e.g. developers. Ansible has poor performance on larger tasks. Idempotency checks to see whether an action needs to be executed require manual work to set up and time to execute. This also makes it slow to work with cloud resources. I switched to Terraform years ago for low-level resource provisioning and cloud automation. I still occasionally use it in conjunction with Packer to create AMIs. The shift to containerized application deployment makes Ansible much less relevant in general. Dockerfiles are bad at idempotency, but the solution is probably not Ansible.
- geerlingguy 3y agoDefinitely a fair take; I think Ansible still has a place in containerized environments, but the nice thing is it can play a large or small role depending on how much you want to learn other tools which might be better at a specific automation segment (like Terraform for infra resources).
- jake_morrison 3y agoThanks for your service supporting the Ansible community. Your books are also great, and I highly recommend them to anyone learning Ansible.
- tetha 3y agoWe're using it to provision the Vms hosting our container platform besides some terraform/packer for allocating the VMs and such. It works, and doesn't suck much more or less than other configuration systems. A big discussion point internally is just speed at even medium scales. I don't know why something like Mitogen is not built-in, as Mitogen is the difference between 12 - 15 minute runs vs 3 minutes flat, even though it has enough other problems.This is growing into some degree of resentment against the tool in the team. There is some murmuring that puppet might just be better to maintain the solid foundation of a fleet of linux systems, after chef was monetized and such. I'm going to send a colleague the idea of persistent connections to test though.