[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



On 1/5/07, Mark R. Lindsey <lindsey@acm.org> wrote:
> Have there been any papers done on naming conventions for servers,
> network gear, etc?
>
> E.g., when is it better to call it "core-router-bwg" versus
> "juniperm10i" versus "router1"?
>
> Or "server1" versus "dns1" versus "franko"?
>
> There are a few obvious up-sides and down-sides of different schemes.
> But has anybody really dug in and written them down?
>
> If not, I'd be interested in writing a paper on this with somebody
> for USENIX or SAGE. If you're interested in working with me on it,
> let me know.
>
>
>
>
>
> Mark R. Lindsey  | ECG |  +1-229-316-0013  |  lindsey@e-c-group.com
>
>
>

Most companies I've worked for we've used a variation of the following
but this approach works very well especially for large multi-region
environments.

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.

If the machine is a blade server we use something like 01xx 01 would
be the blade itself followed by xx that would be the actually location
of that specific blade on the chassis ie. scsinfplpadm0114

Looking at a generic hostname such as "chicsidsdb01" we know off bat
its located in Chicago running a Solaris database in dev and the
business owner is cash securities.

-- 
Rodrick R. Brown