[chef] Re: Re: Re: managing system files with Chef

[Jeffrey Hulten < >]

Now if only there was an /etc/hosts.d

On Thu, May 5, 2011 at 12:54 PM, Rob Guttman 
<
 >
 wrote:
>> The ideal situation is that your applications support config.d/
>> directories ..
>
> Bingo.  Nagios uses such directories aplenty - they work very well for us.
>
> - Rob
>
>
> On Thu, May 5, 2011 at 1:34 PM, Jason J. W. Williams
> <
 >
>  wrote:
>>
>> Hi Sasha
>>
>> > The first has pitfalls.  We shouldn't be managing system files at that
>> > level.  Patching should be an automated process, and trying to keep an
>> > eye
>> > on system files during the patch process is not something I'm interested
>> > in.
>> >   Also it means that only one recipe can ever manage that file.  In most
>> > cases that's fine, but in others, it won't work.  Example: I have two
>> > different cookbooks that add keys to the root authorized_keys file in
>> > some
>> > cases.  Or what if two different things want to insert things in the
>> > modprobe.conf?  I have a system config recipe that inserts lines into
>> > the
>> > modprobe.conf to disable IPv6 and a KVM recipe that inserts the kvm
>> > module
>> > lines.
>>
>> We're in the same boat on things like Nagios NRPE configs where
>> depending on the role of the server different checks need to be
>> present or not. We're planning to handle it with templates and
>> conditional Ruby blocks. Our plan is to use the roles the server
>> belongs to activate particular blocks for checks specific to those
>> roles. I would imagine a similar solution might work in your scenario.
>> That would be much cleaner than patching I would imagine.
>>
>> -J
>
>



-- 
Jeffrey Hulten
Principal Consultant at Automated Labs, LLC

 
 206-853-5216