News for hackers. Stuff that matters.

A comment on Ansible 2.1 Released, with Network Automation, Containers. Parent comment

Re:Ansible 2.1 Released, with Network Automation, Containers by JTenerife on Thursday May 26, 2016 @01:27PM (#11779815)
Exactly. This whole "declare your environment" thing with Ansible doesn't work.

I've completely mixed experiences with Ansible. Yes, it's easy to get started, but it's certainly annoying having to create playbooks for removing stuff to get a clean state.

[ Parent | on HN ]
Re:Ansible 2.1 Released, with Network Automation, Containers by bovermyer on Thursday May 26, 2016 @10:53PM (#11783566)
To be frank, my experience with configuration management has been a mix between "YES! THIS IS WHAT WE NEED!" and "...but it still doesn't adhere to immutable states." That's been true with Chef, Puppet, and Ansible, for me. I haven't experimented with other techs.
[ Parent | on HN ]
Re:Ansible 2.1 Released, with Network Automation, Containers by jmcnulty on Saturday May 28, 2016 @08:22AM (#11791393)
Depends how you write your playbooks/roles. You can write a role that will both add and remove depending on the value of a variable in your inventory. Then tweak the inventory and re-run.
[ Parent | on HN ]