If you only have a couple of servers, it's not a big deal, but when you have hundreds, it's imperative that you make damn sure you name using a method that tells you what each one is for. For example, m-icecast24 would tell me that it's icecast server number 24 in the minneapolis data center. (I don't really have this machine, but this is a similar naming convention we used at a place I used to work). Naming a server something like linux17 is just plain stupid. What the hell does it do? I dunno, better log into it and find out. The only thing I know about it is that it runs linux, and there are probably at least 16 other ones. This naming scheme would suck for me, because I'm a network guy, not a server guy. Since I don't work with this particular machine on a daily basis, I'd probably have to call someone to find out. Unfortunately, I've seen this method used extensively before. -----Original Message----- From: Tony Kelleran [mailto:kiler0n at ags-us.com] Sent: Tuesday, April 22, 2003 8:13 AM To: tclug-list at mn-linux.org Subject: Re: [TCLUG] Server naming conventions As much as I want to name my servers something unique and cool, I tend to stick with what David is saying. Typically, I prefer using the airport code of the city the server is in + function specifier (i.e., A = Application, W = Web, M = Mail, etc) + number. I know, the majority of you are probably cringing with such a "corporate" naming convention. But ultimately, naming conventions should be a documented best practices within your organization. Now naming my personal servers at home is another story. Since I only have a handful, this allows me artistic space to be creative with names. Just my .02 Smith, Craig A (MN14) writes: > At the north end of last Friday's beer meeting, there was a > discussion about server naming conventions. I opined the names of 7 > dwarfs works only until you get an 8th server. > [...] I'm curious as to why you'd need to arbitrarily make up a bunch of server names. I've always named servers after their function. That practice has been used everywhere I've worked. When you have names like www, ns, backup, db, mail, etc., followed by numbers, it is obvious what each box does. It keeps you from saying ``fox is down again'', with people left asking ``is that the mail server or the database server?''. Now, if you're starting a project and need a codename for it, you might pick a short name like ``ant'', and thus name the server that, but that's different than everyday production servers. People would still know what the server was if they knew about the project. -- David Phillips <david at acz.org> http://david.acz.org/ _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list