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

[Seth Chisamore < >]

I'm with Brian on this....clever naming conventions were much more important in the 'old' way of doing things .  In the Chef world a node's role (and environment) is a much more important indicator of 'real' function...and feeds directly into Chef's data-driven goodness.  The sooner you can let go of these naming conventions the sooner you can embrace an ephemeral world where nodes can be killed and rebuilt on demand. You worry less about the individual nodes and more about the infrastructure as a whole...ie your application is just an appliance.

Seth

--
Opscode, Inc.
Seth Chisamore, Technical Evangelist
IRC, Skype, Twitter, Github: schisamo

On Tue, Apr 5, 2011 at 1:26 PM, Brian Akins < "> > wrote:

On Apr 5, 2011, at 10:22 AM, Rob Guttman wrote:

> Thanks for all of the examples so far, everyone.  They answer half of my question which is how best to set/change the hostname of an ec2 instance.  The other half is how best to set the hostname based on the node's roles.  I would like to use a host naming pattern something like this:
>
>   <primary_role>NN-<environment>-<availability-zone>
>
> So something like:
>
>   web04-production-useast1a
>

Not to start a naming convention war, but we used to use a scheme like that.  Many hours were wasted arguing.  Now*, we just name them simple things (like, host1, host48, web1, db8).  Since most of our configs are built using databags and searches and our "doit" scripts use knife, having "meaningful" hostnames is not terribly useful as noone every uses them directly much.

*Note: "Now" meaning we do it some now and are moving towards it.