Both sides previous revision
Previous revision
|
Next revision
Both sides next revision
|
cluster:126 [2020/01/30 08:06] hmeij07 [Other Stuff] |
cluster:126 [2020/02/27 09:26] hmeij07 |
The High Performance Compute Cluster (HPCC) is comprised of several login nodes (all are on our domain //wesleyan.edu// behind VPN for off campus access) | The High Performance Compute Cluster (HPCC) is comprised of several login nodes (all are on our domain //wesleyan.edu// behind VPN for off campus access) |
| |
* primary login node ''cottontail'' (Supermicro 4U), Openlava scheduler and snapshot engine | * primary login node ''cottontail'' (Supermicro 4U), Openlava scheduler and snapshot engine for /home |
* secondary login node ''cottontail2'' (HP Proliant G380 2U), backup scheduler, standby for /sanscratch | * secondary login node ''cottontail2'' (HP Proliant G380 2U), backup scheduler |
* secondary login node ''swallowtail'' (Dell PowerEdge 2950 2U), backup scheduler, databases | * secondary login node ''swallowtail'' (Dell PowerEdge 2950 2U), backup scheduler, databases |
* (old login node) ''petaltail'' (Dell PowerEdge 2950 2U), test box (may crash), Warewulf provisioning | * sandbox ''petaltail'' (Dell PowerEdge 2950 2U), test box, Warewulf provisioning CentOS6 |
* (old login node) ''greentail'' (HP Proliant G380 2U), /sanscratch primary NFS server | * NFS server ''greentail52'' (SuperMicro 36+2, 2U), /sanscratch |
* <del>(old node) ''whitetail'' (Angstrom Blade 1U), Hadoop Cloudera test server</del> | * (only log in when moving conternt) file server node ''sharptail'' (Supermicro 4U), /home NFS server |
* (not to be used as) login node ''sharptail'' (Supermicro 4U), /home primary NFS server | * DR node ''sharptail2'' (Supermicro 2U), disaster recovery for /home, off site (active users only) |
* DR node ''sharptail2'' (Supermicro 2U), disaster recovery for /home, off site | * storage servers ''rstore0'' and ''rstore2'' (Supermicro 4U), NFS mounts and Samba shares (2x 120T) |
* Storage servers ''rstore0'' and ''rstore2'' (Supermicro 4U), NFS mounts and Samba shares | * storage servers ''rstore4'' and ''rstore6'' (Supermicro 4U), NFS mounts and Samba shares (2x 220T) |
| * mindstore storage servers ''mstore0/mstore1'' (Supermicro 4U), available on HPC (2x 110T) |
| |
Several types of compute nodes are available via the OpenLava scheduler, http://www.openlava.org: | Several types of compute nodes are available via the OpenLava scheduler, http://www.openlava.org: |
| |
* All are running CentOS6.[4-9], x86_64, Intel Xeon chips (except the Angstrom blades which are AMD Opteron) | * All are running CentOS6.10 or CentOS7.7 |
* All are on private networks (no internet) | * All are x86_64, Intel Xeon chips from 2006 onwards |
* All mount /home (10TB, to be expanded to 25TB fall 2017) and /sanscratch (33TB) | * All are on private networks (192.168.x.x or 10.10.x.x, no internet) |
| * All mount /home (10TB, to be replaced by FreeNAS/ZFS 190T appliance 2020) and /sanscratch (xfs,55TB) |
* All have local disks providing varying amounts of /localscratch (usually Raid0, no backup!) | * All have local disks providing varying amounts of /localscratch (usually Raid0, no backup!) |
* Hyperthreading is on but only on newer hardware are 50% of logical cores allocated. | * Hyperthreading is on but only 50% of logical cores allocated via scheduler |
| |
Compute node categories which usually align with queues: | Compute node categories which usually align with queues: |
* 18 nodes with dual twelve core chips (Xeon E5-2650 v4, 2.2 Ghz) in Supermicro 1U rack servers with a memory footprint of 128 GB each (2,304 GB). This cluster has a compute capacity of 14.3 teraflops (estimated). Known as the Microway "Carlos" CPU cluster, or nodes n60-n77, queue mw128, 648 job slots. | * 18 nodes with dual twelve core chips (Xeon E5-2650 v4, 2.2 Ghz) in Supermicro 1U rack servers with a memory footprint of 128 GB each (2,304 GB). This cluster has a compute capacity of 14.3 teraflops (estimated). Known as the Microway "Carlos" CPU cluster, or nodes n60-n77, queue mw128, 648 job slots. |
| |
* 1 node with dual eight core chips (Xeon E5-2620 v4, 2.10 Ghz) in Supermicro 1U rack server with a memory footprint of 64 GB (128 GB). This node has four GTX1080Ti (44 GB memory footprint) gpus providing 1.42 teraflops. Known as the "donated Amber" node n78, queue amber128, 24 job slots. | * 1 node with dual eight core chips (Xeon E5-2620 v4, 2.10 Ghz) in Supermicro 1U rack server with a memory footprint of 128 GB. This node has four GTX1080i (32 GB memory footprint) gpus. Known as the "amber128" queue, 24 job slots. |
| |
All queues are available for job submissions via all login nodes. All nodes on Infiniband switches for parallel computational jobs (excludes tinymem, mw128 and amber128 queues). Our total job slot count is roughly 1,712 with our physical core count 1,192. Our total teraflops compute capacity is about 38 cpu side, 25 gpu side (double precision floating point). Our total memory footprint is about 144 GB gpu side, 7,408 GB cpu side. | * 12 nodes with dual twelve core chips (Xeon Silver 4214, 2.20 Ghz) in ASUS ESC4000G4 2U rack servers with a memory footprint of 96 GB ( 1,152 GB, about 20 teraflops dpfp). These node each have four RTX1080S (32 GB memory footprint) gpus providing 702 teraflops (mixed mode). Known as the "rtx2080" rack, nodes n79-n90, queue exx96, 432 job slots. |
| |
Home directory file system are provided (via NFS or IPoIB) by the node ''sharptail'' (our file server) from a direct attached disk array. In total, 10 TB of /home disk space is accessible to the users. Node ''greentail'' makes available 33 TB of scratch space at /sanscratch via NFS. In addition all nodes provide local scratch space at /localscratch (excludes queue tinymem). The Openlava scheduler automatically makes directories in both these scratch areas for each job (named after JOBPID). Backup services for /home are provided via disk-to-disk point-in-time snapshots from node ''sharptail'' to node ''cottontail'' disk arrays. (daily, weekly, monthly snapshots are mounted read only on ''cottontail'' for self-serve content retrievals). Some chemists have their home directories on node ''ringtail'' which provides 33 TB via /home33. Some psyc folks also have their own storage of 110 TB via /mindstore. In addition no-quota, no-backup user directories can be requested in /homeextra1 (7 T) or /homeextar2 (5 T). | All queues are available for job submissions via all login nodes. Some nodes on Infiniband switches for parallel computational jobs (queues: me256fd, hp12). Our total job slot count is roughly 2,144 with our physical core count 1,480. Our total teraflops compute capacity is about 58 cpu side, 25 gpu side (double precision floating point) and 702 gpu side (mixed mode). Our total memory footprint is about 528 GB gpu side, 8,532 GB cpu side. |
| |
Two Rstore storage servers each provide about 104 TB of usable backup space which is not mounted on the compute nodes. Each Rstore server's content is replicated to a dedicated passive standby server of same size, located in same data center but in different racks. As of Spring 2019 we have added two new Rstore servers of 220 T each, fully backed up with replication. | Home directory file system are provided (via NFS or IPoIB) by the node ''sharptail'' (our file server) from a direct attached disk array. In total, 10 TB of /home disk space is accessible to the users. Node ''greentail52'' makes available 55 TB of scratch space at /sanscratch via NFS. In addition all nodes provide local scratch space at /localscratch (excludes queue tinymem). The scheduler automatically makes directories in both these scratch areas for each job (named after JOBPID). Backup services for /home are provided via disk-to-disk point-in-time snapshots from node ''sharptail'' to node ''cottontail'' disk arrays. (daily, weekly, monthly snapshots are mounted read only on ''cottontail'' for self-serve content retrievals). Some faculty have their home directories on node ''ringtail'' which provides 33 TB via /home33. Some faculty also have their own storage (2x 110 TB via /mindstore). In addition no-quota, no-backup user directories can be requested in /homeextra1 (7 T) or /homeextra2 (5 T). All home directories will migrate to a FreeNAS/ZFS appliance named ''hpcstore'' in 2020 (190T usable, scalable to 1.2P). |
| |
| Two (old) Rstore storage servers each provide about 104 TB of usable backup space which is not mounted on the compute nodes. Each Rstore server's content is replicated to a dedicated passive standby server of same size, located in same data center but in different racks. As of Spring 2019 we have added two new Rstore servers of 220 T each, fully backed up with replication. |
| |
| |