[chef] Re: Re: Re: Re: Re: Re: Setting Hostname on EC2 Instance Spinup

[Sean OMeara < >]

Here's an example of a bootstrap template that sets the hostname from -N on 
RHEL

https://github.com/someara/affs-chef/blob/master/.chef/bootstrap/affs-fc13.erb

-s

On Tue, Apr 5, 2011 at 8:41 AM, Thom May 
<
 >
 wrote:
> There's an example of it in the dynect cookbook -
> https://github.com/opscode/cookbooks/blob/master/dynect/recipes/ec2.rb
>
> On Tue, Apr 5, 2011 at 13:04, Rob Guttman 
> <
 >
>  wrote:
>>>
>> This is what we do for our EC2 nodes, except we use the instance ID for the
>> node name and generate the hostnames from the roles.
>>
>> Dan, where can I find how to do something like this for ec2 nodes?  Is the
>> recipe available somewhere?
>>
>> Thanks.
>> - Rob
>>
>>
>> On Tue, Apr 5, 2011 at 12:58 AM, Daniel DeLeo 
>> <
 >
>>  wrote:
>>>
>>> On Monday, April 4, 2011 at 9:53 PM, Chris Streeter wrote:
>>>
>>> I ran knife with the -N option with the parameter set to 'www'. However,
>>> the
>>> hostname of the box (set on the box and in the opscode console) is set to
>>> an
>>> AWS internal IP (ip-10-XXX-XX-XX) while the nodename is set to www. So
>>> this
>>> doesn't quite do what I want it to do. I want the actual hostname of the
>>> box to
>>> be www.
>>>
>>> Otherwise, in a template, how do I get the node's name (for populating
>>> /etc/hosts on all machines)?
>>>
>>> By setting the node name via -N, you should create the node and it's
>>> client with the given id, and configure it to use those values instead of
>>> the hostname. Then you're free to change the hostname without changing the
>>> ID the node uses to identify itself with the server. So you could create a
>>> cookbook to configure the hostname according to the node name. This is 
>>> what
>>> we do for our EC2 nodes, except we use the instance ID for the node name 
>>> and
>>> generate the hostnames from the roles. But the basic idea is the same.
>>>
>>> --
>>> Dan DeLeo
>>>
>>
>>
>