mapws.mit.edu: F5-virtualized hostname for production servers.
These are comprised of two \[TBD\]two HP G4 DL380s with 4 Intel Xeon CPU Cores at 3.20GHz each.Wiki Markup - They have 4G RAM/8G swap. Memory upgrades on order.
- 120G storage capacity.
- Red Hat Enterprise Linux 4
- Load balancing is basic round-robin through the shared F5 provided as a service by IS&T. Sticky sessions are not used because all the services are currently stateless.
- We can change the F5 when more complex configurations become necessary.
...
- "Stage" implies an environment just as reliable as production for outside developers to test their integration with the services.
- Staging will always match the hardware configuration listed for production.
Support Notes
- IPS actively monitors the SOA environment and we keep the system in a state of continuous improvement.
- Improvements are planned by IPS in conjunction with the MAP Working Group. IPS will not alter systems without the Working Group's knowledge and approval.
- ISDA management is committed to improving the SOA offering to MIT and we will not enter into a support-only mode for the foreseeable future.
- Based on the performance of new services that are introduced to the system, we can add additional servers into the topology. Staging will always match production in its configuration.
- Staging environments are in the same place as production and behind the same F5 so that, should one machine experience a critical failure, staging environments can be promoted forward to handle the load.
- Test environments are in a different data center. In the result of a catastrophic failure in the production data center, IPS will convert test machines into production. These will not provide the same level of performance.