[chef] Re: Re: Managing Node Info

[jorge espada < >]

Thanks Adam for answer, yes they are truly per-node, for instance we have:

4 servers(nodes) called app[1-4] all of them are running  tomcat and tomcat is configured to talk to an ejabberd cluster,  but each of them are connected to a different server in that ejabberd cluster.. hence each node (app1 , app2...) has a different config for tomcat, despite they belong to the same services, let say app-services.. so what do you suggest one role per instance of the same service ?

Thanks 

Jorge E. Espada

Phone: +54 9 341 5692435

On Tue, Oct 4, 2011 at 4:29 PM, Adam Jacob < " target="_blank"> > wrote:

Are they truly per-node, or are they four different roles?

Ideally, you would abstract the differences, and then just apply the
attributes to each node through a role (or on the node itself, if it's
truly one-off)

Best,
Adam

On Tue, Oct 4, 2011 at 12:22 PM, jorge espada < " target="_blank"> > wrote:
> Hi, what will be the right or better approach to store custom (non default)
> config attributes  per node ?
> For instance, lets say that I have the tomcat or apache cookbook applied to
> 4 nodes, and all of them have different config files, should I write 4
> different attributes files for that cookbook , also for each same cookbook
> applied to those nodes with different configs? Or is better to use data bags
> for custom configs on each nodes?
> I know that   attribute is a per-node thing. and data bag is across nodes.
> but I'm not sure how to sort this situation.. or there is another thing that
> i'm missing
> Thanks
> Jorge E. Espada
> Phone: +54 9 341 5692435
>

--
Opscode, Inc.
Adam Jacob, Chief Product Officer
T: (206) 619-7151 E: " target="_blank">