Server/System naming conventions between environments
Posted on 1998-02-21
After 11 years of AT&T/Lucent networks where we names systems by buildings or apps... and that is amazingly easier done than it sounds. I am in a quandry for the current desire to re-name networked systems to reflect environments within the systems name (we may alias also to start...).
We have 5 major "environments" to consider:
o disaster recovery (DR)
prior to my involvement system names were assigned
in groups & project association, this no longer can hold
with multiply use/projects all running on the same set of boxes.
We have planets, spices, dogs, cars, Scwartzenager movies,
Batman villians, dead presidents (including Reagan)
Tech Support (our internal) wants to an a leter- combination to the names... which would present problems
As the lead administrator I'm looking for something much more elligant(sp) without naming systems like "prod001",
"dev000", or "test019". We want to avoid this approach at all costs.
What are other people with distinct environments doing?