Difference between revisions of "Endeavour"

From Nuclear Physics Group Documentation Pages
Jump to navigationJump to search
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
= Endeavour =
 
= Endeavour =
  
−
Here are the notes on this system.<br>
+
Endeavour was purchased as part of a full cluster, from Microway (quote: MWYQ11029 ~ $16,000 for base system) <br>
 +
It came with 13 x2 Number Smasher nodes (Total was ~$90,000) <br>
 +
Arrived at UNH in April 2009.
 +
 
 
'''Notes on configuration status/changes and ToDo is at the bottom.'''
 
'''Notes on configuration status/changes and ToDo is at the bottom.'''
  
Line 11: Line 14:
 
Hardware Temperature monitoring  [http://10.0.0.98 10.0.0.98] <br>
 
Hardware Temperature monitoring  [http://10.0.0.98 10.0.0.98] <br>
 
Cacti Statistics:                [http://roentgen.unh.edu/cacti roentgen.unh.edu/cacti]
 
Cacti Statistics:                [http://roentgen.unh.edu/cacti roentgen.unh.edu/cacti]
 +
 +
== RAID Setup ==
 +
 +
* Endeavour has an Areca RAID card on 10.0.0.199.
 +
* There are 24 channels in the RAID card.
 +
* Current setup:
 +
** RAID SET #00 - 9 disks @ 2TB each = 18 TB raw. 3 Volume sets.
 +
***  0/0/0 - RAID 6 - 100 GB
 +
***  0/0/1 - RAID 6 - 100 GB
 +
***  0/0/2 - RAID 6 - 13.8 TB = data1
 +
** RAID SET #02 - 1 @  750 GB
 +
***  0/0/4 - Passthroudh
 +
** RAID SET +04 - 12 disks @ 4TB each = 48 TB raw, 1 Volume set
 +
*** 0/0/6  - RAID 6 - 40 TB = data2
  
 
= Upgrading Nodes =
 
= Upgrading Nodes =
−
[Upgrading the nodes]
+
[[Upgrading the nodes]]
  
 
= System Usage =
 
= System Usage =
Line 19: Line 36:
 
This section explains some of the special use for this system.
 
This section explains some of the special use for this system.
  
−
== OpenPBS = Torque = Portable Batch System ==
+
== OpenPBS = [[Torque]] = Portable Batch System ==
−
 
 
−
[http://en.wikipedia.org/wiki/Portable_Batch_System PBS] is a system for scheduling compute jobs onto nodes, aka "workload management software", that was first created by NASA in the '90s. We ran this early version on our farm back then. It is very sophisticated and thus not so trivial to configure. Some things are already setup.
 
−
 
 
−
The company supporting the old open source version is [http://www.pbsgridworks.com/Default.aspx PBS Gridworks] which seems to be a devision of "Altair". They haven't touched their free open version since 2001.<br>
 
−
There are no manuals for '''OpenPBS''' from Altair, only for '''PBS Pro'''. To get to them, you need to create a username/password at the [https://secure.altair.com/UserArea/ PBS Pro User Area] you can then get to the [https://secure.altair.com/UserArea/docs.php Documentation]. Do not expect a one to one correspondence between the OpenPBS and PBSPro versions (like, you don't need a FLEX license for the open one.)
 
  
−
The newer development in OpenPBS is renamed '''Torque''', which is what is installed on our systems. See [http://www.clusterresources.com/ Cluster Resources] and go to [http://www.clusterresources.com/pages/products/torque-resource-manager.php Torque Resource Manager]. This includes documentation.
+
Toque, "PBS", "OpenPBS", is our batch system. Local information for [[Torque]]
  
 
=== Commands ===
 
=== Commands ===
Line 34: Line 46:
 
; xpbsmon  : Graphical interface to monitor nodes. It gives a quick view of node status. Use Ganglia for more sophisticated node stats.
 
; xpbsmon  : Graphical interface to monitor nodes. It gives a quick view of node status. Use Ganglia for more sophisticated node stats.
 
; [[qsub]]    : Command-line tool for submitting jobs to PBS
 
; [[qsub]]    : Command-line tool for submitting jobs to PBS
 +
; qstat        : Information on what is on the queue
 +
; showq      : Information on what is on the queue from the *scheduler* maui. -- Tells you what job will run next.
 +
; maui : Use 'sudo /etc/init.d/maui restart' to restart if the queuing system goes down
  
 
=== qperf Command ===
 
=== qperf Command ===
Line 40: Line 55:
  
 
On the first node just run
 
On the first node just run
−
Tbow@node2 ~]$qperf
+
  qperf
 
On the second node run this to test Infiniband and ethernet
 
On the second node run this to test Infiniband and ethernet
−
Tbow@node3 ~]$qperf -t 5 node2.farm.physics.unh.edu rc_bi_bw tcp_bw
+
  qperf -t 5 node2.farm.physics.unh.edu rc_bi_bw tcp_bw
  
 
= Initial setup and Configuration =
 
= Initial setup and Configuration =
Line 72: Line 87:
 
# Figure out the monitoring system, Ganglia, and other Microway goodies.<font color="green" ><b>[partially done]</b></font>
 
# Figure out the monitoring system, Ganglia, and other Microway goodies.<font color="green" ><b>[partially done]</b></font>
 
# LDAP (client) on nodes?
 
# LDAP (client) on nodes?
−
# Practice PBS
 
 
# Test the Infiniband and MPICH setup.
 
# Test the Infiniband and MPICH setup.
−
# 24 hour full system burnin?
 
−
# Backups are not being run for endeavour.
 
 
   
 
   
 
=== Long Term To Do ===
 
=== Long Term To Do ===
Line 85: Line 97:
 
# Run a replicate LDAP server on Endeavour.
 
# Run a replicate LDAP server on Endeavour.
 
# Run a replicate Named (DNS) server on Endeavour and Roentgen.
 
# Run a replicate Named (DNS) server on Endeavour and Roentgen.
−
# Install Splunk and pass splunk data on to Pumpkin.
 
 
# Replicate home directories for selected users (this may be too tricky, really)? Else create a local copy of each user.
 
# Replicate home directories for selected users (this may be too tricky, really)? Else create a local copy of each user.

Latest revision as of 17:00, 7 August 2017

Endeavour

Endeavour was purchased as part of a full cluster, from Microway (quote: MWYQ11029 ~ $16,000 for base system)
It came with 13 x2 Number Smasher nodes (Total was ~$90,000)
Arrived at UNH in April 2009.

Notes on configuration status/changes and ToDo is at the bottom.

Endeavor web server is active: Endeavour
It runs the Ganglia monitoring software on Endeavour Ganglia

Endeavor RAID card is connected to: 10.0.0.199
Endeavor SWITCH is connected to 10.0.0.253
Hardware Temperature monitoring 10.0.0.98
Cacti Statistics: roentgen.unh.edu/cacti

RAID Setup

  • Endeavour has an Areca RAID card on 10.0.0.199.
  • There are 24 channels in the RAID card.
  • Current setup:
    • RAID SET #00 - 9 disks @ 2TB each = 18 TB raw. 3 Volume sets.
      • 0/0/0 - RAID 6 - 100 GB
      • 0/0/1 - RAID 6 - 100 GB
      • 0/0/2 - RAID 6 - 13.8 TB = data1
    • RAID SET #02 - 1 @ 750 GB
      • 0/0/4 - Passthroudh
    • RAID SET +04 - 12 disks @ 4TB each = 48 TB raw, 1 Volume set
      • 0/0/6 - RAID 6 - 40 TB = data2

Upgrading Nodes

Upgrading the nodes

System Usage

This section explains some of the special use for this system.

OpenPBS = Torque = Portable Batch System

Toque, "PBS", "OpenPBS", is our batch system. Local information for Torque

Commands

pbsnodes
This gives a quick overview of all the known nodes and whether they are up. If they are what the status is. "pbsnodes -a" lists everything about all the nodes, "pbsnodes -l up" shows a list of the nodes that are up, "pbsnodes -l down" the same for the ones that are down.
xpbs
Graphical interface to PBS. Really old and probably not that useful.
xpbsmon
Graphical interface to monitor nodes. It gives a quick view of node status. Use Ganglia for more sophisticated node stats.
qsub
Command-line tool for submitting jobs to PBS
qstat
Information on what is on the queue
showq
Information on what is on the queue from the *scheduler* maui. -- Tells you what job will run next.
maui
Use 'sudo /etc/init.d/maui restart' to restart if the queuing system goes down

qperf Command

qperf measures bandwidth and latency between two nodes. It can work over TCP/IP as well as the RDMA transports. 

There are many more tests to use (rc_bi_bw) built in on the man page.

On the first node just run 

 qperf

On the second node run this to test Infiniband and ethernet 

 qperf -t 5 node2.farm.physics.unh.edu rc_bi_bw tcp_bw

Initial setup and Configuration

  • Set the UNH IP address (endeavour.unh.edu) on eth1. [done]
    • This made the system think of itself as "endeavor" rather than "master", causing PBS to get confused. PBS in /var/spool/pbs adjusted, also the maui scheduler in /usr/local/maui/maui.cfg modified. [done]
  • I switched the IP address on eth0 to 10.0.0.100 from 10.0.0.1 (since that is the usual gateway address, and we want to bridge the two backend networks.) [done]
    • This requires ALL "hosts" files on the nodes to be modified [done,all nodes but 25]
    • Also, the /root/.shosts /root/.rhosts and /etc/ssh/ssh_known_hosts /etc/ssh/shosts.equiv files need to be copied from node2 to node* [done,all nodes but 25]
    • The file /var/spool/pbs/server_name needs to be updated as well [done,all nodes but 25]
    • The /etc/pam.d/system-auth-ac needs to include the ldap module. (NOT DONE only for 2,3)
  • Set the root password to standard scheme. [done,master only]
  • Setup the LDAP client side. [done,master only]
  • Recompiled PBS to include the xpbs and xpbsmon commands.[done]
  • Configured and started the iptables firewall [done,master only]
  • Integrated the backend network with the farm backend network (bridged the network switches) [done]
  • Setup automount, standard /net/data and /net/home [done,master only]
    • TODO: We need a new rule that resolves /net/data/node2 for the disk in node2 etc. The nodes need to export their /scratch partition. The other partitions may not be needed, since the "rcpf" command (a foreach with rcp) can copy files in batch.
  • The /etc/nodes file included the "master" node. This is too dangerous. It means that in a batch copy the file is also automatically copy back to the master, with potentially dangerous results.
  • To add users to the "microway Ganglia control" part, add them to /etc/mcms.users Password is login password, LDAP is honored.
  • Setup and started SPLUNK - runs its own server, and forwards to pumpkin.
  • Added endeavour disks /data1 and /data2 to the export table and the LDAP auto.data table, so ls /net/data/endeavour{1,2} works.
  • On node2 (so far) to get users and home directories integrated:
    • Copy /etc/ldap.conf /etc/openldap/* to node from endeavour.
    • copy /etc/nsswitch.conf to node from endeavour.
    • restart autofs (/etc/init.d/autofs restart)

TO DO

  1. Figure out the monitoring system, Ganglia, and other Microway goodies.[partially done]
  2. LDAP (client) on nodes?
  3. Test the Infiniband and MPICH setup.

Long Term To Do

Possible long term tasks if manpower is available.

Long term goal is to have Endeavour as an independent system is need be.

  1. Run a replicate LDAP server on Endeavour.
  2. Run a replicate Named (DNS) server on Endeavour and Roentgen.
  3. Replicate home directories for selected users (this may be too tricky, really)? Else create a local copy of each user.
Retrieved from "https://nuclear.unh.edu/wiki/index.php?title=Endeavour&oldid=6212"