Readme file
for IBM® Spectrum LSF 10.1 fix 601284
Abstract
P104744. This
fix supports the following enhancements to LSF:
· Global job IDs
· Global policies
· Addition of the VM_TYPE and RC_ACCOUNT fields to JOB_FINISH2 events
· Enhanced BSUB_QUIET behavior for
customized job submission output
· An all option for several commands
· Automatic cgroup creation.
This fix is
applicable for LSF Fix Pack 12 or later.
Description
Readme
documentation for IBM® Spectrum LSF 10.1 fix 601284 including installation-related
instructions, prerequisites and co-requisites, and list of fixes.
This fix provides the following new features and enhancements:
|
ID |
Description |
|
2547 |
Job IDs can now be configured to be unique across clusters. Use
the new Index column available for
the lsf.shared configuration
file. Assign a unique index to every cluster
involved so that each cluster will generate job IDs ending with the index
configured; for example: When global job IDs are enabled, the last two digits of the job
ID are used to identify the cluster index (for example, for job 12345601, the
cluster index is 01). This reduces the digit range of the job ID; therefore,
ensure that you configure both the MAX_JOBID setting in the lsb.params configuration file,
and the LSB_JOBID_DISP_LENGTH setting in the lsf.conf configuration file,
to enlarge the digit limits. For example, the default value of MAX_JOBID is
999999. To keep the same range for the job ID, explicitly configure MAX_JOBID=99999999 in lsb.params, and configure LSB_JOBID_DISP_LENGTH=9 in lsf.conf. |
|
2738 |
LSF now
supports global policies: · You
can now configure global limit scheduling to apply resource allocation limits
to multiple clusters in the lsb.globalpolicies
configuration file. When
using global limit scheduling, job group limits are still applied when the
jobs are forwarded to another cluster. · You
can configure global resources that are shared between all connected clusters
in the lsb.globalpolicies
file. |
|
SPCLSF-824 |
A new RC_ACCOUNT field is now added to JOB_FINISH2 events in the lsb.stream configuration file. |
|
SPCLSF-825 |
A new VM_TYPE field is now added to JOB_FINISH2
events in
the lsb.stream configuration file. To enable the VM_TYPE field to display in JOB_FINISH2 events, the following configuration is
required: User data
scripts on cloud provisioned hosts must be configured to retrieve this value
and add it to the LSF_LOCAL_RESOURCES setting in the lsf.conf configuration file on the provisioned
host. |
|
SPCLSF-847 |
The behavior of
the BSUB_QUIET environment variable for customized output for the bsub
command has changed: · When
BSUB_QUIET is set to JOBID, only the submitted job’s ID will be printed. · When
BSUB_QUIET is set to QUEUE, only the submitted job’s ID and queue will be
printed. · If
BSUB_QUIET is to anything else, then nothing will be printed for the
submitted job. |
|
SPCLSF-851 |
LSF now supports all as a value for the -o output option for the bjobs, busers, bqueues, and bhosts commands. If you run these
commands with the -o
all
option, the commands output every field defined in the application. |
|
SPCLSF-854 |
LSF now supports automatic cgroup creation. When enabled, LSF will automatically allocate a cgroup of one core per job task for all newly submitted jobs. This feature can be enabled by setting LSF_CGROUP_CORE_AUTO_CREATE=Y in the lsf.conf configuration file |
Readme file for: IBM®
Spectrum LSF
Product or component release: 10.1
Update name: Fix 601284
Fix ID: LSF-10.1-build601284
Publication date: 12
September 2022
Contents
1. List of fixes
2. Download location
3. Product or components affected
4. System requirements
5. Installation and configuration
6. List of files
7. Product notifications
8. Copyright and trademark information
1. List of
fixes
2547
2738
SPCLSF-824
SPCLSF-825
SPCLSF-847
SPCLSF-851
SPCLSF-854
2. Download
locations
Download fix
601284 from the following location: https://www.ibm.com/support/fixcentral
3. Product or
components affected
Affected
product or components in this fix reflect the list of enhancements previously
described:
The following
components in all Linux packages:
mbatchd
mbschd
ebrokerd
sbatchd
res
lim
badmin
bsub
bjobs
bqueues
bhosts
busers
blimits
bhist
bctrld
lsadmin
lsload
lshosts
lsclusters
gpolicyd
bgpinfo
mgres
resource_connector/openstack/scripts/example_user_data.sh
resource_connector/cyclecloud/scripts/example_user_data.sh
resource_connector/aws/scripts/example_user_data.sh
resource_connector/ibmcloudgen2/scripts/example_user_data.sh
resource_connector/google/scripts/example_user_data.sh
resource_connector/azure/scripts/example_user_data.sh
resource_connector/ibmcloudgen2/scripts/vpc_vm_dns.py
The following
components in Aix packages:
mbatchd
mbschd
ebrokerd
sbatchd
res
lim
badmin
bsub
bjobs
bqueues
bhosts
busers
blimits
bhist
bctrld
lsadmin
lsload
lshosts
lsclusters
gpolicyd
bgpinfo
4. System
requirements
linux2.6-glibc2.3-x86_64
linux3.10-glibc2.17-x86_64
linux3.10-glibc2.17-ppc64le
aix-64
5.
Installation and configuration
Before you install
LSF_TOP is the full path to the top-level installation directory of LSF.
1. You must have LSF 10.1 Fix Pack 12 or later installed before you install this fix. Download this fix pack from IBM Fix Central (https://www.ibm.com/support/fixcentral) and search for build600488 (Fix Pack 12) or build601088 (Fix Pack 13).
2. Starting in LSF 10.1 Fix Pack 13, the default values of the following three GPU parameters are changed to:
LSF_GPU_AUTOCONFIG=Y
LSB_GPU_NEW_SYNTAX=extend
LSF_GPU_RESOURCE_IGNORE=Y
If you have Fix Pack 13 installed, the above GPU parameters not configured in the lsf.conf configuration file will take the default values above, and the parameters already configured in the lsf.conf file will not be affected.
If you want to keep the former GPU behavior, and if any of the three parameters are missing in the lsf.conf configuration file, you must explicitly configure the following default settings that are defined in Fix Pack 12 or earlier:
LSF_GPU_AUTOCONFIG=N
LSB_GPU_NEW_SYNTAX=N
LSF_GPU_RESOURCE_IGNORE=N3. Log on to the LSF management host as the LSF primary administrator
4. Set the LSF cluster environment:
- For csh or tcsh: % source LSF_TOP/conf/cshrc.lsf
- For sh, ksh, or bash: $ . LSF_TOP/conf/profile.lsf5. Run badmin hclose all
6. Run badmin qinact all
Installation steps
1. Log on to the LSF management host as root and set the LSF cluster environment.
2. Go to the installation directory for the fix: cd $LSF_ENVDIR/../10.1/install/.
3. Copy the fix file to the installation directory $LSF_ENVDIR/../10.1/install/.
4. Run the patchinstall command: ./patchinstall <fix>.
After you install
1. Log on to the LSF management host as the LSF primary cluster administrator and set the LSF cluster environment.
2. Run lsadmin limrestart all
3. Run lsadmin resrestart all
4. Run badmin hrestart all
5. Run badmin gpdrestart if enable global policy feature.
6. Run badmin mbdrestart
7. Run badmin hopen all
8. Run badmin qact all