This site requires JavaScript to be enabled
Welcome Guest|
Recent searches
IE BUMPER
KB0017403

MSS Hostname Convention

Number of views : 2
Article Number : KB0017403
Published on : 2020-04-30
Last modified : 2020-04-30 11:13:07
Knowledge Base : ESM External

Standard Host Name Convention

 

Host names must be no more than 15 characters prior to the DNS zone (i.e. austin.utexas.edu or its.utexas.edu). The 15 character limit is due to Active Directory and should be related to the service and function of the host. The goal is to identify by looking at host name, what/who it is for, role (prod/test/dev), and if there are more than one performing that role, a number designate.

  • DNS names for LOMs can exceed 15 characters because they are not joined to Active Directory.

Key and Examples

Standard Convention

  • <prefix>-<role>-<p/b/q/d/t/s>##-<suffix>

 

<prefix>

  • If the service is an enterprise wide service owned by ITS such as TED, Wikis, or Jira, the prefix should reflect the service
    • Ex. wikis-, ted-, jira-, blogs-, svcnw-
  • If the service is departmentally owned, then add a prefix for four letter department code which can be looked up in the Alphabetical Department Listing

 

<role>
  • The role the server plays in the service.
    • Ex. svcnw-mid-, into-fmpro-, zenoss-hub-
 

p

production

 

b

beta

 

q

qual

 

d

development

 

r

disaster recovery

 

s

standby

 

t test   

x

sandbox

 

z

prototype

 

##

number designate

 

<suffix>
  • If the hostname is for a specific purpose such as a lom for out-of-band management, add a suffix appropriate to the purpose.
    • Ex. -filer, -lom -private
 
Examples
  • zenoss-col-p01, a Zenoss collector host, in Production role. Subsequent Zenoss collectors would be zenoss-col-p02, zenoss-col-p03, etc.
  • utps-web-p01, a Web server for UT Press.
  • vprd-sas-p01-lom, a lom for an Office of development production SAS server
 

Standard Environment Name Convention

Hierarchical naming of customer-facing environments, depending on number available.

 
No. Environments Naming Heirarchy
2 QUAL > PROD
3 DEV > QUAL > PROD
4 DEV > TEST > QUAL > PROD

If there is a provider-only environment, typically that will be a Sandbox environment. For example, if you have three customer environments and one provider environment, use the 3 Environments Naming Hierarchy for your customers, and Sandbox for providers:

 
Provider Customer
SANDBOX DEV > QUAL > PROD

 

 

 

Permalink: utss/KAhome.do?number=KB0017403

Thank You! Your feedback has been submitted.

Feedback