6 ms·
do you have an ansible playbook for doing that at hand?
by code_research 10y ago
do you have an ansible playbook for doing that at hand?
- feld 10y agoI know I'm going to get backlash for this, but whatever <rant> The article and the docs make it pretty clear that this can be accomplished with a couple shell commands. I don't understand why everyone begs for handouts these days. We now have an entire generation of "sysadmins" who refuse the read documentation and can't produce original work. This is not complicated. You do not need a Master's to figure this out. </rant> That said, I'm quite certain that Ansible does not support IP namespaces natively, so you'll have to manage this with custom "command:" statements. This means these will fire every time you run the Ansible playbook and they will be listed as an item that changed because Ansible does not internally know how to validate whether or not it needs to take action. tl;dr read the docs, write a shell script, and/or figure out the most sane way to do this with ansible/salt/puppet/chef/cfengine/whatever because it's 2016 and I'm tired of people begging for someone else to do their work for them.
- SEJeff 10y agoAka get off my lawn or: http://i.imgur.com/91sn32Q.jpg http://i.imgur.com/91sn32Q.jpg