you may want to think about using a naming scheme that incorporates location as well. We have around 400 servrs now, and 33 racks of equipment. We use the following name scheme:
xxxRnnnSmm
where xxx is a designation for the datacenter. (we have 2 today. eg: va1, sf2, ny1. These just let us know what facility)
Rnnn is for the rack in which the server is located. we number all racks, so R230 or R193, etc.
Smm is for the server number. we count servers from the bottom and then name them accordingly. typically we have between 10-30 servers in a rack.
so a final server name might be: ny1R130S27 - so that would signify our first NYC datacenter facility, Rack #130, 27th server from the bottom.
Additionally we numer all servers on a private network and NAT out from there. The server name is reflective of the IP as well. so we choose an arbitrary IP subnet of 10.22.128.0/17 and number from there. Assuming we number racks 128, 129, 130, 131, etc. we can reconstruct the IP from the server name, and the server name from the IP.
so ny1R130S27 would have IP 10.22.130.27 ny1R141S13 would have IP 10.22.141.13 IP 10.22.235.34 would be server name ny1R235S34 IP 10.22.207.11 would be server name ny1R207S11
Then we have a seperate database that links this server name with an account name/service name. Very handy for operations staff. and there is no possiblity of having the same name, or IP.
These little devices are liked to your email so you receive messages as they are sent on your hip. a cool gadget, but this is the one thing that will really make you keep on top of your messages or drive you crazy.
I have one and it's useful in that I can keep on top of messages as they arrive when I'm away from my desk so that I don't have to sift through hundreds of messages every morning. but at times it drives me crazy as the pager buzzes with every message.
Slashdot Mirror
I'll stick to Reverse Osmosis for my filtering needs.
actually making a software product that functions, even when stressed? now that's just crazy talk.
but in reality this is somethign that every product (hardware or software) should go through. It'll just make a better product.
you may want to think about using a naming scheme that incorporates location as well. We have around 400 servrs now, and 33 racks of equipment. We use the following name scheme:
xxxRnnnSmm
where xxx is a designation for the datacenter. (we have 2 today. eg: va1, sf2, ny1. These just let us know what facility)
Rnnn is for the rack in which the server is located. we number all racks, so R230 or R193, etc.
Smm is for the server number. we count servers from the bottom and then name them accordingly. typically we have between 10-30 servers in a rack.
so a final server name might be:
ny1R130S27 - so that would signify our first NYC datacenter facility, Rack #130, 27th server from the bottom.
Additionally we numer all servers on a private network and NAT out from there. The server name is reflective of the IP as well. so we choose an arbitrary IP subnet of 10.22.128.0/17 and number from there. Assuming we number racks 128, 129, 130, 131, etc. we can reconstruct the IP from the server name, and the server name from the IP.
so ny1R130S27 would have IP 10.22.130.27
ny1R141S13 would have IP 10.22.141.13
IP 10.22.235.34 would be server name ny1R235S34
IP 10.22.207.11 would be server name ny1R207S11
Then we have a seperate database that links this server name with an account name/service name. Very handy for operations staff. and there is no possiblity of having the same name, or IP.
These little devices are liked to your email so you receive messages as they are sent on your hip. a cool gadget, but this is the one thing that will really make you keep on top of your messages or drive you crazy.
I have one and it's useful in that I can keep on top of messages as they arrive when I'm away from my desk so that I don't have to sift through hundreds of messages every morning. but at times it drives me crazy as the pager buzzes with every message.