User Tools

Site Tools


condo_queues

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
condo_queues [2016/09/19 17:52]
pwolinsk
condo_queues [2018/09/24 21:22]
pwolinsk
Line 3: Line 3:
 The Condo program allows individual users to purchase computing hardware with their own funds and use AHPCC staff to provide installation,​ power, cooling, networking and maintenance services. ​ The condo hardware owner has priority access to the condo nodes and has no job walltime restriction. ​ However, the condo nodes are also available for public use for up to 6 hour walltime jobs.  The 6 hour limit may be extended upon request if there are no condo owner jobs waiting in the queue. The Condo program allows individual users to purchase computing hardware with their own funds and use AHPCC staff to provide installation,​ power, cooling, networking and maintenance services. ​ The condo hardware owner has priority access to the condo nodes and has no job walltime restriction. ​ However, the condo nodes are also available for public use for up to 6 hour walltime jobs.  The 6 hour limit may be extended upon request if there are no condo owner jobs waiting in the queue.
  
-The ''​**qcondo_public**''​ queue should be used by non-condo ​users.  ​To get a listing of the available nodes in that queue on Trestles:+All condo nodes are accessible via two queues: ​''​**qcondo_public**'' ​and ''​**qcondo**''​. ​ The qcondo_public ​queue is unrestricted and available for all users.  ​The ''​qcondo'' ​queue is restricted and available for use by condo node owners and their research groups **only**.
  
-<​code>​ 
-tres-l1:​pwolinsk:​$ node-queue-map |grep qcondo_public 
-qcondo_public 8 tres0733 tres0734 tres0735 tres0736 tres0833 tres0834 tres0835 tres0836 ​ 
-</​code>​ 
- 
-In a regular (non-condo) queue all nodes are identical; have same cpus, memory, etc. - have the same properites. ​ The ''​**qcondo_public**''​ queue is different. ​ Individual nodes where purchased by different users and have different properties. ​ To get a listing of properties for an individual node: 
- 
-<​code>​ 
-tres-l1:​pwolinsk:​$ pbsnodes tres0733 |grep properties 
-     ​properties = mib,​douglas,​m768gb 
- 
-</​code>​ 
  
 ==== Trestles ==== ==== Trestles ====
Line 48: Line 36:
  
 <​code>​ <​code>​
-razor-l1:​pwolinsk:​$ for i in `node-queue-map |grep qcondo |cut -d" " -f3-`; do echo -n "$i "; pbsnodes $i |grep properties; ​donecompute0805 ​     ​properties = mib,​ib,​gpu,​k40gpu,​m64gb+razor-l1:​pwolinsk:​$ for i in `node-queue-map |grep qcondo |cut -d" " -f3-`; do echo -n "$i "; pbsnodes $i |grep properties; ​done 
 +compute0805 ​     ​properties = mib,​ib,​gpu,​k40gpu,​m64gb
 compute1153 ​     properties = qib,​ib,​laurent,​m24gb compute1153 ​     properties = qib,​ib,​laurent,​m24gb
 compute1154 ​     properties = qib,​ib,​laurent,​m24gb compute1154 ​     properties = qib,​ib,​laurent,​m24gb
Line 64: Line 53:
 </​code>​ </​code>​
  
-To submit ​a job to ''​**qcondo_public**''​ queue on Razor to use 2 node with property k80gpu (node with Nvidia K80 GPU):+==== qcondo_public - Unrestricted Access ==== 
 +The ''​**qcondo_public**''​ queue can be used by all users.  ​To get a listing of the available nodes in that queue on Trestles: 
 + 
 +<​code>​ 
 +tres-l1:​pwolinsk:​$ node-queue-map |grep qcondo_public 
 +qcondo_public 8 tres0733 tres0734 tres0735 tres0736 tres0833 tres0834 tres0835 tres0836  
 +</​code>​ 
 + 
 +In a regular (non-condo) queue all nodes are identical; have same cpus, memory, etc. - have the same properites. ​ The ''​**qcondo_public**''​ queue is different. ​ Individual nodes where purchased by different users and have different properties. ​ To get a listing of properties for an individual node: 
 + 
 +<​code>​ 
 +tres-l1:​pwolinsk:​$ pbsnodes tres0733 |grep properties 
 +     ​properties = mib,​douglas,​m768gb 
 + 
 +</​code>​ 
 + 
 +Below is an example of submitting ​a job to ''​**qcondo_public**''​ queue on Razor to use 2 node with property k80gpu (node with Nvidia K80 GPU):
  
 <​code>​ <​code>​
 razor-l1:​pwolinsk:​$ qsub -q qcondo_public -l nodes=2:​ppn=24:​k80gpu hostname.pbs ​ razor-l1:​pwolinsk:​$ qsub -q qcondo_public -l nodes=2:​ppn=24:​k80gpu hostname.pbs ​
 1774072.sched 1774072.sched
 +</​code>​
  
 +==== qcondo - Restricted Access ====
 +
 +The ''​**qcondo**''​ queue should only be used by condo node owners and their research groups. ​ To submit jobs to this queue the owner property must be specified during job submission. ​ Below is an example of submitting a job to one of the nodes in the qcondo queue which belongs to the "​douglas"​ condo group:
 +
 +<​code>​tres-l1:​pwolinsk:​$ qsub -q qcondo -l walltime=200:​00:​00 -l nodes=1:​ppn=32:​douglas hostname.pbs
 +283336.torque
 +tres-l1:​pwolinsk:​$ ​
 </​code>​ </​code>​
 +
 +**NOTE:** the owner property must be present when submitting to the ''​qcondo''​ queue.
 +
 ==== Property Code Summary ==== ==== Property Code Summary ====
 <csv> <csv>
condo_queues.txt · Last modified: 2018/09/24 21:22 by pwolinsk