This is the page for the IPP Operational Configuration Management. [[PageOutline]] = 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 {{{}}}s which are managed in configuration are: {{{ addstar cleanup detrend distribution pstamp publishing registration replication stack stdscience summitcopy update }}} Each {{{}}} 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 (if you are not the best is likely to ask ps-ipp-ops mailing-list). First go into the directory: {{{ cd ~ipp/ }}} 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 == == 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