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