IBM Spectrum LSF 10.1 Fix Pack 11
(600128) Readme
Abstract
LSF Version 10.1 Fix Pack 11. This Fix Pack includes new
issues and solutions resolved between 2 Jun 2020 and
12 Nov 2020 .
Description
Readme documentation for IBM Spectrum
LSF 10.1 Fix Pack 11 (600128) including installation-related
instructions, prerequisites and co-requisites.
The CORAL-reported issues addressed in LSF Version 10.1 Fix Pack 11:
ID
|
Description
|
P103870
|
An enhancement to LSF fairshare component.
The fairshare run time field type has been changed from int to long to avoid a potential overflow problem.
|
The new CORAL-requested solutions in LSF Version 10.1 Fix Pack 11: |
ID
|
Description
|
RFE#142731
|
An enhancement to LSF that allows you to use
the -f parameter with the 'brsvmod addhost' command in a similar way
to using the brsvadd command.
|
For further details on these solutions and other new features
in LSF 10.1.0.11, refer to https://www.ibm.com/support/knowledgecenter/SSWRJV_10.1.0/lsf_release_notes/lsf_relnotes_whatsnew10.1.0.11.html
The python package is updated and tested against LSF 10.1.0.11 in this fix.
JSM is updated to 10.4.0.03rtm4 in this fix.
Readme file for: IBM® Spectrum LSF
Product/Component Release: 10.1.0.11
Update Name: Fix 600128
PMR/APAR: not available
Fix ID: lsf-10.1-build600128-csm
Publication date: 4 Feb
2021
Last modified date: 4
Feb 2021
Contents:
- List of fixes
- Download location
- Product notifications
- Products or components affected
- System requirements
- Installation and configuration
- List of files
- Copyright and trademark information
- List of fixes
P103870, RFE#142731
- Download Location
Download Fix 600128 from the following location: http://www.ibm.com/eserver/support/fixes/
- Product notifications
To receive information about product solution and patch
updates automatically, subscribe to product notifications on
the My notifications page http://www.ibm.com/support/mynotifications/
on the IBM Support website (http://support.ibm.com). You can
edit your subscription settings to choose the types of
information you want to get notification about, for example,
security bulletins, fixes, troubleshooting, and product
enhancements or documentation changes.
- Products or components affected
lsf-common-10.1.0.11-600128.ppc64le.rpm
lsf-master-10.1.0.11-600128.ppc64le.rpm
lsf-misc-10.1.0.11-600128.ppc64le.rpm
lsf-python2-api-1.0.6-10.1.0.11.ppc64le.rpm
lsf-server-10.1.0.11-600128.ppc64le.rpm
ibm_jsm-10.4.0.03rtm4-rh8_20210112.ppc64le.rpm
lsf-conf-10.1.0.11-600128.noarch.rpm
lsf-man-pages-10.1.0.11-600128.noarch.rpm
lsf-client-10.1.0.11-600128.x86_64.rpm
lsf-python2-api-1.0.6-10.1.0.11.x86_64.rpm
- System requirements
linux3.10-glibc2.17-ppc64le
- Installation and configuration
6.1 Before
installation
- 1. Shutdown LSF on all work load manager (WLM) and launch
node (LN) hosts.
- 2. Back up the LSF configuration from the conf ($LSF_ENVDIR)
directory and any scripts or binary files that you added to
the LSF_SERVERDIR directory (for example, customized elims,
esubs, stage in pre-scripts, stage out post scripts).
- 3. Run rpm -qa| grep lsf to list the currently installed rpm
files.
- 4. Use yum erase or rpm -evh to unistall the existing LSF
packages.
rpm -ev --allmatches -notriggers 'list of filenames as they
appear in step 3'
6.2 Installation
steps
-
6.2.1 Server
Package Instructions
Download lsf-10.1.0.11-600128.ppc64le_csm.bin package
Run lsf-10.1.0.11-600128.ppc64le_csm.bin to extract the
RPM files. Accept the license agreement when prompted to
continue with the file extraction.
lsf-common-10.1.0.11-600128.ppc64le.rpm
lsf-master-10.1.0.11-600128.ppc64le.rpm
lsf-misc-10.1.0.11-600128.ppc64le.rpm
lsf-server-10.1.0.11-600128.ppc64le.rpm
lsf-python2-api-1.0.6-10.1.0.11.ppc64le.rpm
ibm_jsm-10.4.0.03rtm4-rh8_20210112.ppc64le.rpm
Use rpm -ivh or yum install commands to deploy the common,
server, and master RPM packages. The installation is
relocatable (--prefix options supported)
On the work load manager
rpm -ivh lsf-common-10.1.0.11-600128.ppc64le.rpm
lsf-server-10.1.0.11-600128.ppc64le.rpm
lsf-master-10.1.0.11-600128.ppc64le.rpm
On the launch node
rpm -ivh lsf-common-10.1.0.11-600128.ppc64le.rpm
lsf-server-10.1.0.11-600128.ppc64le.rpm
Verify that the installation is successful:
rpm -qa | grep lsf
lsf-server-10.1.0.11-600128.ppc64le
lsf-common-10.1.0.11-600128.ppc64le
lsf-master-10.1.0.11-600128.ppc64le
6.2.2 X86_64
Client Package Instructions
Obtain and run lsf-client-10.1.0.11-600128.x86_64.bin
package to extract the rpm packages. This should be done
on x86_64 client host.
lsf-conf-10.1.0.11-600128.noarch.rpm
lsf-man-pages-10.1.0.11-600128.noarch.rpm
lsf-client-10.1.0.11-600128.x86_64.rpm
lsf-python2-api-1.0.6-10.1.0.11.x86_64.rpm
The installation directory is
/opt/ibm/spectrumcomputing/lsf.
The user lsfadmin must be added if it does not exist on
the host before installing the lsf-conf rpm package.
rpm -ivh ./lsf-conf-10.1.0.11-600128.noarch.rpm
./lsf-man-pages-10.1.0.11-600128.noarch.rpm
./lsf-client-10.1.0.11-600128.x86_64.rpm
./lsf-python2-api-1.0.6-10.1.0.11.x86_64.rpm
Verify that the installation is successful:
rpm -qa | grep lsf
lsf-conf-10.1.0.11-600128.noarch
lsf-man-pages-10.1.0.11-600128.noarch
lsf-client-10.1.0.11-600128.x86_64
lsf-python2-api-1.0.6-10.1.0.11.x86_64
-
6.3 After
installation
- 6.3.1 Server Package
Restore previously backed up LSF conf directory and any
customized scripts or binaries in LSF_SERVERDIR
- (Optional) Under LSF_TOP:
Rename work.rpmsave to work
- Using bash: On each WLM and LN, run the following commands
as root:
- . /opt/ibm/spectrumcomputing/lsf/conf/profile.lsf
or if you have used the --prefix to define your own LSF_TOP
. /conf/profile.lsf
- Start up LSF
lsf_daemons start
6.3.2 X86_64 Client Package
- Configuring client hosts within your
cluster.
Log on to the LSF master host as the user lsfadmin.
Static Client
It is recommended that the x86_64 hosts be configured as
static clients.
Edit the LSF_CONFDIR/lsf.cluster.cluster_name file and add
host information for the new host to the Host section.
- - Add the name of the host.
- - Add model or type.
- o If you enter the ! keyword in
the model and type columns, the host model and type
reported by LSF will be UNKNOWN.
- o Alternatively, X86_64 can be
specified for type.
- - Specify LSF server or client in
the server column:
- o You must specify 0 (zero) to
indicate an LSF client-only host.
Begin
Host
HOSTNAME model
type server RESOURCES
<<
snip >>
clienthost !
X86_64 0 ()
End
Host
It is important that all host names of client hosts added
to the cluster are resolvable by the management nodes.
Depending on your site's DNS, you can configure a
$LSF_ENVDIR/hosts file that includes all official names
and IP addresses of the client hosts. If LSF cannot
resolve the host name of a client host it will reject
requests originating from that host.
Float Client
Alternatively, you could configure the x86_64 hosts as
floating clients. You do not add the host information for
the new host to the Host section of the
LSF_CONFDIR/lsf.cluster.cluster_name file. You must add
the parameters FLOAT_CLIENTS_ADDR_RANGE and FLOAT_CLIENTS
to the Parameters section of the
LSF_CONFDIR/lsf.cluster.cluster_name file.
The FLOAT_CLIENT parameter sets the maximum allowable size
for floating clients in a cluster. If FLOAT_CLIENTS is not
specified in lsf.cluster.cluster_name, the floating LSF
client feature is disabled. When the LSF floating client
feature is enabled, any host can submit jobs to the
cluster. You can limit which hosts can be LSF floating
clients with the parameter FLOAT_CLIENTS_ADDR_RANGE.
The FLOAT_CLIENTS_ADDR_RANGE specifies IP address or range
of addresses of domains from which floating client hosts
can submit requests.
A floating client can join the cluster only when an LSF
command is run from this host and LSF has verified it
against FLOAT_CLIENTS (total number of floating clients)
and FLOAT_CLIENTS_ADDR_RANGE (IP range). After
verification, it is listed by the lshosts command. A
floating client expires at 12:00 midnight or when the
master LIM is reconfigured or restarted.
Begin
Parameters
FLOAT_CLIENTS_ADDR_RANGE=
IP_address
...
FLOAT_CLIENTS=
number_of_floating_clients
End
Parameters
Now reconfigure the cluster.
- Reconfigure lim to enable the new host
in the cluster.
% lsadmin reconfig
- Restart mbatchd.
-
% badmin mbdrestart
Check your connectivity
Run the lsid and bhosts command from a client
host. these commands should return the same information as
if they were run from a CORAL server machine.
Submitting Jobs
When submitting jobs from an x86_64 client host and your
cluster's execution hosts are not x86_64 you should specify
the resource requirement -R 'type==any'. This tells LSF to
ignore host type when selecting hosts for the job. Note that
when submitting CSM job in easy mode the resource
requirement is automatically set.
6.4 Uninstallation
- 6.4.1 Server Package
Shut down LSF on all WLM and LN hosts.
lsf_daemons stop
Back up the LSF conf directory and any customized scripts or
binaries as stated in previous steps.
Use yum erase or rpm -evh commands to unistall LSF following
the same previous steps.
6.4.2 X86_64 Client Package
Log on to the x86_64 client host. Use the rpm uninstall
command to uninstall the rpm packages.
# rpm -ev --allmatches --notriggers
lsf-client-10.1.0.11-600128.x86_64
lsf-man-pages-10.1.0.11-600128.noarch
lsf-conf-10.1.0.11-600128.noarch
lsf-python2-api-1.0.6-10.1.0.11.x86_64
- List of files
lsf-10.1.0.11-600128.ppc64le_csm.bin
lsf-client-10.1.0.11-600128.x86_64.bin
The contents
of lsf-10.1.0.11-600128.ppc64le_csm.bin:
lsf-common-10.1.0.11-600128.ppc64le.rpm
lsf-master-10.1.0.11-600128.ppc64le.rpm
lsf-misc-10.1.0.11-600128.ppc64le.rpm
lsf-python2-api-1.0.6-10.1.0.11.ppc64le.rpm
lsf-server-10.1.0.11-600128.ppc64le.rpm
ibm_jsm-10.4.0.03rtm4-rh8_20210112.ppc64le.rpm
The contents
of lsf-client-10.1.0.11-600128.x86_64.bin:
lsf-conf-10.1.0.11-600128.noarch.rpm
lsf-man-pages-10.1.0.11-600128.noarch.rpm
lsf-client-10.1.0.11-600128.x86_64.rpm
lsf-python2-api-1.0.6-10.1.0.11.x86_64.rpm
- Copyright and trademark information
© Copyright IBM Corporation 2021
U.S. Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM
Corp.
IBM®, the IBM logo and ibm.com® are trademarks of
International Business Machines Corp., registered in many
jurisdictions worldwide. Other product and service names might
be trademarks of IBM or other companies. A current list of IBM
trademarks is available on the Web at "Copyright and trademark
information" at www.ibm.com/legal/copytrade.shtml