4. Unpackaged Installation
Prev Chapter 6. Manual Installation Next

4. Unpackaged Installation

Not all target operating systems are supported with native software packages. In this case, a non-package based installation via a tar-archive is supported. This type of installation will build all software for both, node and frontend, and install it to a path that you specify. From there, you have to perform the actual driver and service installation using scripts provided with the installation.

This type of installation installs the complete software into a directory on the local machine. Depending on whether this machine will be a node or the frontend, you have to install different drivers or services from there. To install using this method, please proceed as follows:

  1. Become superuser:

    $ su - 
#

  2. Create the tar archive from the SIA, and upack it:

    # sh DIS_install_<version>.sh --get-tarball
#* Logfile is /tmp/DIS_install.log_260 on node1

#*
#+ Dolphin ICS - Software installation (version: 1.31 $ of: 2007/09/27 15:05:05 $)
#+

#* Generating tarball distribution of the source code

#* NOTE: source tarball is /tmp/DIS.tar.gz

# tar xzf DIS.tar.gz

  3. Enter the created directory and configure the build system, specifying the target path <install_path> for the installation. We recommend that you use the standard path /opt/DIS, but you can use any other path. The installation procedure will create subdirectories (like bin, sbin, lib, lib64, doc, man, etc) relative to this path and install into them.

    # cd DIS
# ./configure --prefix=/opt/DIS

  4. Build the software stack using make. Check the output when the command returns to see if it the build operation was successful.

    # make
...
# make supersockets
...

  5. If the build operations were successful, install the software:

    # make install
...
# make supersockets-install
...

    Tip

    You can speed up the installation on multiple nodes if you copy over the installation directory to the other nodes, provided they features the same Linux kernel version and CPU architecture. The best way is to create a tar archive:

    # cd /opt
# tar czf DIS_binary.tar.gz DIS

    Transfer this file to /opt on all nodes and unpack it there:

    # cd /opt
# tar xzf DIS_binary.tar.gz

  6. Install the drivers and services depending on whether the local machine should be a node or the frontend. It is recommended to first install all nodes, then the frontend, than configure and test the cluster from the frontend.

    For a node, install the necessary drivers and services as follows:

    1. Change to the sbin directory in your installation path:

      # cd /opt/DIS/sbin

    2. Invoke the scripts for driver installation using the option -i. The option --start will start the service after a successful installation:

      # ./irm_setup -i --start
# ./nodemgr_setup -i --start
# ./sisci_setup -i --start
# ./ssocks_setup -i

      Note

      Please make sure that SuperSockets are not started yet (do not provide option --start to the setup script).

      You can remove the driver from the system by calling the script with the option -e. Help is available via -h.

    Repeat this procedure for each node.

    For the frontend, install the necessary services and perform the cluster configuration and test as follows:

    1. Change to the sbin directory in your installation path:

      # cd /opt/DIS/sbin

    2. Configure the cluster via the GUI tool dishostseditor:

      # ./dishostseditor

      For more information on using dishostseditor, please refer to Chapter 4, Initial Installation, Section 3.3, “Working with the dishostseditor”.

    3. Invoke the script for service installation using the option -i:

      # ./networkmgr_setup -i --start

      You can remove the service from the system by calling the script with the option -e.

    4. Test the cluster via the GUI tool sciadmin:

      # ./sciadmin

      For more information on using dxadmin to test your cluster installation, please refer to Appendix B, dxadmin Reference and Section 1, “Verifying Functionality and Performance”.

    5. Enable all services, including SuperSockets, on all nodes.

      # dis_services start
Starting Dolphin IRM 3.3.0 ( November 13th 2007 )          [  OK  ]
Starting Dolphin Node Manager                              [  OK  ]
Starting Dolphin SISCI 3.3.0 ( November 13th 2007 )        [  OK  ]
Starting Dolphin SuperSockets drivers                      [  OK  ]

      Note

      This command has to be executed on the nodes, not only on the frontend!

Prev Up Next
3. Manual RPM Installation Home Chapter 7. Interconnect Maintenance