This is the page for the IPP Operational Configuration Management.

How it works: The Software Documentation

The repositories location is on /data/ippc18.0/home/operational_repository (on ippc18). rsync of this directory is performed every day (the rsync completion/failure status is shown in the daily report).

The current operational configuration repository is in the current project. TODO: One day we will need tags

Any member of the users group (on the Maui cluster) can export/checkout the current operational configuration:

svn export file:///data/ippc18.0/home/operational_repository/current

(see the appropriate crontab)

Every day, at 06:30 HST, on ippc18, the ipp user runs the ~ipp/local/bin/configuration_monitoring.sh script. This script checks various files which are used by the IPP in production.

How to fix failures

PanTasks Servers Configuration Files

The <pantasks_server>s which are managed in configuration are:

addstar
cleanup
detrend
distribution
pstamp
publishing
registration
replication
stack
stdscience
summitcopy
update

Each <pantasks_server> has its own directory under pantasks. Two files are managed in each directory:

input
ptolemy.rc

If you are responsible for a change in an input or ptolemy.rc file for some <pantasks_server> (if you are not the best is likely to ask ps-ipp-ops mailing-list). First go into the <pantasks_server> directory:

cd ~ipp/<pantasks_server>

Update and then inspect its contents (according to SVN):

svn update .
svn status . -q

The input or the ptolemy.rc (or both) should be displayed with a 'M'.

Modified input file

svn diff input

If you are satisfied with the changes, as YOURSELF:

svn commit -m "`An informative message`" input

Modified ptolemy.rc file

svn diff ptolemy.rc

If you are satisfied with the changes, as YOURSELF:

svn commit -m "`An informative message`" ptolemy.rc

ippconfig Directory Files

Four files are managed in configuration in the operational ippconfig directory:

ippmonitor.config
ipprc.config
nebulous.config
site.config

If you are responsible for a change in the operational ippconfig directory (if you are not, the best is likely to ask ps-ipp-ops mailing-list). First go into the operational ippconfig directory:

cd ~ipp/ippconfig

Update and then inspect its contents (according to SVN):

svn update .
svn status . -q

One of the files should be shown with an 'M'.

Modified ippmonitor.config file

svn diff ippmonitor.config

If you are satisfied with the changes, as YOURSELF:

svn commit -m "`An informative message`" ippmonitor.config

Modified ipprc.config file

svn diff ipprc.config

If you are satisfied with the changes, as YOURSELF:

svn commit -m "`An informative message`" ipprc.config

Modified nebulous.config file

svn diff nebulous.config

If you are satisfied with the changes, as YOURSELF:

svn commit -m "`An informative message`" nebulous.config

Modified site.config file

svn diff site.config

If you are satisfied with the changes, as YOURSELF:

svn commit -m "`An informative message`" site.config

Databases Configuration Files

The databases configuration files which are checked are the MySql configuration files on the following hosts:

ippdb00: The master for Nebulous
ippdb01: The master for gpc1, isp, ippadmin,czardb
ippdb02: The replication slave of ippdb00 (for Nebulous)
ippdb03: The replication slave of ippdb01 (for gpc1, isp, ippadmin)
ippc17: The master for ippRequestServer
ippc19: The replication slave of ippc19 (for ippRequestServer)

Each expected my.cnf file (located in the current/<host>) is diff'd against the actual version /etc/mysql/my.cnf on the <host> (The file on the <host> is locally copied using scp and the local copy is diff'd).

If you are responsible for a check failure (that is, if you modified the /etc/mysql/my.cnf file on some <host>), you have to log as YOURSELF on the Maui cluster and do:

mkdir ~/tmp/ipp_ocm                                                       # Create a working directory
cd ~/tmp/ipp_ocm                                                          # Go into that working directory
svn checkout file:///data/ippc18.0/home/operational_repository/current    # Get the current repository contents
cd current/databases/<host>                                               # Change to the "right" host directory
scp <host>:/etc/mysql/my.cnf .                                            # Copy the MySql configuration file to your local working copy
svn commit -m "`Some informal message`" .                                 # Commit the changes

Databases Backup Files

Nebulous Apache Configuration Files

Other Files

RSync Failures

Requests

Software Improvements/Bugs

Files / Directories to be added to the OCM

Please be precise and exhaustive (name of the file, location)

Software Changes

beta version

• rsync to a directory on the manoa cluster; something under /data/ipp001.0/ipp: DONE (but not on the Manoa cluster since there are operational passwords in the repository)
• E-mail title according to global status: DONE
• mysql configuration files: ippdb00, ippdb01, ippdb02, ippdb03, ipp001, ippc17, ippc19: DONE
• apache/nebulous configuration files: ippc01-ippc09, ippc10: DONE