<div dir="ltr">While I do appreciate/respect the ansible/chef enthusiasm; It'd be considerably harder to get support for deploying something new in the environment that I'm working on. We're already using puppet in our "production" so there are already people interested in getting puppet into the we'll call it a lab. I'm just doing the grunt work. 😉 <div><br></div><div>Mike B</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 17, 2015 at 5:09 PM, Quentin Hartman <span dir="ltr"><<a href="mailto:qhartman@gmail.com" target="_blank">qhartman@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Just going to quickly throw my 0.02 in. Stuff like this is why I abandoned Puppet and ran into the warm embrace of Chef and haven't looked back. Chef isn't perfect by any stretch, but omg, it's a such a pleasure next to Puppet... I haven't really played with Ansible, but I hear it's nice.<span class="HOEnZb"><font color="#888888"><div><br></div><div>QH</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 17, 2015 at 4:22 PM, Chris Fedde <span dir="ltr"><<a href="mailto:chris@fedde.us" target="_blank">chris@fedde.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Ok. I'll crawl back out from under my bridge.<div><br></div><div>You are right. Ansible just uses ssh and python. To do anything useful, the remote system has to trust the remote user. Either by allowing root to ssh directly in or via some su or sudo approach.</div><div>Prior to adopting ansible I was using pssh. First I would pscp a script to the remote systems then I'd pssh to execute it. Still at some level of thought this is pretty much how ansible works.</div><div><br></div><div>The main value that gets added here is that there is a pretty reasonable body of documentation and automaton steps that has already been written. There are a number of organizational features around inventory management, template and execution order that work well for me. Also it is mostly push based which means that it is pretty easy to run from an engineer's workstation. Of course that has benefits and drawbacks too. </div><div><br></div><div>Personally I'm old enough that I think that Perl is still cool. If you also like perl and config mgmt you might like to look at:</div><div><a href="http://www.rexify.org/" target="_blank">http://www.rexify.org/</a><span><font color="#888888"><br></font></span></div><span><font color="#888888"><div><br></div><div>chris </div><div><br></div><div><div><br></div></div></font></span></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 17, 2015 at 2:53 PM, Mike Nolte <span dir="ltr"><<a href="mailto:obiwanmikenolte@gmail.com" target="_blank">obiwanmikenolte@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Nyah-ha! Chris is trolling! I vote CFEngine!<div><br></div><div>I don't want to start a debate, but can you elaborate on why you think that Ansible is better? When you say "overhead," what do you mean?</div><div><br></div><div>I've looked at Ansible a few times, and I've worked through the O'Reilly book, but it was a slog. All I kept thinking was, "This is just root SSH!"</div><div><br></div><div>Also, do you use more Ruby or Python?</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 17, 2015 at 2:33 PM, Chris Fedde <span dir="ltr"><<a href="mailto:chris@fedde.us" target="_blank">chris@fedde.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I'm going to be an ass here and just say "ansible".<div><br></div><div>Puppet is a great tool but I think that it requires too much ceremony and has transformation rules that I can't wrap my head around.</div><div>While I don't consider our investment in puppet to be sunk cost I do think that we could have been farther along if we had invested the same time in ansible.</div><div>Of course about half of our problem with puppet has as much to do with giant company overhead as it does with a</div><div><br></div><div><a href="https://ansible.wistia.com/medias/qrqfj371b6" target="_blank">https://ansible.wistia.com/medias/qrqfj371b6</a><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Thu, Sep 17, 2015 at 2:12 PM, Mike Bean <span dir="ltr"><<a href="mailto:beandaemon@gmail.com" target="_blank">beandaemon@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div>Follow-up:</div><div>It is! It's the bloody camel-casing!</div><div>I created the exact same module/directory structure and called it atest, instead of aTest, and it worked fine! </div><div>Sheesh. </div><div><br></div><div>Sorry for the spam.</div><div><br></div><div>Mike B</div><div><div><div><br></div>---------- Forwarded message ----------<div class="gmail_quote">From: <b class="gmail_sendername">Mike Bean</b> <span dir="ltr"><<a href="mailto:beandaemon@gmail.com" target="_blank">beandaemon@gmail.com</a>></span><br>Date: Thu, Sep 17, 2015 at 2:05 PM<br>Subject: seeking puppet advice<br>To: CLUE's mailing list <<a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a>><br><br><br><div dir="ltr"><br><div>I've been staring at something, looking at google, various books for a couple days now, I don't know what the heck is going on. I've got a prototype puppet server going in a small environment, but I haven't managed to apply a roll-my-own module yet. </div><div><br></div><div>I get </div><div>Error: Could not find class aTest for mul-puppet.xxx on node mul-puppet.xxxx<br></div><div><br></div><div>Interestingly enough, physically specifiying the long path in the site.pp file seems to work</div><div><br></div><div>import '/etc/puppet/modules/aTest/manifests/init.pp'<br></div><div><br></div><div><div>root@mul-puppet:/etc/puppet/manifests# cat /etc/puppet/modules/aTest/manifests/init.pp</div><div>class aTest {}</div></div><div><br></div><div>What I don't understand is why the autoloader can't handle it. I literally have other modules I've copied from books the exact same way, there's only one difference. The module name is camelCase. Is it that simple? does screwing with the case mess with the puppet autoloader?</div><div><br></div><div>Mike B</div></div>
</div><br></div></div></div>
<br></div></div><span>_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" rel="noreferrer" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br></span></blockquote></div><br></div>
<br>_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" rel="noreferrer" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" rel="noreferrer" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" rel="noreferrer" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" rel="noreferrer" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br></blockquote></div><br></div>