Installation Steps

This section explains the steps needed to install and configure ScaleOut StateServer during a typical installation. You should install ScaleOut StateServer on every server that potentially could join the distributed store, including systems that may be used as spares in case a server fails. A server that runs ScaleOut StateServer is called a host. The installation procedure is as follows:

  1. To install ScaleOut StateServer, download the appropriate rpm file for Red Hat Linux or DEB file for Debian Linux from ScaleOut Software’s Web site (www.scaleoutsoftware.com). For example, for 64-bit Red Hat Linux 5, download soss-5.0.19-219.el5.x86_64.rpm (or a later version).

  2. Make sure that you have root privileges. Install ScaleOut StateServer using using your distribution’s package installer, for example: 

    Red Hat Linux:
    rpm -i  soss-5.0.19-219.el5.x86_64.rpm

Debian Linux:
    dpkg -i soss soss_5.0.19.219_amd64.deb
    [Note] Note

    The installer automatically installs and starts the StateServer service. The service is configured to automatically start when the system boots. On Red Hat Linux, you can change this behavior using the Red Hat Services Configuration Tool or with the chkconfig command-line tool. On Debian Linux, you can change this behavior using the Debian Runlevel Configuration Tool (rcconf) or the update-rc.d command-line tool.

  3. Edit the Configuration Parameters in the soss_params.txt file, which was created with default parameters in /usr/local/etc/. In most cases, you initially only have to enter your license key and select the network interface that you want the StateServer service to use when communicating with other hosts.

    [Note] Note

    You can edit these parameters using the Web management console, by using the command-line control program (soss), or by editing the parameters file with a text editor. You should use the management tools whenever possible because this enables changes to global parameters to automatically propagate to all other hosts in the store. If you make changes manually with a text editor, they will not be propagated and could be overwritten by other hosts; you also need to restart the StateServer service for manual changes to take effect.

  4. If desired, install and run the Web Management Console to check the configuration of all parameters. The console connects to the local StateServer service, which has already been started by the installer. You should review the local host’s configuration settings and select the correct network interface for the service’s communications with other hosts. (If you have only one network interface, the service automatically selects the first available network interface and sets the net_interface parameter.)

    [Note] Note

    Be sure to configure the server’s firewall to ensure that the configured management and server ports are not blocked.
  5. Activate the StateServer service, i.e., have it join the distributed store, using the management console or from the command line using the soss command (see Command-line Control Programs). If this is the first server to be activated, a new store will be created. Otherwise, the service will automatically discover the store and join it to take on a portion of the storage workload.

  6. Repeat this installation process on additional servers in the farm. You should install ScaleOut StateServer on all hosts that make access requests to the store, since access requests are always directed to a host’s local service.

    [Note] Note

    Be sure that all hosts use the same multicast IP address (mcast_ip parameter) and port (mgt_port parameter). Otherwise, the hosts will not discover each other.