System Naming Schema

[seth vidal]

On Thu, 2011-04-28 at 15:25 -0600, Kevin Fenzi wrote:
> Well, here's the simple way I imagine: 
> 
> - new machines increment number. 
> - we setup CNAME aliases. 
> - CNAMEs change when new machine is placed in service. 
> 
> For example: 
> 
> We have a log01. We make a new log02, get it all setup, working, etc. 
> We have a 'collectd-server' cname that points to log01
> We have a 'syslog-server' cname that points to log01
> We have (optionally) a 'log-server' cname that points to log01.
> 
> When changing things, we just change the cnames. Admins learn to login
> to the cname and it always goes to the live one. Although that doesn't
> help for puppet. 
> 


I am in favor of the above wholeheartedly - it is, implicitly, what I've
been doing with the single-server instances - like people.

we have people01 - which is accessed by people.fp.o or fedorapeople.org

when people02 is happy it will be where people.fp.o points to.

now - what about for services which have more than one machine
backending them.

if we have, for example, x86-01 -> x86-19 - which are builders - should
we go to 20-25 and remove 01-06? or should we just replace and keep the
same range.

I don't mind either, I just want a decision on those.

-sv