|
Having used puppet, salt and now Ansible i'll toss in my opinion, not that anyone asked! I used puppet in a place which wasn't using puppet to its fullest potential, its easy and I wrote a few custom modules for it ( installing java a certain way some other stuff ) and its relatively fine. As a more python person I felt it was a bear to use when doing anything ruby related. However I did appreciate the custom facts piece, foreman was also a pretty neat piece of software which gave everything a decent UI to manage from. I didn't like that we needed puppet enterprise to run commands via puppet to a subset of systems, though this might have changed. Salt I really like, it can be extremely fiddly especially when writing templates for the first time. Lots of errors returned are not the most user friendly. I also found that writing automated tests of the code ( mostly spinning up docker containers, applying the code to the container then writing tests ) was tougher than using puppet, since Rspec/Serverspec was so easy to use. However the flexibility I felt in salt is something, especially the reactor system, that is really nice to work with Ansible I've used the least, I'm using it to template AMIs using packer within AWS. It's really strong i feel in this role. I've also written a few libraries for it. I found that to be a bit of a pain from a testing standpoint but this might be outside the scope of the conversation. I like how it provides a way to set something to state and not have an agent, thought I think for longer running systems this could be a disadvantage.
|
#
¿
Aug 15, 2019 17:05
|
|
|
|
| # ¿ May 9, 2024 22:13 |
|