<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Mar 13, 2017 at 2:15 PM, Jerald Sheets <span dir="ltr"><<a href="mailto:questy@gmail.com" target="_blank">questy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">> My measly 100+ systems are all basically different systems with different design needs.<br>
<br>
</span>I think we’ve reached the point in our relationship that I can suggest that if the above sentence is the case, there’s a likelihood you’re doing it wrong.<br>
<br>
(from the automation department)</blockquote></div><br>To follow up on that. I have groups of "same design" systems, but even for my one-of-a-kind systems I write an Ansible playbook. The advantages of Ansible apply to single systems just as much as they do to a group of same systems. I'm not a fan of YAML, but it is far easier to update a YAML file than it is a Bash/whatever script. Plus, the playbook acts as a description of what the system is as a whole.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Also, for the people that do, or want to, use Ansible: I have a Yeoman generator available for bootstrapping new Ansible projects -- <a href="https://www.npmjs.com/package/generator-ansible-bare">https://www.npmjs.com/package/generator-ansible-bare</a><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">James Sumners<br><a href="http://james.sumners.info/" target="_blank">http://james.sumners.info/</a> (technical profile)<br><a href="http://jrfom.com/" target="_blank">http://jrfom.com/</a> (personal site)<br><a href="http://haplo.bandcamp.com/" target="_blank">http://haplo.bandcamp.com/</a> (music)</div>
</div></div>