Hostnames
61–70 of 187 posts
Re: Hostnames
#62There's an RFC on that, too. "Choosing a name for your computer" http://tools.ietf.org/html/rfc1178 Shades of colours, for example https://en.wikipedia.org/wiki/Category:Shades_of_blue , are a good, safe source of names.
https://en.wikipedia.org/wiki/Category:Shades_of_gray
For a network of 50 computers :)
Re: Hostnames
#63Cute server naming schemes are one of my pet peeves. In my experience the only two logical choices are: sequential numbers (e.g. foo1, ..., foo100, ... if your company name is Foo Corp.), or hashes / uuids (like amazon instance IDs, e.g. i-977a24e3). If you want to give a server a memorable or cute name, use DNS or some kind of alias.
Read the aforementioned RFC - with sequential numbers you are not naming them. I can imagine how thrilled your colleagues are if they have to ssh into i-977 what was the rest of it?
You might as well just call them "1", "2", and "3". The only time this kind of
naming scheme is appropriate is when you have a lot of machines and there are
no reasons for any human to distinguish between them. For example, a master
computer might be controlling an array of one hundred computers. In this case,
it makes sense to refer to them with the array indices.
When you're starting off with your cute naming scheme, how do you know how many machines you'll manage in the end? Most places I've worked at have hundreds of servers. Using a simple, easy to follow, don't-make-me-think standard from the beginning is the only thing that makes sense IMO.To give a server a meaningful name, use DNS.
edit: Also, to take your complaint about "i-977.. what was the rest of it?" and turn it around - imagine this scenario: provision 20 new app servers named foo40..foo59 OR provision 20 new app servers and think of 20 cool names to match our existing cool naming scheme of leonardo donatello michaelangelo raphael master-splinter shredder blah blah blah :)
Re: Hostnames
#64AlphaTrion is the PDC, A-3 is the BDC/SDC. Iacon is the SQL machine (VectorSigma is the name of the LVM pool). OmegaSupreme/Metroplex/FortressMaxiums are the gateways. Gestalts (Defensor, Computron, Superion) are used for the SANs and any other clusters.
Considering we try to be good guys, we only allow Autobot names for workstations. Starfire, Starscream, Punch-Counterpunch, and other fence sitters are not allowed. I lobbied for Wheelie to be included in that list, but was overruled by others.
[EDIT] I could see how this might have limitations on scale, but we haven't hit those limits internally, so it doesn't affect me yet. :)
Re: Hostnames
#65Sweet list. Phonetic Alphabet is a good one - it has the typing superpower of striking first letter then for instant autocomplete.
Re: Hostnames
#66There's an RFC on that, too. "Choosing a name for your computer" http://tools.ietf.org/html/rfc1178 Shades of colours, for example https://en.wikipedia.org/wiki/Category:Shades_of_blue , are a good, safe source of names.
Re: Hostnames
#67We had a 'bad idea' theme once which included:-
port23
dotat
But my favourite for one of our build machines and appeared in -version output of our product was sigsegv.I've settled on the elements with atomic number as last octet and the handy shorthands, but that's for home dev network.
For company stuff they get named by function/env/counter.
Re: Hostnames
#68Re: Hostnames
#69We used to use Marvel characters until our setup got too big. Now it's (datacenter)-(type (web, proxy, db, etc))(number). So, sfo-proxy1, for example.
Re: Hostnames
#70Shortly after setting it up, I pinged it from a Solaris box. The response was 'passion is alive'.
I tell this story every time there is a 'what do you call your hosts?' discussion!