- From: "
" <
>
- To:
- Subject: [chef] Re: Hostname Naming Strategies
- Date: Thu, 5 Aug 2010 13:03:02 -0700
- 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=iz/K9wZly+a3tmwzQrSXWsTioW1NMNtD6EW4uyeDtzWZc+Ge2R3G/qsOmt06Gbgmhw hzOJ/BkHXO+xZS8d2cbh0ahdZmCl9IOrzWizLLN4fCwxOsN28xi+PitQfLEYPO6togCS 7Clgt8wpUr6VL0ePBubtJehPzDeqBNDBUrKX4=
This tends to follow the standards I'm used to pretty well this is worth a read ...
http://labmice.techtarget.com/articles/computernaming.htm
--sahil
On Thu, Aug 5, 2010 at 1:01 PM, Ryan Chavez
<
">
> wrote:
Hi All,
We're starting to think through more of our infrastructure work, and I'm curious how you all approach naming your boxes. We were thinking a simple prefix followed by an index that increments with each new box that starts up. But we're wondering what the best way is to manage that counter. Is that something you all delegate to the opscode server?
And how do you deal with host names when you scale up/down capacity?
We're trying to figure this stuff out on our own, so looking to learn from those who have been down this road already.
Thanks!
Ryan Chavez
Archive powered by MHonArc 2.6.16.