[chef] Re: Re: Re: How do you set node-level attributes?

[Jacobo García < >]

I don't think there's a best practice at all in setting values, what
I'd do in your case is setting these values as default, then changing
then in the UI per machine basis.

Other option is setting them based on fqdn on atributtes defined.
Something like this:

case fqdn
when "host1.foo.com"
default[:mongodb][attr1]="foo"
when "host2.foo.com"
default[:mongodb][attr1]="bar"
end

Hope this helps.

Jacobo García López de Araujo
blog: http://robotplaysguitar.com
http://workingwithrails.com/person/13395-jacobo-garc-a




On Wed, Feb 10, 2010 at 4:54 PM, Ruby Newbie 
<
 >
 wrote:
> Hey, Jacobo.
>
> On Feb 10, 2010, at 5:43 AM, Jacobo García wrote:
>> What are you using to set the value (set or default) in the attributes
>> file? I guess that you are using set
>
> All attributes are set with 'default', like so...
>  default[:mongodb][:platform] = 'linux'
>  default[:mongodb][:arch] = 'x86_64'
>  default[:mongodb][:version] = '1.2.2'
>
> Do you know of any way *besides* the web GUI to set node-level attributes? 
> The fact that I am not managing to set them from the web interface is not 
> as concerning as the fact that there seems to be no "best practice" for 
> defining a node -- that is, defining both its role(s), and the particular 
> attribute values it *doesn't* share with other nodes that play the same 
> role.
>
> Thanks for responding,
> Ruby newbie.
>
>
>