LSF Version 7.3 - Running Jobs With Platform LSF

◆ Mapped to hosts in lsf.cluster. cluster_name
The combination of host type and CPU speed (CPU factor) of the computer.
All hosts of the same relative speed are assigned the same host model.
The CPU factor is taken into consideration when jobs are being dispatched.
◆ lsinfo -m—View a list of currently running models
◆ lsinfo -M—View all models defined in lsf.shared
◆ Defined in lsf.shared
◆ Mapped to hosts in lsf.cluster. cluster_name
Users and administrators
A user account that has permission to submit jobs to the LSF cluster.
In general, you must be an LSF administrator to perform operations that will affect
other LSF users. Each cluster has one primary LSF administrator, specified during LSF
installation. You can also configure additional administrators at the cluster level and at
the queue level.
The first cluster administrator specified during installation and first administrator listed
in
lsf.cluster. cluster_name . The primary LSF administrator account owns
the configuration and log files. The primary LSF administrator has permission to
perform clusterwide operations, change configuration files, reconfigure the cluster, and
control jobs submitted by all users.
May be specified during LSF installation or configured after installation. Cluster
administrators can perform administrative operations on all jobs and queues in the
cluster. Cluster administrators have the same cluster-wide operational privileges as the
primary LSF administrator except that they do not necessarily have permission to
change LSF configuration files.
For example, a cluster administrator can create an LSF host group, submit a job to any
queue, or terminate another user’s job.
An LSF administrator user account that has administrative permissions limited to a
specified queue. For example, an LSF queue administrator can perform administrative
operations on the specified queue, or on jobs running in the specified queue, but cannot
change LSF configuration or operate on LSF daemons.
Resources
The LSF system uses built-in and configured resources to track resource availability and
usage. Jobs are scheduled according to the resources available on individual hosts.
Jobs submitted through the LSF system will have the resources they use monitored while
they are running. This information is used to enforce resource limits and load thresholds
as well as fairshare scheduling.
LSF collects information such as:
◆ Total CPU time consumed by all processes in the job