What's new and changed in IBM Spectrum LSF Suite for Workgroups Version 10.2 Fix Pack 9

The following topics summarize the new and changed behavior in IBM Spectrum LSF Suite for Workgroups 10.2 Fix Pack 9.

New features in each component

See the What’s New page for each IBM Spectrum LSF component:

Installing Kibana for use with Elasticsearch

In 10.2 Fix Pack 9, Kibana 7.2.1 has been bundled with the installer (as part of the Explorer component).

Kibana is the graphical interface to Elasticsearch and provides more in-depth functionality for displaying, analyzing, and manipulating data in Elasticsearch. This allows IBM Spectrum LSF Suite for Workgroups users to do their own reporting with a richer toolset.

IBM Spectrum LSF Suite for Workgroups provides an optional installation of Kibana. Kibana must use the same Elasticsearch that IBM Spectrum LSF Suite for Workgroups uses. The installer will check if the Elasticsearch used by IBM Spectrum LSF Suite for Workgroups is the same as the version bundled with Kibana.

Kibana will be installed on the first GUI_host configured in the lsf-inventory file.

Installation of Kibana is enabled before installing IBM Spectrum LSF Suite for Workgroups by setting the Install_Kibana: True parameter in the lsf-config.yml file before installation.

Update Elasticsearch/Logstash/Filebeat/Metricbeat to version 7.2.1

In 10.2 Fix Pack 9, Elasticsearch/Logstash/Filebeat/Metricbeat have been updated to version 7.2.1 (as part of the Explorer component).

Fix pack query tool included in installer

Starting in 10.2 Fix Pack 9, a tool (queryFixPack.sh) is provided as part of the fix pack installer to query IBM Fix Central for the latest fix pack. The tool is run automatically during fix pack installation.

TensorFlow, Jupyter, and H20 submission template

In 10.2 Fix Pack 9, TensorFlow, Jupyter, and H2O submission form templates have been bundled with the installer (as part of the Application Center component).

Public/Private IP installations using parameter Private_IPv4_Range in lsf-config.yml

The new optional parameter Private_IPv4_Range in the lsf-config.yml file allows you to specify a range of private IPv4 addresses used by LSF and Elasticsearch hosts.

This parameter can be used in scenarios where the LSF managementhost has both public and private IP addresses, but the compute nodes have only private IP addresses. Also, it allows you to easily configure Elasticsearch to use private IP addresses to listen to other private IP addresses to which the beats on the LSF server hosts can connect/contact.

Specify a range of IPv4 addresses in the form of a Classless Inter-Domain Routing (CIDR) block. For example, Private_IPv4_Range: 10.10.99.0/8

The parameter is set before installation, along with other cluster properties, in lsf-config.yml.

By default, FQDN(fully qualified domain name)s are used by LSF and Elasticsearch hosts.

Assumptions when using this parameter:
  • Name resolution (host name to/from IP address) is fully functional.
  • Valid private IP addresses must be available on all hosts (LSF_Masters, LSF_Servers, LSF_Clients, and GUI_Hosts roles).
  • The LSF_hosts file has not been configured manually.