[chef] Re: Re: Re: Re: Re: Re: Re: Re: Where to keep your <node>.json files?

[Torben Knerr < >]

Peter, AJ,

thanks for sharing your thoughts and the pointer to the bag_config cookbook, I will have a look at it!

Torben

On Tue, Apr 24, 2012 at 10:27 AM, AJ Christensen < " target="_blank"> > wrote:

That cookbook is built by Heavy Water -- I guess it largely reflects
my views on transitive node data.

--AJ

On 24 April 2012 20:13, Peter Donald < "> > wrote:
> Hi,
>
> And someone just pointed out to me a cookbook that may help you ...
> though I have yet to try it.
>
> http://community.opscode.com/cookbooks/bag_config
>
> On Tue, Apr 24, 2012 at 3:49 PM, Peter Donald < "> > wrote:
>> On Tue, Apr 24, 2012 at 3:41 PM, Torben Knerr < "> > wrote:
>>> But what about attribute overrides on node level? Is that something that we
>>> should rather avoid and better do any cookbook configuration on a role level
>>> instead?
>>
>> We have been able to avoid node specific attributes in our
>> infrastructure. Attributes are all in roles or environments. Sometimes
>> we store the configuration for a particular application in a databag.
>> Then our recipes may read the databag (often based on the current
>> environment) and publish relevant attributes from the databag into the
>> node - but usually we only do this when we need to use these
>> attributes in searches from other nodes. So far ... this approach
>> seems to be working ok.
>>
>> --
>> Cheers,
>>
>> Peter Donald
>
>
>
> --
> Cheers,
>
> Peter Donald