4 ms·
As a "devops engineer" cough sysadmin cough, configuration management is still a freaking nightmare. I write too much YAML, I do not know why everyone all at o
by honkycat 8y ago
As a "devops engineer" cough sysadmin cough, configuration management is still a freaking nightmare.
I write too much YAML, I do not know why everyone all at once decided they were done building abstractions and instead wanted to write a ton of boilerplate.
I use ansible currently for our SMALL business. I have thousands of lines of ansible to do relatively simple tasks. YAML is not a programming language, you have to repeat your self over and over again. If you get tired of doing that, you are out of luck. You are not writing in a programming language so you cannot develop an abstraction.
That being said, the main advantage of Ansible is that someone has already gone in and written all of the boilerplate code for provisioning various resources in my cloud provider. Unless OpsMop has this, I don't see the value-add.
- jacobsenscott 8y agoI switched from chef to ansible because in my opinion a DSL is the wrong way to go for this stuff. Granted I've only ever managed fairly small deployments. But so much more can go wrong when you are writing code vs writing yaml. If your yaml parses it will probably work. I write ruby application code everyday and I love ruby. But I hated writing chef scripts. I also ended up with many fewer lines of yaml than ruby.
- scirocco 8y agoRequiring you to be a developer to do automation is not a sustainable strategy. Ansible is a better fit for non-developers to do automation, which helps drive adoption And since it's agentless you can automate almost anything... As mentioned above - the playbooks created by the community avoids you from reinventing the wheel. Companies like Cisco are writing playbook to automate their switches
- rollcat 8y agoShameless plug, you might find judo interesting: https://github.com/rollcat/judo https://github.com/rollcat/judo