[Info-vax] Cluster Nomenclature

[Main, Kerry]

> -----Original Message-----
> From: info-vax-bounces at rbnsn.com [mailto:info-vax-bounces at rbnsn.com] On
> Behalf Of Rich Jordan
> Sent: March 5, 2009 1:24 PM
> To: info-vax at rbnsn.com
> Subject: Re: [Info-vax] Cluster Nomenclature
> 
> On Mar 5, 11:00 am, sapienzaf <sapie... at noesys.com> wrote:
> > On Mar 5, 10:07 am, Rich Jordan <jor... at ccs4vms.com> wrote:
> >
> > > At home I used music and literature for a while (Fugue and Fury,
> > > Sonnet, Tempo) till I got an alpha running NT and didn't want to
> waste
> > > a good name on it (it became 'wastedalpha' but I almost named it
> > > 'rap'), then switched to cars (Fury, heh!, Monaco, Polara, Dart,
> > > Demon, Duster, Cuda, hemi).
> >
> > Sorry to spoil your naming convention, but Hemi is an engine, not a
> > car.
> >
> > :-)
> 
> True.  Hemi is a way of life ;)  Related enough since it was the most
> powerful node in the cluster at the time.  My cluster had a Hemi in
> it.  Besides the motoring illiterati would look at a Roadrunner or
> GTX, see the Hemi badging, and just call it a Hemi so its not entirely
> inconsistent.
> 
> "Wastedalpha" was also node "Rising" when running a real OS.  From
> "Wasted Alpha" to "Alpha Rising" just by rebooting.  Its name also
> didn't fit the convention, but then who really cares, it was (and is)
> a good name and it fit in the 6 character limit.
> 
> I personally like the Deathrow naming convention but not for my own
> use.
> _______________________________________________


Might be boring, but given the reality of system upgrades, servers moving
from one facility or one dept to another, architecture chgs etc, I prefer 
to use a more functional approach which also makes it easier to add-on 
additional systems:

SYS001
SYS002
SYS00x


Regards

Kerry Main
Senior Consultant
HP Services Canada
Voice: 613-254-8911
Fax: 613-591-4477
kerryDOTmainAThpDOTcom
(remove the DOT's and AT)

OpenVMS - the secure, multi-site OS that just works.