The project must be a valid license project configured in the lsf.licensescheduler file. If your usage section specifies a feature that you configured in the lsf.licensescheduler file, and you do not submit your job to a license project, the job is submitted to the default license project unless LSF_LIC_SCHED_STRICT_PROJECT_NAME=y in lsf.conf and you have not configured a default project for the required feature.
This submits a job called myjob to the default license project (unless LSF_LIC_SCHED_STRICT_PROJECT_NAME=y in lsf.conf and you have not configured a default project for the required feature) and requests one AppB license.
If your queue or job starter scripts request a license that is managed by an LSF ELIM, you need to update the job submission scripts to request that license using the license token name.
bsub -R "select[type==any] order[resource_name] rusage[token_name=1]" -Lp license_project_name job_name
bsub -R "select[type==any] order[cpuf] rusage[feature1=1]" -Lp Lp1 my_jobname
You can sort by other factors such as swp, ut, and r1m in your order string.
Configure the resource requirement string and host list in lsb.queues:
Begin Queue
QUEUE_NAME = fastqueue
PRIORITY = 10
HOSTS = hostA+1 hostB+2 hostC hostD+1
RES_REQ = select[type==any] rusage[feature1=1]
End Queue
Configure your host list based on desirability. This depends on your own knowledge of the capability of each host. In this example, you decide that:
After configuring lsb.queues, use badmin reconfig, then submit jobs: