Production Servers

• Naming Convention: \[product\]-prod-\[service\].mit.edu. Example: map-prod-ws1.mit.edu

• Server Ops maintained physical hardware. No virtualization.
• Assume that each service requires at least two load-balanced servers.

Staging Servers

• Naming Convention: \[product\]-stage-\[service\].mit.edu. Example: map-stage-ws1.mit.edu

• Server Ops maintained physical hardware. No virtualization.
• Assume that each service requires at least two load-balanced servers.

Test Servers

• Naming Convention: \[product\]-test-\[service\].mit.edu. Example: map-test-ws1.mit.edu

• Server Ops virtualized server.
• These are testing for developers, not operations. Assume only one server instance per service required.

Development Servers

• Naming Convention: \[product\]-dev-\[service\].mit.edu. Example: map-dev-ws1.mit.edu

• Server Ops virtualized server.
• These are for software development, not operations or infrastructure prototyping. Assume only one server instance per service required.

Prototype Servers

• Naming Convention: \[product\]-proto-\[service\].mit.edu. Example: map-proto-ws1.mit.edu

• ISDA maintained virtualized server co-located with server operations.
• These servers are for our internal use, for any system that needs quick turn around, will be in use for brief periods of time, or other well defined, low usage functions by a small number of people.

Naming Convention Notes for Hostnames

numbers: Numbers describe the number of servers for that service for that tier. map-dev-ws1 and map-test-ws1 are both legal, because both are the 1st server rolled out for the service for that tier. 

product: A 2 to 5 letter call sign for either a product group (such as map for MIT Application Platform) or a Meta-Project that has other Projects as its components (Project Athena, Project Minerva). ** 

map: MIT Application Platform (map-test-ws1)

ws: Web Services (map-prod-ws2)

ts: Touchstone (map-dev-ts1)

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