Installing LSF Web Services

As an administrator, after you have installed or upgraded to the LSF Fix Pack 15 level, you can install LSF Web Services installation package for easy access to your LSF from anywhere. LSF Web Services is supported on RHEL 8 or later.

1. Log on to an existing LSF management or server host as root​.
2. Extract the downloaded package; one of:
   • lws10.1.0.15_linux-aarch64.tar.Z
   • lws10.1.0.15_linux-ppc64le.tar.Z
   • lws10.1.0.15_linux-x86_64.tar.Z

   For example:

   [root@lsfhost ~]# tar xvf lws10.1.0.15_linux-x86_64.tar.Z​

3. Change to the directory where you extracted the files and edit lwsinstall.sh file to source LSF cluster environment:
   1. Locate the # . $LSF_ENVDIR/profile.lsf line.
   2. Add the a line after this one to source the LSF cluster environment.
      For example:

      # cd lws10.1.0.15_linux-x86_64​
      # vi lwsinstall.sh​
       …​
      #. $LSF_ENVDIR/profile.lsf​
      . /opt/lsf/conf/profile.lsf

   3. Save your changes.
4. Install the LSF Web Services package:
   1. Run the installer:

      # ./lwsinstall.sh

   2. Enter 1 to accept the LSF license agreement.
   3. Support for HTTPS is enabled by default so that server side, self signed certificates are installed automatically. Enter N to keep it enabled, or Y to disable it.
   By default, the installer:

   • Installs the ibm-jre and lsf-webservice RPM files into the /opt/ibm/ directory.
   • Installs a single client-side LSF CLI library called lsf so you can run LSF commands wherever the client is installed.
   • Enables LSF Web Services for HTTPS so that server side, so that self signed certificates are installed automatically.
     Note: The certificate that LSF Web Services issues is specific for your host; therefore, if you change your hostname, you must also re-enable HTTPS for that host.

     If you entered Y to disable HTTPS during installation, then the installer enables HTTP. You can enable HTTPS later on for LSF Web Services and the lsf client CLI library.

5. Source LSF Web Services profile:
   For example:

   # . /opt/ibm/lsfsuite/ext/profile.platform​

6. Start LSF Web Services​:
   For example:

   # systemctl restart lwsd​

7. Check LSF Web Services status​:
   For example:

   # systemctl status lwsd​
   
   SERVICE        STATUS         PID            PORT           HOST_NAME​
   WEBSERVICE     STARTED        3976321        8088           lwshost
   
   # netstat -na|grep 8088​
   tcp6       0      0 :::8088                 :::*                    LISTEN​

8. Test LSF Web Services with the client-side CLI:
   1. Log into any host as a normal user, switch to your LSF Web Services installation directory and list the lsf client binary:

      $ cd /opt/ibm
      $ ls -l
      -rwxr-xr-x  1 user1   user1    29876840 Apr 24 14:21 lsf
      $ ./lsf version
      version:  v0.0.1
      commit:   0.0.1 Preview

   2. Authenticate the lsf client binary to LSF Web Services by logging on to the LSF Web Services host with your existing OS username and password. For example:

      $ ./lsf cluster logon --username user1 --url http://lwshost:8448
      Password> *********
      OK

      In the example, user1 is an existing user on the LSF Web Services host. This user can be a local user on the host, or an LDAP user.

   3. Run any LSF CLI commands (as you would run with LSF normally) using the lsf client-side CLI. Preface LSF commands with lsf.
      For example, run the lsfid, bsub, and bjobs) commands:

      $ ./lsf lsid
      IBM Spectrum LSF Standard 10.1.0.15, June 25 2024
      Copyright International Business Machines Corp. 1992, 2016.
      US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
      
      My cluster name is lwshost
      My master name is lsfmgrA
      
      $ ./lsf bsub sleep 100
      Job <20770> is submitted to default queue <normal>.
      
      $ ./lsf bjobs 20770
      JOBID   USER   STAT  QUEUE      FROM_HOST   EXEC_HOST   JOB_NAME   SUBMIT_TIME
      20770   user1  RUN   normal     lwshost     lsfexec     sleep 100  Apr  9 15:56