User Tools

Site Tools


cluster:88

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
cluster:88 [2010/08/11 11:50]
hmeij
cluster:88 [2010/08/17 15:56] (current)
hmeij
Line 79: Line 79:
     * name: kusu101prov,​ type: provision     * name: kusu101prov,​ type: provision
     * eth1: 10.10.101.254/​255.255.0.0     * eth1: 10.10.101.254/​255.255.0.0
-    * name: kusupriv, type: other+    * name: kusu101priv, type: other
   * 4 - gateway & dns: gateway 192.168.101.0 (is not used but required field), dns server 192.168.101.254 (installer node)   * 4 - gateway & dns: gateway 192.168.101.0 (is not used but required field), dns server 192.168.101.254 (installer node)
   * 5 - host: FQDN kusu101, PCD kusu101 (basically we will not provide internet accessible names)   * 5 - host: FQDN kusu101, PCD kusu101 (basically we will not provide internet accessible names)
Line 177: Line 177:
 Now reboot the entire cluster and observe changes to be permanent. Sidebar: for Pace, you can now on the installer node assign eth1 a pace.edu IP, and have the necessary changes made to the ProCurve switch, so your users can log into the installer/​head node.  You still only have 50 gb or so of home directory space but users can play around.  ​ Now reboot the entire cluster and observe changes to be permanent. Sidebar: for Pace, you can now on the installer node assign eth1 a pace.edu IP, and have the necessary changes made to the ProCurve switch, so your users can log into the installer/​head node.  You still only have 50 gb or so of home directory space but users can play around.  ​
  
 +Actually had a better idea: create another node group template from your _BSS template and remove eth1, naming convention login#N and set starting IP to something like 192.168.101.10 ... call this node group _BSS_login or so.  Start addhost, add new host to this node group. ​ Next manually add eth1 with IP in pace.edu and wire up via switch to outside world. ​ Next add this host to the list of LSF_MASTER_LIST. ​ Now users can log into this node and submit jobs and stay out of your way on the installer node. 
  
 ===== Step 5 ===== ===== Step 5 =====
Line 264: Line 265:
 ===== Step 6 ===== ===== Step 6 =====
  
-More fun. Parallel jobs can be submitted over ethernet interconnects but will not achieve the performance of Infiniband interconnects ofcourse. ​ OpenMPI is a nice MPI flavor ​becuase ​software compiled with it automatically detects if the host has an HCA card or not and will allocate the appropriate libraries. So in order to compile, or run, some OpenMPI examples we need the following:+More fun. Parallel jobs can be submitted over ethernet interconnects but will not achieve the performance of Infiniband interconnects ofcourse. ​ OpenMPI is a nice MPI flavor ​because ​software compiled with it automatically detects if the host has an HCA card or not and will allocate the appropriate libraries. So in order to compile, or run, some OpenMPI examples we need the following:
  
-  * yum install libibverbspdsh yum install libibverbs -q -y+  * yum install libibverbs 
 +  * pdsh yum install libibverbs -q -y
   * yum install gcc-c++   * yum install gcc-c++
  
Line 272: Line 274:
  
   * download tarball, stage in /​home/​apps/​src   * download tarball, stage in /​home/​apps/​src
-  * cd /opt; tar zxvf /​home/​apps/​src/​mpis.tar.gzpdsh "cd /opt; tar zxvf /​home/​apps/​src/​mpis.tar.gz"​+  * cd /opt; tar zxvf /​home/​apps/​src/​mpis.tar.gz 
 +  * pdsh "cd /opt; tar zxvf /​home/​apps/​src/​mpis.tar.gz"​
   * examples in /​opt/​openmpi/​gnu/​examples have been compiled like so:   * examples in /​opt/​openmpi/​gnu/​examples have been compiled like so:
     * export PATH=/​opt/​openmpi/​gnu/​bin:​$PATH     * export PATH=/​opt/​openmpi/​gnu/​bin:​$PATH
Line 280: Line 283:
  
 Ok, so now we need write a script to submit a parallel job.  A parallel job is submitted with command '​mpirun'​. ​ However that command needs to know which hosts are allocated to the job.  That is done with a wrapper script located in /​usr/​bin/​openmpi-mpirun. Ok, so now we need write a script to submit a parallel job.  A parallel job is submitted with command '​mpirun'​. ​ However that command needs to know which hosts are allocated to the job.  That is done with a wrapper script located in /​usr/​bin/​openmpi-mpirun.
 +
 +  * irun
  
 <​code>​ <​code>​
 #!/bin/bash #!/bin/bash
 +
 +rm -f err out 
  
 #BSUB -e err #BSUB -e err
 #BSUB -o out #BSUB -o out
-#BSUB +#BSUB -n 4 
 +#BSUB -q normal 
 +#BSUB -J ptest
  
 export PATH=/​opt/​openmpi/​gnu/​bin:​$PATH export PATH=/​opt/​openmpi/​gnu/​bin:​$PATH
Line 294: Line 303:
 which mpirun which mpirun
  
 +/​usr/​bin/​openmpi-mpirun /​opt/​openmpi/​gnu/​examples/​hello_c
  
 +/​usr/​bin/​openmpi-mpirun /​opt/​openmpi/​gnu/​examples/​ring_c
  
-<​code>​+</code> 
 + 
 +  * 'bsub < irun' (submits) 
 +  * '​bjobs'​ (check status) 
 + 
 +===== Step 7 =====
  
 +Tools. As you add nodes, monitoring tools are added to Ganglia and Cacti. ​ These are useful to look at.
  
 +But first we must fix firefox. ​ You can down load a tarball here [[http://​lsfdocs.wesleyan.edu/​firefox.tar.gz|http://​lsfdocs.wesleyan.edu/​firefox.tar.gz]],​ stage in /​usr/​local/​src and untar, then link the firefox executable in /​usr/​local/​bin.
  
 +  * '​startx'​ to start the gnome gui
 +  * '​firefox'​ to start browser
 +  * http://​localhost/​ganglia
 +  * http://​localhost/​cacti (first login, admin/​admin,​ set a new password ... admin ;), you can let users in via guest/​guest)
 +  * http://​localhost:​3000 (for ntop)
  
 +  * http://​localhost/​[ cfm | kits | repos ] (the kits one will show all kusu commands available)
 +  * http://​lsfdocs.wesleyan.edu ( lsf 6.2 guides, close to lava )
  
 \\ \\
 **[[cluster:​0|Back]]** **[[cluster:​0|Back]]**
cluster/88.1281541806.txt.gz · Last modified: 2010/08/11 11:50 by hmeij