User Tools

Site Tools


cluster:89

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:89 [2010/10/21 11:29]
hmeij
cluster:89 [2010/11/22 14:05] (current)
hmeij
Line 28: Line 28:
   * x.y.z.254 is head or log in node   * x.y.z.254 is head or log in node
   * x.y.z.0 is gateway   * x.y.z.0 is gateway
-  * x.y.z.<10 is for all switches and console ports +  * x.y.z.<10 is for all switches (prefer 1) and console/management ports 
-  * x.y.z.10( up to 253) is for all compute nodes+  * x.y.z.10(up to 253) is for all compute nodes
  
 We are planning to ingest our Dell cluster (37 nodes) and our Blue Sky Studios cluster (130 nodes) into this setup, hence the approach. We are planning to ingest our Dell cluster (37 nodes) and our Blue Sky Studios cluster (130 nodes) into this setup, hence the approach.
  
 Netmask is, finally, 255.255.0.0 (excluding public 129.133 subnet). Netmask is, finally, 255.255.0.0 (excluding public 129.133 subnet).
 +
 +----
 +
 +Update with the following:
 +Hi Shanna, ok, i see that, so globally lets go with
 + 
 +eth0 192.168.102.x/255.255.0.0\\
 +eth1 10.10.102.x/255.255.0.0 (data, need to reach netapp filer at 10.10.0.y/255.255.0.0)\\
 +eth2 129.133.1.226 public (wesleyan.edu)\\
 +eth3 192.168.103.x/255.255.255.0 ipmi (or over eth0?)\\
 +eth4 192.168.104.x/255.255.255.0 ilo (or over eth0?)\\
 +ib0 10.11.103.x/255.255.255.0 ipoib (data)\\
 +ib1 10.11.104.x/255.255.255.0 ipoib (data, not used at the start)\\
 + 
 +where x=254 for head and x=10(increment by 1) for nodes n1-n32
 + 
 +does that work for you?  i'm unsure how ilo/ipmi works but it could use eth0.
 + 
 +-Henk
 +
 +
 +----
 +
 +
  
 ===== Infiniband ===== ===== Infiniband =====
Line 57: Line 81:
   * eth1, data/private, 10.10.102.254/255.255.0.0 (greentail-eth1, should go to ProCurve 2610)   * eth1, data/private, 10.10.102.254/255.255.0.0 (greentail-eth1, should go to ProCurve 2610)
   * eth2, public, 129.133.1.226/255.255.255.0 (greentail.wesleyan.edu, we provide cable connection)   * eth2, public, 129.133.1.226/255.255.255.0 (greentail.wesleyan.edu, we provide cable connection)
-  * eth3 (over eth2), ipmi, 192.168.103.254/255.255.0.0,  (greentail-ipmi, should go to better switch ProCurve 2910, do later)+  * eth3 (over eth0), ipmi, 192.168.103.254/255.255.0.0,  (greentail-ipmi, should go to better switch ProCurve 2910, do later)
     * see discussion iLo/IPMI under CMU     * see discussion iLo/IPMI under CMU
   * ib0, ipoib, 10.10.103.254/255.255.0.0 (greentail-ib0)   * ib0, ipoib, 10.10.103.254/255.255.0.0 (greentail-ib0)
Line 66: Line 90:
   * /snapshot mount point for snapshot volume ~ 10tb    * /snapshot mount point for snapshot volume ~ 10tb 
   * /sanscratch mount point for sanscratch volume ~ 5 tb   * /sanscratch mount point for sanscratch volume ~ 5 tb
-  * logical volume LOCALSCRATCH: mount at /localscratch ~ 100 gb (should match nodes at 160 gb, leave rest for OS)+  * /localscratch ... maybe just a directory
   * logical volumes ROOT/VAR/BOOT/TMP: defaults   * logical volumes ROOT/VAR/BOOT/TMP: defaults
  
Line 90: Line 114:
 [[http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c01800572&prodTypeId=18964&prodSeriesId=489496|HP Link]] (compute nodes) [[http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c01800572&prodTypeId=18964&prodSeriesId=489496|HP Link]] (compute nodes)
  
-    * node names hp000, increment by 1 +    * node names n0, increment by 1 
-    * eth0, provision, 192.168.102.25(increment by 1)/255.255.0.0 (hp000-eth0, should go to better switch ProCurve 2910) +    * eth0, provision, 192.168.102.10(increment by 1)/255.255.0.0 (n0-eth0, should go to better switch ProCurve 2910) 
-      * do we need an iLo eth? in range 192.168.104.25(increment by 1)+      * do we need an iLo eth? in range 192.168.104.10(increment by 1)
       * CMU wants eth0 on NIC1 and PXEboot       * CMU wants eth0 on NIC1 and PXEboot
-    * eth1, data/private, 10.10.102.25(increment by 1)/255.255.0.0 (hp000-eth1, should go to ProCurve 2610) +    * eth1, data/private, 10.10.102.10(increment by 1)/255.255.0.0 (n0-eth1, should go to ProCurve 2610) 
-    * eth2 (over eth1), ipmi, 192.168.103.25(increment by 1)/255.255.0.0, (hp000-ipmi, should go to better switch ProCurve 2910, do later)+    * eth2 (over eth0), ipmi, 192.168.103.10(increment by 1)/255.255.0.0, (n0-ipmi, should go to better switch ProCurve 2910, do later)
       * see discussion iLo/IPMI under CMU       * see discussion iLo/IPMI under CMU
-    * ib0, ipoib, 10.10.103.25(increment by 1)/255.255.0.0 (hp000-ib0) +    * ib0, ipoib, 10.10.103.10(increment by 1)/255.255.0.0 (n0-ib0) 
-    * ib1, ipoib, 10.10.104.25(increment by 1)/255.255.0.0 (hp000-ib1, configure, might not have cables!)+    * ib1, ipoib, 10.10.104.10(increment by 1)/255.255.0.0 (n0-ib1, configure, might not have cables!)
  
     * /home mount point for home directory volume ~ 10tb (contains /home/apps/src)     * /home mount point for home directory volume ~ 10tb (contains /home/apps/src)
cluster/89.1287674972.txt.gz · Last modified: 2010/10/21 11:29 (external edit)