[clue] Fwd: seeking puppet advice

Mike Bean beandaemon at gmail.com
Fri Sep 18 06:08:53 MDT 2015


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. 😉

Mike B

On Thu, Sep 17, 2015 at 5:09 PM, Quentin Hartman <qhartman at gmail.com> wrote:

> 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.
>
> QH
>
> On Thu, Sep 17, 2015 at 4:22 PM, Chris Fedde <chris at fedde.us> wrote:
>
>> Ok.  I'll crawl back out from under my bridge.
>>
>> 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.
>> 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.
>>
>> 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.
>>
>> 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:
>> http://www.rexify.org/
>>
>> chris
>>
>>
>>
>> On Thu, Sep 17, 2015 at 2:53 PM, Mike Nolte <obiwanmikenolte at gmail.com>
>> wrote:
>>
>>> Nyah-ha!  Chris is trolling!  I vote CFEngine!
>>>
>>> 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?
>>>
>>> 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!"
>>>
>>> Also, do you use more Ruby or Python?
>>>
>>> On Thu, Sep 17, 2015 at 2:33 PM, Chris Fedde <chris at fedde.us> wrote:
>>>
>>>> I'm going to be an ass here and just say "ansible".
>>>>
>>>> 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.
>>>> 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.
>>>> Of course about half of our problem with puppet has as much to do with
>>>> giant company overhead as it does with a
>>>>
>>>> https://ansible.wistia.com/medias/qrqfj371b6
>>>>
>>>>
>>>> On Thu, Sep 17, 2015 at 2:12 PM, Mike Bean <beandaemon at gmail.com>
>>>> wrote:
>>>>
>>>>> Follow-up:
>>>>> It is!   It's the bloody camel-casing!
>>>>> I created the exact same module/directory structure and called it
>>>>> atest, instead of aTest, and it worked fine!
>>>>> Sheesh.
>>>>>
>>>>> Sorry for the spam.
>>>>>
>>>>> Mike B
>>>>>
>>>>> ---------- Forwarded message ----------
>>>>> From: Mike Bean <beandaemon at gmail.com>
>>>>> Date: Thu, Sep 17, 2015 at 2:05 PM
>>>>> Subject: seeking puppet advice
>>>>> To: CLUE's mailing list <clue at cluedenver.org>
>>>>>
>>>>>
>>>>>
>>>>> 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.
>>>>>
>>>>> I get
>>>>> Error: Could not find class aTest for mul-puppet.xxx on node
>>>>> mul-puppet.xxxx
>>>>>
>>>>> Interestingly enough, physically specifiying the long path in the
>>>>> site.pp file seems to work
>>>>>
>>>>> import '/etc/puppet/modules/aTest/manifests/init.pp'
>>>>>
>>>>> root at mul-puppet:/etc/puppet/manifests# cat
>>>>> /etc/puppet/modules/aTest/manifests/init.pp
>>>>> class aTest {}
>>>>>
>>>>> 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?
>>>>>
>>>>> Mike B
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> clue mailing list: clue at cluedenver.org
>>>>> For information, account preferences, or to unsubscribe see:
>>>>> http://cluedenver.org/mailman/listinfo/clue
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> clue mailing list: clue at cluedenver.org
>>>> For information, account preferences, or to unsubscribe see:
>>>> http://cluedenver.org/mailman/listinfo/clue
>>>>
>>>
>>>
>>> _______________________________________________
>>> clue mailing list: clue at cluedenver.org
>>> For information, account preferences, or to unsubscribe see:
>>> http://cluedenver.org/mailman/listinfo/clue
>>>
>>
>>
>> _______________________________________________
>> clue mailing list: clue at cluedenver.org
>> For information, account preferences, or to unsubscribe see:
>> http://cluedenver.org/mailman/listinfo/clue
>>
>
>
> _______________________________________________
> clue mailing list: clue at cluedenver.org
> For information, account preferences, or to unsubscribe see:
> http://cluedenver.org/mailman/listinfo/clue
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://cluedenver.org/pipermail/clue/attachments/20150918/50476074/attachment.html 


More information about the clue mailing list