Re: [SAGE] Naming conventions for servers, network gear, etc.

["Rodrick Brown" <rodrick.brown@gmail.com>]

On 1/7/07, Brad Knowles <brad@shub-internet.org> wrote:
> At 4:28 PM -0500 1/6/07, Rodrick Brown wrote:
>
> >  scsinfpladm01
> >  (scs) == Location "Secacus"
> >  (inf) == Business Owner in this case "Infrastructure"
> >  (p) == Server environment "production"
> >  (l) == OS type "linux"
> >  (adm) == server function "administrative"
> >  (01) == instance number.
>
> I really, really, really hate long hostnames.  Use subdomains if you
> need to, but don't try to have a flat namespace across the entire
> company or the entire world.
>
It really depends on your definition of a long hostname? I find
subdomains to be really annoying in a practical sense especially in
environments where you can easily run into issues where you have
duplicate hostnames depending on your search path it can get really
confusing, this is very likely in larger environments. ie.
servera.foo1.domain.com servera.foo2.domain.com.
> And I wouldn't encode the OS into the hostname, either.  See RFC 1178
> (e.g., <http://www.faqs.org/rfcs/rfc1178.html>) for reasons why.
>
The OS type indication in a hostname makes automation/scripting very
simple across the board. I have not found a single issue with this
scheme over the years please enlightenment on where exactly this can
be problematic so far you've stated nothing but religious reasons.
Brad I really value your input so please don't take this response as
an attack in anyway I just want to see where exactly you feel this can
be an issue.

> --
> Brad Knowles, <brad@shub-internet.org>
>
> Trend Micro has announced that they will cancel the stop.mail-abuse.org
> mail forwarding service as of 15 November 2006.  If you have an old
> e-mail account for me at this domain, please make sure you correct that
> with the current address.
>

-- 
Rodrick R. Brown