The Tufts High Performance Compute (HPC) cluster delivers 35,845,920 cpu hours and 59,427,840 gpu hours of free compute time per year to the user community.

Teraflops: 60+ (60+ trillion floating point operations per second) cpu: 4000 cores gpu: 6784 cores Interconnect: 40GB low latency ethernet

For additional information, please contact Research Technology Services at tts-research@tufts.edu


Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Update Announcement

Attention Cluster users:

This is an update regarding the Tufts Research Cluster expansion project.
  The final phase of the project is now underway.  Three earlier phases
(hardware acquisition, installation and production migration) have been
completed successfully.

We expect the final phase to complete in early September.  Work is
on-going with IBM to finalize network hardware and connectivity for about
30 nodes.  In addition the ATLAS project host, Cobalt, is expected to
re-join the cluster this week.  Once the combined clusters are stable, we
will address software updates and other minor issues that may appear as a
result of this upgrade.

  SSH related login key issues

We are aware that changes to the ssh keys have caused some connectivity
problems with the new cluster head node.  A simple solution is to remove
old cluster keys from your ssh client.  This process depends on how you
connect.   For those that use ssh directly, (Mac OS X or Windows with
CygWin) one may remove/edit out the old key in the following manner:

Launch the terminal application:

Mac OS X launch Terminal.app
Windows with CygWin launch CygWin and then startx

From the shell prompt, run the following command:

rm -f ~/.ssh/known_hosts

If you are using a Windows ssh or sftp client  you may need to use the
embedded key management options/tool.  Unfortunately, there are too many
ssh clients for us to provide exact steps for each.  Your client
documentation is the best source of information for making this change.

Once you have connected to the new head node, you may need to clear old
ssh keys to ensure connectivity with all the new cluster nodes. The
easiest way to do this is to run the following command when you have
connected:

cleanSSH.sh

If you have any concerns, please send them to
cluster-support@tufts.edu<cluster-support@tufts.edu> .

  • No labels