2 - Installation:

2.1 - Preliminary Notes:

• Currently, only installation in ROCKS-based clusters is documented. However, installation in other cluster environments shouldn't be difficult, provided the auxiliary libraries and applications are available, and the correct paths are set in the configuration files.
• The installation, configuration and utilization procedures assume that: 1) the "domus" user will be the unique cluster user (albeit virtual) that will deploy Domus monitorization services; 2) the "domus" user will never deploy Domus clusters (other users will eventually do so).

Although not strictly mandatory, the previous separation of roles ensures the existence of a unique set of Domus monitorization services feeding Ganglia, thus sparing cluster resources. The separation depends, however, on the goodwill/availability of the cluster administrator to perform the role of the "domus" user (another possibility is to have the Domus monitorization services running continuously, starting at boot-time, side-by-side with Ganglia). Thus, it may be necessary, sometimes, for a normal user to install, configure, deploy and manage the complete Domus infrastructure; in such case, the user must follow all the supplied instructions.

• The various commands and tools share the same philosophy with regard to the definition of important operation parameters: 1) local variables used as parameters start by assuming default values defined in a Domus system-level library (domus_libsys.py); 2) if a configuration file is explicitly supplied as a command line argument, the definitions therein will overwrite the defaults; 3) if specific parameters are explicitly valued via command line arguments, the supplied values will overwrite any previous ones.

2.2 - Installation Instructions:

The following are installation instructions for ROCKS 4.3. Specific procedures for versions 4.0.0 and 4.2.1 are given where necessary. In general, the installation method tries to avoid, as much as possible, the need for 3rd party applications and administrative privileges to install and run Domus.
1. Make sure that the following packages are pre-installed in the frontend:
   • BerkeleyDB development files:
     usually pre-installed in any ROCKS version ( check it with rpm -qa | grep db4-devel )
   • SWIG:
     usually pre-installed in ROCKS 4.3 and absent in ROCKS 4.2.1 and 4.0.0; if absent in ROCKS 4.3 or ROCKS 4.2.1 then root may install it with yum install swig; if absent in ROCKS 4.0.0 then root may search for local files that match "swig*.rpm" ( find / -name "swig*.rpm" -print ) and install it ( rpm -ivh swig*.rpm ); the later method also works in ROCKS 4.3 and 4.2.1;

2. Ask "root" to create a "domus" account in the cluster frontend:

   	
   [root@frontend]# useradd domus
   [root@frontend]# rocks sync users
   

   ROCKS 4.0.0: no need to execute rocks sync users.
   The "domus" account will hold the Domus executables and general configuration files. All cluster users will have access to ~domus (by NFS), thus avoiding the need to update every worker node. The "domus" account will also host, by default, the files needed / generated by the Domus monitorization services that cooperate with the pre-installed Ganglia services.

3. Ask "root" to add the following line to /etc/sudoers:

   	
   domus ALL=NOPASSWD: /opt/ganglia/bin/gmetric
   

   ROCKS 4.0.0: instead, add the line domus ALL=NOPASSWD: /usr/bin/gmetric
   This is needed in order for the Domus monitorization services to inject new metrics in Ganglia, at the frontend node. The lifetime of these metrics may be configured to be limited (see the parameter DOMUS_NODEINFO_LIFETIME in 3 - Monitorization Services), allowing for their automatic removal by Ganglia after the Domus monitorization services finish.

4. As "domus":

   4.1

   Untar the Domus package:

   	
   [domus@frontend]# cd ~domus
   [domus@frontend]# tar zxvf domus-version-X.Y.tgz
   

   4.2

   Edit ~domus/domus-version-X.Y/src/domus_make.sh and, if necessary, modify the paths defined therein. The default paths are adequate for ROCKS 4.3 (32bits), provided that BerkeleyDB and SWIG where installed in the default locations using rpm or yum. Alternate path definitions belong to specific configurations, as defined by the parameter -c conf_dir_name of the script domus_install.py (see next).

   4.3

   Install the Domus package using the domus_install.py script.

   Usage:

   	
   [domus@frontend]# cd ~domus/domus-version-X.Y
   [domus@frontend]# ./domus_install.py -h
   Usage: ./domus_install.py 
   -h | { [-c conf_dir_name] [--rocks_400 | --rocks_421] [-H home_dir_path] [-d] [--debug]
          [--64bits] [--libusr_threadsafe] [--libsys_threadsafe] [--service_threadsafe] }
   

   Parameters:

   • -h : print usage information;
   • -c conf_dir_name : a directory where resides a set of configuration files to install (such files regulate the behaviour of Domus services); the set may be generic or tailored to some specific physical cluster; available sets may be found under ~domus/domus-version-X.Y/etc; by default, the alfa set (tailored for a ROCKS 4.3 cluster) is installed;
   • --rocks_400 | --rocks_421 : target is a ROCKS 4.0.0 or 4.2.1 cluster environment, depending on the supplied option; default behavior: target is a ROCKS 4.3 cluster environment;
   • -H home_dir_path : where to install Domus; default value: ~domus/.domus;
   • -d : activate debug code during the installation process;
   • --debug : activate debug code on the installed files; default behavior: debug code absent;
   • --64bits : activate 64bit awareness code on the installed files (mandatory for 64bit clusters); default behavior: 64 bit code absent;
   • --libusr_threadsafe:
     --libsys_threadsafe:
     --service_threadsafe: activate threadsafe code on the installed files; --libusr_threadsafe is not necessary if one does not intend to have multithreaded Domus client applications; --service_threadsafe is not necessary if one does not intend to have multithreaded Domus services; --libsys_threadsafe may be absent only if neither kind of multithreaded support is wanted;

   4.4

   Assuming ~domus/.domus was the target folder during Domus installation, edit ~domus/.bash_profile and add the following lines:

   	
   LD_LIBRARY_PATH=$LD_LIBRARY_PATH:~domus/.domus/lib:~domus/.domus/bin:.
   LD_RUN_PATH=$LD_RUN_PATH:~domus/.domus/lib:~domus/.domus/bin:.
   PYTHONPATH=$PYTHONPATH:~domus/.domus/lib:~domus/.domus/bin:.
   PATH=$PATH:$HOME/bin:~domus/.domus/bin:.
   
   export PATH LD_LIBRARY_PATH LD_RUN_PATH PYTHONPATH