- From: Tim Uckun <
>
- To:
- Subject: [chef] Re: Re: Starting out with the opscode platform.
- Date: Mon, 30 May 2011 14:30:21 +1200
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=MfLeWVGwwYbwaK2/DZgwJ5hFpkkZyNmyFf1cNJzql8buW7IRb2h52apoaqQ2Vtu5p7 YdeT/HOMeXUB7EqVjmqloKr6UTIDatQZBgEFukzdjO72gbGCgyAvyxJZQMrWAXyOm3Y0 0tFUdvDeU5FcaF2uUpuIoMjnV2Buw4ff41vmo=
>
>
If you have some custom setup (most people do) then you would create a
>
new recipe to do that and include it in the relevant role.
>
How about highly specific parameters like IP address etc.
I am sorry if this is a dumb question but I am coming from puppet and
I guess I still have that the puppet way of doing things in my head.
Normally I set up my node and set some variables like
$ip_address = 'blah'
$host_name = 'blah'
Then I might have individual resources for this node alone like
file :some_file { ...}
This along with the inheritance of other common roles defines the
state of the node.
I am wondering where that configuration takes place in the chef node.
From what you guys are saying it sounds like I need to create a role
for the server right?
Archive powered by MHonArc 2.6.16.