Theodolite Support Installation

This document is divided into three sections:

Something you should know about theodolites

Theodolites are the basic monitoring fuctionality. Theodolites should run on hosts located as near as possible to the router at the border of your domain: in the simplest case, you will have one monitoring host running a single theodolite. The border of the domain should be defined so that the connectivity within the domain is, as a general rule, better than between domains.

In case you have more than one router to different WANs you might specify several theodolites, but you should also tell us other routing infos. For the now, one theodolite should be sufficient, and its location should be found by compromise.

Hosts running theodolites need not to be specially equipped: instead, they may have quite modest capabilities. The following might be considered as typical:
# cat /proc/cpuinfo
processor: 1
vendor_id: GenuineIntel
cpu family: 6
model: 8
model name: Pentium III (Coppermine)
stepping: 3
cpu MHz: 797.380
cache size: 256 KB

Network interfaces should be adequate to the infrastructure inside the domain. Hard disk capacity is not an issue: 10 GB is Ok.

The computational load of a theodolite is minimal, but its activity relies on a fast response. Therefore it is inappropriate to install the theodolite on a host with a high computational load.



Entering the GlueDomains monitoring network

You will receive a "welcome aboard" reply to your mail containing the IP addresses of the hosts that run your theodolites. The reply contains a tar attachment gridice-theodolite-custom-<date>.tar where <date> is used for versioning. Save that file and proceed selecting between:

You can later inspect your installation using the log of the daemon that controls the theodolite(s) (/opt/GlueDomains/var/log/*.thd) or those that log the activity of the monitoring sessions (same directory).

Installation on Scientific Linux

The following step by step howto applies to Scientific Linux SLC303 installed from scratch with boot CD + NFS/HTTP. You can probably skip the first two steps if your host already runs Scientific Linux, or you can adapt the OS install part with your preferred OS install system.

Software installation

The following steps are needed to install the required software (or use this untested quattor template):

  1. configure your installation type as SERVER

  2. install the following groups of packets:
  3. add to your installation the following additional RPMs (indented ones are the dependencies to be satisfied in our setup):
    iperf-1.7.0-cern1
      compat-gcc-c++-7.3-2.96.123
      compat-gcc-7.3-2.96.123
      compat-libstdc++-7.3-2.96.123
      compat-libstdc++-devel-7.3-2.96.123
    
    perl-DBI-1.32-5
    
    perl-DBD-MySQL-2.1021-3
      mysql-3.23.58-2.3
    
  4. Install theodolite support software:
    # cd /usr/include; h2ph -r -l .
    # cd /tmp
    # wget ftp://ftp.di.unipi.it/pub/Papers/ciuffoletti/gluedomains/install.sh
    # chmod u+x install.sh
    # ./install.sh mdstheodolite
    

Software configuration

Unpack the configuration tarball you received with the welcome mail:

# tar -xv -C / -f gridice-theodolite-custom-<DATE>.tar 

Running GlueDomains

When installation is complete, start GlueDomains with:

# service gluedomains start
and activate it at system startup with:
# chkconfig gluedomains on

Installation without LCFG

Installation is at present fully supported for Linux RedHat7.3. RedHat and external rpms that are needed to satisfy GlueDomains dependencies are available here. To get support for Linux Debian contact Augusto Ciuffoletti.

The following steps, tested for a Linux RedHat 7.3 should bring your theodolites up and running on the target host:

  1. If you start from a RedHat 7.3 installation, you probably want to install also these packages that should cover dependencies.
  2. Follow the instruction sections INSTALLATION for theodolite in the document README.html. In a nutshell:

    # cd /usr/include; h2ph -r -l .
    # cd /tmp
    # wget ftp://ftp.di.unipi.it/pub/Papers/ciuffoletti/gluedomains/install.sh
    # chmod u+x install.sh
    # ./install.sh mdstheodolite
    
  3. Unpack the configuration tarball you received with the welcome mail:

    # tar -xvf gridice-theodolite-custom-<DATE>.tar -C /
  4. When installation is complete, start GlueDomains with:

    # service gluedomains start
    and activate it at system startup with:
    # chkconfig gluedomains on

Installation with LCFG

This part is still incomplete: you should start with a RedHat 7.3 installed with a PlainGRIS-cfg.h profile, and next follow the instructions for installation without LCFG. TODO

Upgrading GlueDomains

If you are running Red Hat 7.3, you should consider this upgrade as an opportunity to switch to Scientific Linux, and to reinstall GlueDomains from scratch.

Prior to upgrading your software, stop GlueDomains with:

# service gluedomains stop
# killall -9 mdsproxy.pl

next:

# cd /tmp
# wget ftp://ftp.di.unipi.it/pub/Papers/ciuffoletti/gluedomains/install.sh
# chmod u+x install.sh
# ./install.sh mdstheodolite
You may also want to check whether an upgrade is required for the configuration tarball: you should be notified about this, and the mail should contain the new tarball. In case, save the attachment and run:
# tar -xv  -C / -f gridice-theodolite-custom-DATE.tar
using the appropriate DATE. Finally restart:
# service gluedomains start

Maintenance and troubleshooting

The following are respectively generic hostname, ipnumbers and theodolite identifiers: myhost, 123.123.123.123, a. Uninterestin lines are replaced with "...".