[chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Introducing the httpd cookbook

[Phil Dibowitz < >]

On 09/07/2014 12:23 AM, Ranjib Dey wrote:
> i dont like the attribute driven lwrps. they couple your code with 
> attribute.
> historically the customization via chef's attribute system has painful. They
> are extremely powerful to create flatter hierarchies, but recipes, wrapper
> recipes etc is a pain. This is partially due to chef's elaborate attribute
> precedence level, and also having a single attribute system to represent
> ohai's related data.
> note. attributes are public read only data. that means any attribute you
> define is available for reads to the entire fleet.

That's not true at all. If I have fb_cron that defines some skeleton
attributes and then fb_httpd that adds some cronjobs, only the things running
fb_httpd see those attributes... which makes sense, since they need those 
crons.

> This also means you are
> storing more data in chef server. 

If you chose to run it that way. You can choose what attributes get sent back
to the Chef server - in Chef 11 via the client.rb, or in Chef 10 via
whitelist_node_attrs. For Facebook, that's no attributes, but for most people,
you could just namespace all this data such that it doesn't get sent back to
the Chef server.

-- 
Phil Dibowitz                             

 
Open Source software and tech docs        Insanity Palace of Metallica
http://www.phildev.net/                   http://www.ipom.com/

"Be who you are and say what you feel, because those who mind don't matter
 and those who matter don't mind."
 - Dr. Seuss

Attachment: signature.asc
Description: OpenPGP digital signature