IBM Spectrum LSF 10.1 Fix 506432 Readme File
Abstract
This solution supports Variable Use licensing for dynamic compute workloads that extend to the cloud, enabling you to optimize cloud-based resource usage with cost-effective pay-as-you-go licensing. With this enhancement, administrators can configure their IBM Spectrum LSF cluster to upload CPU core, CPU socket, GPU socket, and host count through an external load index monitor (ELIM) to a metering service in IBM Cloud Private 3.1. They can then audit IBM Spectrum LSF resource usage from the metering dashboard in IBM Cloud Private.
Description
Readme documentation for IBM Spectrum LSF 10.1 Fix 506432 including installation-related instructions, prerequisites and co-requisites, and list of fixes.
This fix addresses the following solution:
This solution supports Variable Use licensing for dynamic compute workloads that extend to the cloud, enabling you to optimize cloud-based resource usage with cost-effective pay-as-you-go licensing. With this enhancement, administrators can configure their IBM Spectrum LSF cluster to upload CPU core, CPU socket, GPU socket, and host count through an external load index monitor (ELIM) to a metering service in IBM Cloud Private 3.1. They can then audit IBM Spectrum LSF resource usage from the metering dashboard in IBM Cloud Private.
Readme file for: IBM® Spectrum LSF and LSF suite
Product/Component Release: LSF 10.1 and LSF suite 10.2
Update Name: Fix 506432
Fix ID: lsf-10.1-build506432 for LSF; suite-10.2.0.6-build506432 for LSF suite.
Publication date: 15 November 2018
Last modified date: 13 November 2018
Contents:
1. List of fixes
2. Download location
3. Products or components affected
4. System requirements
5. Known Issue
6. Installation and configuration
7. List of files
8. Product notifications
9. Copyright and trademark information
1. List of fixes
N/A
2. Download Location
Download Fix 506432 from the following location: http://www.ibm.com/eserver/support/fixes/
3. Products or components affected
Affected components include: LSF/elim.icp.uploader
4. System requirements
Linux2.6-glibc2.3-x86_64
Lnx310-lib217-x86_64
Note: For the LSF Suite, only linux2.6-glibc2.3-x86_64 is supported.
5. Known Issue
In the cluster failover scenario for the LSF Suite Version 10.2, the elim.icp.uploader fails to start automatically on the secondary master host. If you encounter this issue, get the fix from Fix Central (Fix ID: lsf-10.1-build506622). The workaround is to start the elim.icp.uploader manually by running /opt/ibm/lsfsuite/lsf/10.1/linux2.6-glibc2.3-x86_64/etc/elim.icp.uploader in the background.
6. Installation and configuration
6.1 Before installation
(LSF_TOP=Full path to the top-level installation directory of LSF.)
1) Log on to the LSF master host as root
2) Set your environment:
- For csh or tcsh: % source LSF_TOP/conf/cshrc.lsf
- For sh, ksh, or bash: $ . LSF_TOP/conf/profile.lsf
6.2 Installation steps
1) Go to the patch install directory: cd $LSF_ENVDIR/../10.1/install/
2) Copy the patch file to the install directory $LSF_ENVDIR/../10.1/install/
3) Extract the patch file. Run "zcat <patch tar file>|tar xvf -".
Copy elim.icp.uploader to the /opt/ibm/lsfsuite/lsf/10.1/<system version>/etc directory.
6.3 Configuration and usage
Install IBM Cloud Private 3.1 to take advantage of resource usage metering. The metering service is automatically installed as part of the IBM Cloud Private environment.
1) If you are licensed to install IBM Cloud Private 3.1, see https://www.ibm.com/support/knowledgecenter/SSBS6K_3.1.0/kc_welcome_containers.html.
2) To install IBM Cloud Private 3.1 Community Edition, see https://www.ibm.com/support/knowledgecenter/SSBS6K_3.1.0/installing/install_containers_CE.html..
After applying this enhancement in your IBM Spectrum LSF cluster and with your IBM Cloud Private cluster ready, complete the following steps:
1) Generate an API key for the IBM Cloud Private 3.1 metering service.
2) Configure IBM Spectrum LSF to upload usage data to IBM Cloud Private 3.1.
Generate an API key for the metering service:
Log on to the IBM Cloud Private boot node and obtain the cluster configuration details according to step 3 in https://www.ibm.com/support/knowledgecenter/SSBS6K_3.1.0/manage_cluster/cfc_cli.html.
Using the following cloudctl commands, log in as the administrator (admin) and generate an API key, substituting the current node's IP address for <my_icp_IP>:
1) cloudctl login -a https://<my_icp_IP>:8443 -u admin -p admin -n default --skip-ssl-validation
2) cloudctl iam service-id-create spectrumserviceid-default-1 -d "SPECTRUM serviceid in default namespace, number 1"
3) cloudctl iam service-api-key-create spectrumapikey-default-1 spectrumserviceid-default-1
The output of the last command displays the API key, which is similar to the following:
"OiiJ1q3gjIDk2JJGxHK6xeZwU5mrIHyu2nUv38SzrQSA"
Save this key to add to the icpup.json file in step below.
Configure IBM Spectrum LSF to upload usage data
1) Log in to the LSF master host as root, edit the $LSF_ENVDIR/lsf.shared configuration file, and add the following line to the Resource section:
totalcores Numeric 15 Y (Total CPU cores in the cluster)
2) Edit the $LSF_ENVDIR/lsf.cluster.* configuration file and add the following line to the Resource Map section.
totalcores [all]
3) Create the new $LSF_ENVDIR/icpup.json file and insert the following contents, replacing <my_icp_IP> and <my_API_key> with actual values:
{
"icpUrl": "https://<my_icp_IP>:8443",
"apiKey": "<my_API_key>",
"logLevel": "LOG_INFO"
}
To set the log level, edit the logLevel parameter to any of the following values: LOG_INFO, LOG_WARNING, LOG_ERR, or LOG_DEBUG.
4) Restart lim on LSF master host.
- Run the "lsadmin limrestart" command.
- For clusters running LSF Suite Version 10.2, run the "systemctl restart lsfd" command.
5) Check the ELIM status in the $LSF_TOP/log/elim.icpup.log.<hostname> file. For clusters running LSF Suite Version 10.2, check the ELIM status in the /opt/ibm/lsflogs/elim.icpup.log.<hostname> file.
6) Log in to the IBM Cloud Private console and navigate to the Metering page to see the uploaded usage data. For more information, see https://www.ibm.com/support/knowledgecenter/SSBS6K_3.1.0/manage_metrics/metering_service.html.
The following metrics are uploaded to IBM Cloud Private: CPU core and GPU socket data for the previous two days are immediately uploaded to the Metering page. Host and socket usage is uploaded from the current time. The system collects metrics every 5 minutes and uploads to the metering service every 15 minutes.
6.4 Uninstallation To roll back a patch: 1) Log on to the LSF master host as root 2) Remove /opt/ibm/lsfsuite/lsf/10.1/<system version>etc/elim.icp.uploader. 3) Rollback the configration files change in section 6.3. 4) Run lsadmin limrestart
7. List of files
elim.icp.uploader
8. Product notifications
To receive information about product solution and patch updates automatically, subscribe to product notifications on the My notifications page (www.ibm.com/support/mynotifications) on the IBM Support website (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.
9. Copyright and trademark information
© Copyright IBM Corporation 2018
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.
a) Total Hosts: Total number of available and closed hosts in the cluster. The other metrics are for these reported hosts and do not include unavailable hosts.
b) Total Cores: Total number of CPU cores on the reported hosts.
c) Total GPUs: Total number of GPU processors on the reported hosts.
d) Total Sockets: Total number of CPU sockets on the reported hosts.