A list of considerations when buying a new cluster, or adding to an existing cluster. Also applies to other high performance computing (HPC) systems.
General |
Deployed, or simply iIdeas or options which would required further study |
Notes |
Scheraga's Matrix upgrade, 2014 |
---|---|---|---|
Software |
ChemIT: OS, the cluster's software "stack", and core applications. |
See Roles and responsibilities for clusters managed by ChemIT. |
Confirm this is Czerek. |
Backup |
EZ-Backup service |
See Cluster backups and related considerations. |
Get input from Czerek on our current practices, costs, value, as well as other ideas listed. |
Head nodes and compute nodes |
Ensure contemporary head node, taking into account it's age, warranty, and ease of replacement with a compute node (unique attributes, including hard drive bays). |
ChemIT: Will require a new, dedicated head node. |
|
Data storage |
Storage required for headnode and computational use (short term), including job store and user accounts. |
Storing large amounts of data make restores harder, riskier, and more time-consuming. Storing large amounts of data needing backups will cost more than smaller amounts of data. |
Consider the value in separating out longer-term user files from those related to current computational data. |
Networking |
Ensure adequate number of network switches are provisioned. Cabling. Physical arrangement/ proximity. |
|
ChemIT: Will require some more switches and cables. |
Power |
Power strips required (limits!). |
|
Recently purchased UPS can be used for the new head node. Any further protection required to reduce downtime? |
Cornell Active Directory |
When is it a value to research group or ChemIT? |
|
ChemIT not ready to do this at this time. (Revisit if we are ready to offer this when time to deploy.) |
Rack space |
Physical arrangement. Form factors (see nodes, above). |
|
Significant rearrangements may be required in 248 to accommodate a lot of new compute nodes. |
Upgrade process contacts and roles |
Funder(s). Technical lead (in research group). Testers. Users. |
|
|