Purpose:
This document describes the naming convention used by Infrastructure Services for servers. Server names should provide information about the purpose of the server and which environment it belongs to (production or non-production).
Scope:
All servers managed by Infrastructure services should conform to this convention.
Procedure:
General Form:
<service name> - <function > - < environment>
xxxxx-xxx##-xxx
The host name should be ideally be less than 15 characters total (see below).
Service Name – Clear abbreviation of the service or application this server is used for.
-
The service name should be the same for ALL servers within a service/application group. Example: mixing csgold and csgld is not acceptable
-
Up to 5 characters
-
Examples: www, cybr, ebi, rds
Function – 2 to 3 characters with 2-digit sequence number
-
Suggested function names (based on what is currently in use): web, app, db.
-
Other server functions can be added as necessary.
-
Keep functions consistent throughout the service.
-
Use of a two digit number (e.g. 01) for organized sorting.
-
Examples: web01, app01, fwd02, syn03, db01
Environment – Three characters indicating the environment
-
Suggested environments (based on what is currently in use): prd, pre, dev, tst, snd.
-
Keep this consistent - prd not prod. tst not test
Naming - other considerations to keep our server naming in compliance
-
Keep server names all lowercase
-
We’re still limited by NetBIOS on the Windows side, 15 characters max
-
Consistency is the primary focus here. As stated above, keep Service and Function consistent throughout a server group.
Examples
-
Good:
-
adfs-app01-prd
-
splnk-fwd01-prd
-
ems-web01-dev
-
lnl-app02-prd
-
www-web01-prd
-
Not good:
-
buena-vista
-
cdn-prod
-
bantha-serv
-
lic-apppri02-prd
-
cow