[chef] Re: RE: Re: multiple clusters and attributes

[KC Braunschweig < >]

A cluster sounds like it could be a chef environment. could you just have a recipe in which each node uses the search API to find all nodes in the environment?

KC

On Apr 6, 2012 8:28 AM, "Van Fossan,Randy" < "> > wrote:

Thanks Brad,

There are some nice things in that cookbook that I may rethink in my hosts cookbook.

However, the issue for specifying all the nodes in a cluster when running the bootstrap on a particular node remains.

The only solution I have come up with is to use a databag that describes each cluster and it's nodes or to create a custom role for each cluster..

Randy

-----Original Message-----
From: "> [mailto: "> ] On Behalf Of Brad Montgomery
Sent: Friday, April 06, 2012 11:09 AM
To: ">
Subject: [chef] Re: multiple clusters and attributes

We've got a recipe to do this... you create a role, and then an attribute that just lists all the hostnames. The recipe then looks up their ip addresses and writes the /etc/hosts file.

There's probably a better way to do this, but this works for us.

You can see our recipe, here:
https://github.com/coroutine/chef-hosts

On Fri, Apr 6, 2012 at 9:05 AM, Van Fossan,Randy < "> > wrote:
> How are you guys handling attributes for multiple systems (like clusters)??
>
>
>
> For example, in cluster, I need to be able to add all nodes in the
> cluster to the /etc/hosts file on each cluster node.   I am not sure
> of the best method for setting / adding attributes for these entries
> without creating something like a separate role for each cluster.
>
>
>
> I already have a hosts cookbook to add additional entries if the
> attribute has data.   I just do not know how to populate that array
> differently for different clusters.
>
>
>
> Anyone have any suggestions or ideas?
>
>
>
> Thanks
>   Randy