Euler - Revision history

Anderson at 22:18, 19 February 2020

2020-02-19T22:18:49Z

Anderson at 22:16, 19 February 2020

2020-02-19T22:16:54Z

Anderson at 22:16, 19 February 2020

2020-02-19T22:16:02Z

Anderson at 22:15, 19 February 2020

2020-02-19T22:15:37Z

Anderson at 21:57, 19 February 2020

2020-02-19T21:57:17Z

Anderson at 21:41, 19 February 2020

2020-02-19T21:41:56Z

Anderson at 21:37, 19 February 2020

2020-02-19T21:37:54Z

Anderson at 21:24, 17 June 2015

2015-06-17T21:24:01Z

Anderson at 19:57, 8 January 2015

2015-01-08T19:57:50Z

Anderson at 16:13, 22 July 2014

2014-07-22T16:13:30Z

@@ Line 65: / Line 65: @@
 <h3>Python</h3>
-A special note about python is in order.  There are three versions of python installed:  2.4 (the default), 2.6.6, and 2.7.2.
+A special note about python is in order.  There are many versions of python installed:  2.4 is the default.
 You can set your python version using the 'module' command.  Examples that do what you think they do are:
   module load python/2.7.2

@@ Line 29: / Line 29: @@
 If you must subvert the batch system selection provided by qlogin, it is possible to ssh directly into the
-compute nodes. They are named compute-0-0 through compute-0-5, compute-1-1 through compute-1-3, and compute-2-0 through compute-2-5 and are accessible only through the frontend (euler.lbl.gov). This is not recommended unless you have a good reason.
+compute nodes. They are named  compute-1-0 through compute-1-2, and compute-2-0 through compute-2-5 and are accessible only through the frontend (euler.lbl.gov). This is not recommended unless you have a good reason.
 <h3>Batch Jobs</h3>

@@ Line 1: / Line 1: @@
 <h1>Overview of EULER Cluster</h1>
-euler.lbl.gov is a computing cluster consisting of one frontend node and sixteen dedicated compute nodes. The cluster runs Rocks Cluster 6.6, which is a collection of cluster management tools built on top of [http://www.centos.org CentOS 6.6] ( a standard Redhat Enterprise rebuild, like Scientific Linux). Job scheduling is through Sun Grid Engine (SGE) 6.2u4.
+euler.lbl.gov is a computing cluster consisting of one frontend node and nine dedicated compute nodes. The cluster runs Rocks Cluster 6.6, which is a collection of cluster management tools built on top of [http://www.centos.org CentOS 6.6] ( a standard Redhat Enterprise rebuild, like Scientific Linux). Job scheduling is through Sun Grid Engine (SGE) 6.2u4.
 The first time you login to the system you may be asked to generate an SSH key. The process will be started automatically. You will be prompted for a passphrase. This key will only be used to migrate jobs from the frontend to the various compute nodes. It is recommended that you enter an empty passphrase for this key. Otherwise you will have to have an active ssh-agent process running all the time or your batch jobs will not be able to be started. There are no security implications of making the passphrase for this particular key empty (as long as you don't distribute the private key residing in ~/.ssh, of course).

@@ Line 13: / Line 13: @@
 <h2>Storage Configuration</h2>
 * /home -- The user home directories reside on the frontend's 23TB disk and are NFS exported to all the compute nodes.
-* /home/data --The frontend's 23TB disk array is NFS exported to the compute nodes at /home/data. Users can create subdirectories under /home/data as on a standard scratch disk and the contents will be accessible from any compute node.
+* /home/data3 --The frontend's 23TB disk array is NFS exported to the compute nodes at /home/data3. Users can create subdirectories under /home/data3 as on a standard scratch disk and the contents will be accessible from any compute node.
-* /home/data1 --A large (5.4TB) network mounted disk with a 4Gbit/sec connection to the cluster.  The disk is configured as a standard scratch disk, just like /home/data.
+* /home/data1 --A large (5.4TB) network mounted disk with a 4Gbit/sec connection to the cluster.  The disk is configured as a standard scratch disk, just like /home/data3.
-* /home/data2 --A large (4.6TB) network mounted disk with a 4Gbit/sec connection to the cluster.  The disk is configured as a standard scratch disk, just like /home/data.
+* /home/data2 --A large (4.6TB) network mounted disk with a 4Gbit/sec connection to the cluster.  The disk is configured as a standard scratch disk, just like /home/data3.
 * /state/partition1 -- Each compute node has a local working area mounted at /state/partition1. These areas are local to each node and are not visible to the other nodes. If your job is disk intensive, you may wish to have your jobscript copy files onto the local work space at the beginning of the job. If your job writes files into the local work space, be sure to have your jobscript move them out when it is done. This is for two reasons. First, you will not necessarily know what node your job ran on, so it may be difficult to find the files later. Second, it leaves the node clean for the next user.

@@ Line 6: / Line 6: @@
 <h2>Hardware</h2>
 *The frontend has a 2.1GHz Intel XEON E5-2620 processor (thirty-two cores) with 64GB of RAM. It has a 4TB disk, plus a 23TB RAID array.
 *Three compute nodes have two 2.5GHz quad-core Xeon processors (eight cores) with 16GB of RAM and a 750GB local disk.
 *Six compute nodes have two 2.4GHz six-core Xeon processors ( twelve cores ) with 24GB of RAM and a 1TB local disk.
@@ Line 13: / Line 12: @@
 <h2>Storage Configuration</h2>
-* /home -- The user home directories reside on the frontend's 250GB disk and are NFS exported to all the compute nodes.
+* /home -- The user home directories reside on the frontend's 23TB disk and are NFS exported to all the compute nodes.
-* /home/data --The frontend's 750GB disk array is NFS exported to the compute nodes at /home/data. Users can create subdirectories under /home/data as on a standard scratch disk and the contents will be accessible from any compute node.
+* /home/data --The frontend's 23TB disk array is NFS exported to the compute nodes at /home/data. Users can create subdirectories under /home/data as on a standard scratch disk and the contents will be accessible from any compute node.
 * /home/data1 --A large (5.4TB) network mounted disk with a 4Gbit/sec connection to the cluster.  The disk is configured as a standard scratch disk, just like /home/data.
 * /home/data2 --A large (4.6TB) network mounted disk with a 4Gbit/sec connection to the cluster.  The disk is configured as a standard scratch disk, just like /home/data.

← Older revision		Revision as of 19:57, 8 January 2015
Line 35:		Line 35:

	* Batch jobs are submitted to the cluster via the command qsub. There are a total of 110 slots.		* Batch jobs are submitted to the cluster via the command qsub. There are a total of 110 slots.
		+
		+	* Currently the cluster is partitioned into two queues: long and short.
		+	* You can submit jobs to these queues via 'qsub -q long myscript.sh' or 'qsub -q short myscript.sh'

@@ Line 8: / Line 8: @@
 <h2>Hardware</h2>
 *The frontend has a 2.4GHz Intel Core 2 Duo processor (two cores) with 4GB of RAM. It has a 250GB disk, plus a 750GB RAID array.
-*Seven compute nodes have a 2.4GHz Intel Core 2 Duo processor (two cores) with 4GB of RAM and a 250GB local disk.
+*Five compute nodes have a 2.4GHz Intel Core 2 Duo processor (two cores) with 4GB of RAM and a 250GB local disk.
 *Three compute nodes have two 2.5GHz quad-core Xeon processors (eight cores) with 16GB of RAM and a 750GB local disk.
 *Six compute nodes have two 2.4GHz six-core Xeon processors ( twelve cores ) with 24GB of RAM and a 1TB local disk.