Differences

This shows you the differences between two versions of the page.

--- cluster:79 [2009/08/21 19:50] – hmeij
+++ cluster:79 [2013/04/18 19:40] (current) – hmeij
@@ Line 1: / Line 1: @@
 \\
 **[[cluster:0|Back]]**
+Deprecated.  We only have rack running (on demand) offering access to 1.1 TB of memory.  The bss24 queue on head node greentail represents the Blue Sky Studio job slots available.
+ --- //[[hmeij@wesleyan.edu|Meij, Henk]] 2013/04/18 15:39//
+==== ====
 {{:cluster:sht.jpg|sharptail saltmarsh sparrow}}
+Update: 21 Sept 09
+Cluster sharptail has undergone some changes.  Courtesy of ITS, 2 more blade enclosures have permanently been added.  Another 3 blade enclosures have temporarily been added (destined for another ITS project so they may disappear in the future but in the meantime I figure it could be put to good use).  That means
+Cluster sharptail has 129 compute nodes, 258 job slots, and a total memory footprint of 2,328 GB Cluster swallowtail has 36 compute nodes, 288 job slots, and a total memory footprint of 244 GB
+On cluster sharptail, four queues have been set up.  Also, Gaussian optimized for AMD Opteron chips as well as a Linda version are available.
+https://dokuwiki.wesleyan.edu/doku.php?id=cluster:73#gaussian
+We’ll have some documentation soon, but in the meantime there are links to resources on the web.
+Queue ‘bss12’ and ‘bss24’ are comprised of nodes with either 22 GB or 24 GB of memory per node (2 single core CPUs).  When using Linda, the target node names need to be listed (somewhat silly) instead of letting the scheduler find free nodes.  So queues ‘bss12g16’ and ‘bss24g16’ have been set up with 8 predefined hosts each.  These queues will not accept jobs requiring less than 16 job slots, the idea being you submit Linda jobs with #BSUB –n 16 and %NProcs=16.
 ===== Cluster: sharptail =====
@@ Line 19: / Line 39: @@
-The operating system is **[[http://centos.org|CentOS]]**,  version 5.3 at this time.  This is much like Redhat but not completely.  All software compiled in /share/apps has been compiled under RHEL 5.1 and hence may not work in CentOS 5.3.  We will recompiled software when requested and post it in /share/apps/centos53 ... all commercial software will only run on petaltail and swallowtail.
+The operating system is **[[http://centos.org|CentOS]]**,  version 5.3 at this time.  This is much like Redhat but not completely.  All software compiled in /share/apps has been compiled under RHEL 5.1 and hence may not work in CentOS 5.3.  We will recompile software when requested and post it in /share/apps/centos53 ... all commercial software will only run on petaltail and swallowtail.
 The scheduler is **[[http://hpccommunity.org|Lava]]**, that is, a recent version of LSF but not the latest. All regular commands for submitting jobs work the same way.  The only difference is the advanced queue settings are missing like fairshare, pre-emption, backfill etc.
@@ Line 27: / Line 47: @@
 As such, we will start to implement a soft policy that the Infiniband switch is dedicated to jobs that invoke MPI parallel programs.  That is queue "imw" on petaltail and swallowtail.
-Their are still some minor configurations that need to be implemented but you are invited to put cluster sharptail to work.
+There are still some minor configurations that need to be implemented but you are invited to put cluster sharptail to work.
+This page will be updated with solutions to problems found or questions asked.
+All your tools will remain on **[[http://petaltail.wesleyan.edu|petaltail.wesleyan.edu]]**
+===== Questions =====
+**Are the LSF and Lava scheduler working togther?**
+No.  They are two physically and logically individual cluster.
+**How can i determine if my program or the program i am using will work on sharptail?**
+When programs compile on a certain host, they link themselves against system and sometimes custom libraries. If they are missing on another host, the program will not run.  To check, use 'ldd', if none are missing you are good to go.
+<code>
+[hmeij@sharptail ~]$ ldd /share/apps/python/2.6.1/bin/python
+        libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003679e00000)
+        libdl.so.2 => /lib64/libdl.so.2 (0x0000003679600000)
+        libutil.so.1 => /lib64/libutil.so.1 (0x0000003687000000)
+        libm.so.6 => /lib64/libm.so.6 (0x0000003679a00000)
+        libc.so.6 => /lib64/libc.so.6 (0x0000003679200000)
+        /lib64/ld-linux-x86-64.so.2 (0x0000003678e00000)
+</code>
+If one or more libraries are missing, you could run this command on petaltail or swallowtail, observe were the libraries are located, and if they exist on sharptail, add that path to LD_LIBRARY_PATH. Otherwise the programs need to be recompiled if they are supported on CentOS 5.3 x86_64.
+===== Picture =====
+Some organic wiring schema.
-This page will be update with solutions to problems found or questions asked.
+{{:cluster:bss_racks.jpg|detail of wiring}}
-=====  =====
+==== ====
 \\
 **[[cluster:0|Back]]**