LSF Version 7.3 - Administering Platform LSF

How Resources are Classified
234 Administering Platform LSF
How Resources are Classified
Resource categories
By values
By the way values
change
By definitions
By scope
Boolean resources
Boolean resources (for example, server to denote LSF server hosts) have a value of
one (1) if they are defined for a host, and zero (0) if they are not defined for the host.
Use Boolean resources to configure host attributes to be used in selecting hosts to
run jobs. For example:
◆ Machines may have different types and versions of operating systems.
◆ Machines may play different roles in the system, such as file server or compute
server.
◆ Some machines may have special-purpose devices needed by some
applications.
◆ Certain software packages or licenses may be available only on some of the
machines.
Specify a Boolean resource in a resource requirement selection string of a job to
select only hosts that can run the job.
Boolean resources Resources that denote the availability of specific features
Numerical resources Resources that take numerical values, such as all the load
indices, number of processors on a host, or host CPU factor
String resources Resources that take string values, such as host type, host model,
host status
Dynamic Resources Resources that change their values dynamically: host status and
all the load indices.
Static Resources Resources that do not change their values: all resources except
for load indices or host status.
External Resources Custom resources defined by user sites: external load indices
and resources defined in the lsf.shared file (shared resources).
Built-In Resources Resources that are always defined in LSF, such as load indices,
number of CPUs, or total swap space.
Host-Based
Resources
Resources that are not shared among hosts, but are tied to
individual hosts, such as swap space, CPU, or memory. An
application must run on a particular host to access the
resources. Using up memory on one host does not affect the
available memory on another host.
Shared Resources Resources that are not associated with individual hosts in the
same way, but are owned by the entire cluster, or a subset of
hosts within the cluster, such as floating licenses or shared file
systems. An application can access such a resource from any
host which is configured to share it, but doing so affects its value
as seen by other hosts.