Server Types

We define five tiers of servers. No product requires all five. Five are the maximum. A product will likely have several servers for different purposes in each tier.

  • Prototype (proto): In ISDA's colocation rack. Defined as temporary, try-out, crash-and-burn systems.
  • Development (dev): Virtualized via Server Operations' virtualization service. The environment for developers to perform their project work.
  • Test (test): Virtualized via Server Operaions virtualization service. The environment for internal ISDA testing.
  • Staging (stage): Real production hardware via Server Operations standard offerings. For products that require it, this is for external developers or other end-users to test their integration. ISDA treats these as production. The configuration of this system is always identical to production.
  • Production (prod): Real production hardware via Server Operatons standard offerings. This is the live system.

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

A 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.

Naming Pattern for Prototype Server

Prototype servers are on ISDA's colocation rack. Prototypes are designed to crash and burn so IPS selected a very generic namespace to avoid the overhead of requesting new names from server operations on a regular basis.

First Call Sign

Second Call Sign

Third Call Sign

real: for hostnames of actual server hardware

proto: this is always the second part of the name

alpha, beta, etc: greek alphabet in order real machine is added to farm or VM is created.

 virt: for hostnames of virtual operating systems

 

 

 The Result: Names in the form "real - proto - alpha" or "virt - proto - omega."

  • No labels