This is the page for the IPP Operational Configuration Management.

How it works: The Software Documentation

TODO

How to fix failures

PanTasks Servers Configuration Files

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 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

Databases Configuration Files

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