Currently there is no automated way to install the IEPM-BW monitoring kit on a host. Here are the steps which shouldbe followed, in order, to install the monitoring host software.This assumes that the requirements for hardware and software configuration have been met. Note that if the default account 'iepm' with home directory '/home/iepm' is used, the source directory '/home/iepm/v3src' is used for the source, '/home/iepm/mysql' is used for the data base, then much of the installation can be done by cutting and pasting from this documentation.
The following instructions must be performed as root
- Decide what accounts are going to be needed. Assume the account 'cal' will have root privileges and be used for operations requiring root. Assume that the monitoring will run under the non-root access account 'iepm'. Both, for purposes of this documentation are assumed to be in group '<account group>, 'slac'. For this example, I will assume that the home directory for the 'cal' account is '/home/cal', and the home directory for the 'iepm' account is '/home/iepm'. For the sake of consistency beteween monitoring systems, the account 'iepm' with '/home/iepm' is strongly recommended.
- The monitoring host has a name. This is referred to as '<fully qualified monitoring host name>'.
- The monitoring host should be given an <aliasname> that starts with 'iepm-bw'. The idea is to hide the real name of the node, but provide it with a name that can recognize its place in the world. This is important. Examples include:
- iepm-bw.twaren.net
- iepm-bw.caltech.ul-org
- iepm-bw.cern.ch
- iepm-bw.bnl.org
- iepm-bw.snv.ul-org
- iepm-bw.fzk.de
- If the account mysql:mysql has not been allocated, allocate it by:
groupadd -g 20000 mysql useradd -u 20000 -g mysql mysql
- Decide on the directory structure for the mysql data base and the monitoring code. It is best to have the mysql data base on a separate physical disk from the system disk, but if this is not possible, use '/home/iepm/mysql' as the base. Make the mysql directory.
mkdir /home/iepm/mysql chown mysql:mysql /home/iepm/mysql
- Create a configuration file for /etc/my.cnf which MySQL will use when you install the database.
[mysqld] datadir=/home/iepm/mysql socket=/home/iepm/mysql/mysql.sock port=3306 [mysqld_safe] datadir=/home/iepm/mysql socket=/home/iepm/mysql/mysql.sock port=3306 [mysql.server] datadir=/home/iepm/mysql socket=/home/iepm/mysql/mysql.sock port=3306 [client] socket=/home/iepm/mysql/mysql.sock port=3306
- If mysql is already running, it is running with the 'test' database. Kill the mysql daemons.
- Restart MySQL with 'mysqld_safe&'. This will restart the MySQL server with the configuration file /etc/my.cnf.
- Create the data base by executing 'mysql_install_db'.
- Change the ownership of '/home/iepm/mysql' by the command chown 'chown -R mysql:mysql /home/iepm/mysql'.
- Set the database root password with 'mysqladmin -u root password "new password" '.
- You are now ready to create the directories with '/home/iepm/mysql' that must be owned by the iepm account. These directories are used by the iepm monitoring to track the state of the monitoring system. Execute the following commands with 'iepm:slac' replaced with 'slac' replaced by the appropirate group for the 'iepm' account.
# the data directory is where the results from the probes are stored. # These files are picked up by the 'load-datad' daemon and put into the database. mkdir /home/iepm/mysql/data chown iepm:slac /home/iepm/mysql/data # the logs directory contain the log files from each process mkdir /home/iepm/mysql/logs chown iepm:slac /home/iepm/mysql/logs # the pids from the daemons are stored here mkdir /home/iepm/mysql/pids chown iepm:slac /home/iepm/mysql/pids # the files in the keepalives directory are used by the monitoring software to ascertain that # the daemons are running mkdir /home/iepm/mysql/keepalives # prime the pump with: touch /home/iepm/mysql/keepalives/traced.alive touch /home/iepm/mysql/keepalives/pingd.alive touch /home/iepm/mysql/keepalives/bw-synched.alive touch /home/iepm/mysql/keepalives/pathchirpd.alive touch /home/iepm/mysql/keepalives/load-datad.alive touch /home/iepm/mysql/keepalives/load-scheduled.alive touch /home/iepm/mysql/keepalives/owpingd.alive # set the permissions so that the iepm account can access them chown \-R iepm:slac /home/iepm/mysql/data chown \-R iepm:slac /home/iepm/mysql/logs chown \-R iepm:slac /home/iepm/mysql/keepalives chown \-R iepm:slac /home/iepm/mysql/pids
- The output from the analysis and reports must go into a directory which is writeable by the 'iepm' account. Generally this is '/home/iepm/public_html'. Make this directory with:
mkdir /home/iepm/public_html mkdir /home/iepm/public_html/<aliasname> chown -R iepm:<account> /home/iepm/public_html
- Create a link to this area from /var/www/html
ln -s /home/iepm/public_html/<aliasname> /var/www/html/<aliasname>
- IEPM-BW requires a simple configuration file, '/etc/iepm.cnf'. The contents of /etc/iepm.cnf should contain:
# required iepm configuration parameters # /etc/iepm.conf dataBase = "iepm" dataBaseHost = "<fully qualified monitoring host name>" dataBaseDir = "/home/iepm/mysql" iepmSrcDir = "/home/iepm/v3src" updateAcct = "iepm" acctGroup = "<account group>" readAcct = "readonly" monHost = "<fully qualified monitoring host name>"; aliasName = "<aliasname>"; monHostip = "<monitoring host ip address>"; mysqlport = 3306; #Connie Logg 5/12/04 cal@slac.stanford.edu <- configurator's name and date please
The following installation instructions do not need root privileges can be performed under thei iepm account.
Currently loading of the monitoring host is done from iepm-bw.slac.stanford.edu.
- Enter the node into the 'NODES' data base.
- Enter the node into the 'MONHOST' data base.
- On iepm-bw.slac.stanford.edu, make a tar file including all the code.
cd /afs/slac/package/netmon/bandwidth-tests tar -cvf v3src dist.tar gzip dist.tar scp dist.tar iepm@<fully qualified monitoring host name>:/home/iepm/dist.tar.gz