Changes between Version 16 and Version 17 of IPP_Operational_Configuration_Management

Timestamp:

Jul 20, 2011, 12:07:31 PM (15 years ago)

Author:

Serge CHASTEL

Comment:

--

IPP_Operational_Configuration_Management

@@ -4 +4 @@
 = How it works: The Software Documentation =
 
-TODO
+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 ==