- What's new
This fix patch introduces the energy accounting feature, which
installs the lsfbeat and Logstash tool
into the LSF cluster. lsfbeat calls the ipmitool to collect the energy
data of
each host and to send the
data to Logstash, then Logstash send data to Elasticsearch for LSF
Explorer. The LSF bjobs and bhosts
commands get the energy data from LSF Explorer and display it.
- Download location
Download 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 and components affected
LSF Explorer Data Collector
LSF Explorer Server
LSF (all edition except CE)
- System requirements
- Linux 2.6 glibc 2.3 x86 64 bit, Red Hat 6.5, 6.8,6.9
- Linux 3.10 glibc 2.17 x86 64 bit, Red Hat 7.2,7.3,7.4
- Linux 3.0 glibc 2.11 x86 64 bit, SUSE 11.2, 11.3
- Linux 3.11 glibc 2.18 x86 64 bit, SUSE 12
- Linux for Power Systems Servers 8 Little Endian (Linux kernel
3.10, glibc 2.17):
Red Hat Enterprise Linux 7.1, 7.2,7.3
- Linux for Power Systems Servers 8 Little Endian (Linux kernel
4.4, glibc2.26): Ubuntu 16.04 LTS
- Installation and configuration
- In this document,
assume the IBM Spectrum LSF Explorer is installed under /opt/ibm
- 6.1 Pre-requisites
- Ensure your clusters
are running LSF V10.1.0 Fix Pack 4 and are configured correctly
for energy accounting, as follows:
Configuring Energy Accounting data collection for IBM Spectrum LSF
clusters:
Edit $LSF_ENVDIR/lsf.conf, add below parameters:
LSF_ENABLE_BEAT_SERVICE="energy"
LSF_QUERY_ES_FUNCTIONS="energy"
LSF_QUERY_ES_SERVERS="ip:port"
#where "ip" is LSF Explorer
Server host IP, "port" is LSF Explorer Server GUI port, default port is
8080.
- Ensure that ipmitool
is installed on each host where you intend to collect energy data.
The ipmitool binary file needs to either be in the same location on all
hosts, or you need
to create a symbolic link for ipmitool to point to the location
specified by the IPMI_HOME
parameter in the install.config file when you installed the LSF
Explorer Data Collector.
In addition, ipmitool must be able to get power data on the host.
Check whether ipmitool can
get energy data normally, as root run command:
ipmitool sensor | grep Power
- 6.2 Backup Explorer Server and Data Collector before
instalIation
- Log in IBM Spectrum LSF Explorer Server and Data
Collector host as root.
- Determine the location of your existing IBM Spectrum LSF
Explorer Server and
Data Collector installation.
rpm -q --queryformat "%{INSTPREFIXES}\n"
lsf-explorer-server
rpm -q --queryformat "%{INSTPREFIXES}\n" lsf-perf
- Stop IBM Spectrum LSF Explorer Server services before
upgrade.
Set the LSF Explorer Server environment:
* For csh or tcsh: source /opt/ibm/lsfsuite/ext/cshrc.platform
* For sh, ksh, or bash: .
/opt/ibm/lsfsuite/ext/profile.platform
Stop the LSF Explorer Server services:
pmcadmin stop
Check that the LSF Explorer Server services have been stopped.
pmcadmin list
- Stop IBM Spectrum LSF Explorer Data Collector services
before upgrade.
Set the LSF Explorer Data Collector environment:
* For csh or tcsh: source /opt/ibm/lsfsuite/ext/perf/conf/cshrc.perf
* For sh, ksh, or bash: .
/opt/ibm/lsfsuite/ext/perf/conf/profile.perf
Stop the LSF Explorer Data Collector services:
perfadmin stop all
Check that the LSF Explorer Data Collector services have been stopped.
perfadmin
list
- Back up your existing installation.
For example, assuming that LSF Explorer Server and Data Collector are
installed on the same host
and the same directory /opt/ibm:
cp -rfp /opt/ibm /opt/ibm.bak
- 6.3 Installation steps for IBM Spectrum LSF Explorer
Server V10.2.0
- Log in as root to the IBM Spectrum LSF Explorer Server
V10.2.0 host on which you intend
to install this fix patch.
- Extract the fix patch package downloaded and navigate to
the directory.
For example:
tar -xvzf
explorer10.2_server_linux-x64.tar.gz
cd explorer10.2_server_linux-x64
- Edit the install.config file to set installation
variables. Ensure set INSTALL_ES=N ,and the value of
other variables are the same as the variables when you first installed
IBM Spectrum LSF Explorer
Server V10.2.0 on the host.
- Run the ExplorerServerInstaller.sh installation script
and finish the installation:
For example:
./ExplorerServerInstaller.sh
-f install.config
- Restart the IBM Spectrum LSF Explorer Server.
pmcadmin start
- Check that the IBM Spectrum LSF Explorer Server services
have started.
pmcadmin list
- Log in to the IBM Spectrum LSF Explorer Server GUI as LSF
Explorer administrator,
The default dashboard Cluster Overview is displayed.
- 6.4 Installation steps for IBM Spectrum LSF Explorer
Data Collectors V10.2.0
Important:
- Apply the following steps on all the LSF clusters one by
one where you installed LSF Explorer Data Collector.
- Before applying the patch, ensure the LSF clusters meet the pre-requisites
in 6.1.
-
- Log in to the IBM Spectrum LSF Explorer Data Collector
V10.2.0 host on which you
intend to intall this fix path by the same user used to install V10.2.0.
- Extract the downloaded fix patch package and navigate to
the directory.
For example:
tar -xvzf
explorer10.2_node_linux-x64.tar.gz
cd explorer10.2_node_linux-x64
- Edit the install.config file to set required
installation variables. Ensure that the value of
variables are the same as the variables when you first installed IBM
Spectrum LSF Explorer
Data Collector V10.2.0 on the host.
- Run the ExplorerNodeInstaller.sh installation script.
./ExplorerNodeInstaller.sh
-f install.config
Note: For a silent
installation, add the option -silent.
- Check that logstash service has started.
service logstash-for-lsf status
- [Optional] If the LSF cluster has other OS Types
installed that are different from the
OS Type of the LSF Explorer Data Collector host, ensure that you
install the lsfbeat service
for each OS Type.
6.a) determine which OS Types you need to install
lsfbeat service.
You can check which OS Types are installed in your
LSF cluster:
Navigate to $LSF_ENVDIR/../10.1, where you can see
which OS Types are installed in the LSF cluster.
This fix patch supports the following LSF OS types:
- linux2.6-glibc2.3-x86_64
- linux3.10-glibc2.17-x86_64
- linux3.10-glibc2.17-ppc64le
For example, if the LSF cluster has installed the
three OS Types and the LSF Explorer Data Collector
has been installed for type
linux2.6-glibc2.3-x86_64, you need to install the lsfbeat service for
other
two OS Types. Following step 6.b to finish
lsfbeat installation.
6.b) Install the lsfbeat service for different OS Types.
1) Install lsfbeat for
linux3.10-glibc2.17-x86_64 OS type if you have installed lsfbeat for
type linux2.6-glibc2.3-x86_64
create two links for lsfbeat:
ln -s
LSF_TOP/10.1/linux2.6-glibc2.3-x86_64/etc/lsfbeat
LSF_TOP/10.1/linux3.10-glibc2.17-x86_64/etc/lsfbeat
ln -s LSF_TOP/10.1/linux2.6-glibc2.3-x86_64/etc/lsfbeat.service
LSF_TOP/10.1/linux3.10-glibc2.17-x86_64/etc/lsfbeat.service
2) Install lsfbeat for the
linux3.10-glibc2.17-ppc64le OS Type:
- Find a LSF host where OS Type is
linux3.10-glibc2.17-ppc64le, and log in to the host as root.
- Source the LSF environment:
* For csh or tcsh:
source LSF_TOP/conf/cshrc.lsf
* For sh, ksh, or bash:
. LSF_TOP/conf/profile.lsf
- Download and extract the fix patch package:
explorer10.2_node_linux-ppc64le.tar.gz
- Navigate to the extracted directory:
cd explorer10.2_node_linux-ppc64le/install - Export the following environment variables based on
your LSF Explorer installation:
ES_HOST, ES_PORT, LOGSTASH_HOST, IPMI_HOME,
- Install lsfbeat:
For example:
rpm -Uvh --prefix /opt/ibm lsf-beat-10.2.0.0-17121914.ppc64le.rpm
- Restart the LSF lim to apply the changes and start the
lsfbeat daemon.
lsadmin limrestart -f all
- Restart the LSF Explorer Data Collector services.
perfadmin start all
- Check that the data loaders are running.
plcclient.sh -s
- Verfiy that the Energy data is collected and that the LSF
"bhosts -l" and "bjobs -l" commands can get
the energy data.
For example:
Verify that the bhosts -l output has the following energy information:
ENERGY:
Current Power: 120.00 Watt Energy Consumed: 1624225.00 Joule/ 0.4512 kWh
Verify that the bjobs -l output for exclusive jobs has the
following energy information:
ENERGY USAGE:
800.00 Joule/ 0.0002 kWh
- Uninstallation
- In this document,
assume the IBM Spectrum LSF Explorer Server and Data Collector are
installed on the same host and same directory under /opt/ibm
- 7.1 Before uninstallation
Stop all IBM Spectrum LSF
Explorer Server and Data Collector services:
perfadmin
stop all
pmcadmin stop
- 7.2 Roll back the LSF Explorer Data Collector fix patch
- Log in to the IBM Spectrum LSF Explorer Data Collector
host on which you
intall this fix patch by the same user used to install V10.2.0.
- Navigate to the extracted LSF Explorer Data Collector fix
patch installation package directory,
and back up the RPM installation files.
cd explorer10.2_node_linux-x64/install
mv lsf-perf-10.2.0.0-17121914.x86_64.rpm lsf-perf-10.2.0.0-17121914.x86_64.rpm.new
mv ibm-jre-1.8.0-17121914.x86_64.rpm ibm-jre-1.8.0-17121914.x86_64.rpm.new
- Download and extract LSF Explorer Data Collector V10.2.0,
then navigate to the extracted
directory (explorer10.2_node_linux-x64/install) and copy the
lsf-perf-10.2.0.0-17110904.x86_64.rpm
and ibm-jre-1.8.0-17110904.x86_64.rpm files to this extracted fix patch
directory
explorer10.2_node_linux-x64/install.
- Navigate to the extracted LSF Explorer Data Collector
package fix
patch directory.
Run the ExplorerNodeInstaller.sh installation script and finish the
rollback:
For example:
./ExplorerNodeInstaller.sh
-d -f install.config
- Uninstall logstash and lsfbeat.
rpm -e lsf-beat-10.2.0.0-17121914.x86_64.rpm
rpm -e logstash-for-lsf-5.4.1-17121914.noarch.rpm
- Repeat step 5 on all the hosts on which you
installed
this LSF Explorer Data Collector fix patch.
- Check that the rollback completed successfully.
rpm -qa|grep lsf
rpm -qa|grep ibm-jre
- Restart LSF lim.
lsadmin limrestart -f all
- Restart the IBM Spectrum LSF Explorer Data Collector
services.
perfadmin start
all
- Check that the IBM Spectrum LSF Explorer Data Collector
services have started.
perfadmin list
- 7.3 Roll back the LSF Explorer Server fix patch
-
Important:
This fix patch does not support LSF Explorer Server rollback.
If you want to rollback this
fix patch, you must uninstall the existing LSF Explorer Server, then download
and reinstall the LSF
Explorer Server V10.2.0 package. For more details, refer to the LSF
Explorer V10.2
Getting Started document (explorer10.2_getting_started.pdf).
When you uninstall the existing LSF Explorer Server, do not uninstall
IBM-JRE and Elasticsearch and its data;
When you reinstall LSF Explorer Server V10.2.0, configure
install.config to use the existing Elasticsearch
for new installations.
After reinstalling LSF Explorer Server V10.2.0, copy the contents of
the config directory /opt/ibm.bak/lsfsuite/ext/explorer/server/config
from the backup directory to replace the config directory under the new
installation.
- List of files
N/A
- Copyright and trademark information
©Copyright IBM Corporation 2017
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