...

Note: For products that do not require staging, tiers, "test" will match the production configuration and all other requirements for a staging system, and IPS will not requisition a virtualized test environment.

Basic Naming Pattern

Wiki MarkupA hostname is composed of three call signs separated by hyphens. The last call sign is appended with a number to indicate the number of hosts in service for that tier. It ends up taking the form as \ [product\] - \ [tier\] - \ [type\]\[number\], for instance "cms - dev - wcm1" or "map - prod - ws1". Each call sign is 2 to 5 characters. \ *\*

Product and Type Calls Signs

• ist: The IS&T web site
  • sdls: Software Download and Licensing System
• map: MIT Application Platform
  • src: Developer Tools, source browsing and management.
  • build: Developer Tools, build and deploy systems.
  • svn: Developer Tools, Subversion installations.
  • ts: Touchstone, single sign-on (example map-test-ts1)
  • ws: web-services environments (example: map-dev-ws1)
• cms: content-managment system
  • stlr: Stellar course-management system (example cms-test-stlr2)
  • th: Thalia image management (example cms-dev-th1)
• drs: data reporting services. This is not intended to reflect the team name so much as a class of application service.
  • rprt: web-reporting applications

**  The previous convention was to use the department name in this spot, such as ISDA.  However, these change often, but product or project names change less often.  Also note that Athena servers are generally maintained by Server Operations, which has their own naming scheme and set of host organization policies.

...