25.06.2015 Views

Administering Platform LSF - SAS

Administering Platform LSF - SAS

Administering Platform LSF - SAS

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Network Floating Licenses<br />

Licenses used outside of <strong>LSF</strong> control<br />

Example<br />

lsf.shared<br />

To handle the situation where application licenses are used by jobs outside of<br />

<strong>LSF</strong>, use an ELIM to dynamically collect the actual number of licenses available<br />

instead of relying on a statically configured value. The ELIM periodically<br />

informs <strong>LSF</strong> of the number of available licenses, and <strong>LSF</strong> takes this into<br />

consideration when scheduling jobs.<br />

Assuming there are a number of licenses for the Verilog package that can be<br />

used by all the hosts in the cluster, the <strong>LSF</strong> configuration files could be set up<br />

to monitor this resource as follows:<br />

Begin Resource<br />

RESOURCENAME TYPE INTERVAL INCREASING DESCRIPTION<br />

verilog Numeric 60 N (Floating<br />

licenses for Verilog)<br />

End Resource<br />

lsf.cluster.cluster_name<br />

Begin ResourceMap<br />

RESOURCENAME LOCATION<br />

verilog<br />

([all])<br />

End ResourceMap<br />

The INTERVAL in the lsf.shared file indicates how often the ELIM is<br />

expected to update the value of the Verilog resource—in this case every 60<br />

seconds. Since this resource is shared by all hosts in the cluster, the ELIM only<br />

needs to be started on the master host. If the Verilog licenses can only be<br />

accessed by some hosts in the cluster, specify the LOCATION field of the<br />

ResourceMap section as ([hostA hostB hostC ...]). In this case an ELIM<br />

is only started on hostA.<br />

Submitting jobs<br />

The users would submit jobs requiring verilog licenses as follows:<br />

% bsub -R "rusage[verilog=1:duration=1]" myprog<br />

Configuring a dedicated queue for floating licenses<br />

Example<br />

Whether you run all license jobs through <strong>LSF</strong> or run jobs that use licenses that<br />

are outside of <strong>LSF</strong> control, you can configure a dedicated queue to run jobs<br />

requiring a floating software license.<br />

For each job in the queue, <strong>LSF</strong> reserves a software license before dispatching<br />

a job, and releases the license when the job finishes.<br />

Use the bhosts -s command to display the number of licenses being reserved<br />

by the dedicated queue.<br />

The following example defines a queue named q_verilog in lsb.queues<br />

dedicated to jobs that require Verilog licenses:<br />

Begin Queue<br />

QUEUE_NAME = q_verilog<br />

RES_REQ=rusage[verilog=1:duration=1]<br />

End Queue<br />

282<br />

<strong>Administering</strong> <strong>Platform</strong> <strong>LSF</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!