You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 7
Next »
Installation
Builds for the master and develop branches of the Repair Service can be found at http://adaptci01.umiacs.umd.edu/resource/medic
The rpm creates a chronopolis user if it does not exist, and creates the following files/directories.
[~] $ rpm -ql ingest-server
/etc/chronopolis
/etc/chronopolis/repair.yml
/etc/init.d/chron-repair
/usr/lib/chronopolis
/usr/lib/chronopolis/chron-repair.jar
/var/log/chronopolis
Configuration
The configuration for the repair service is done in the repair.yml under /etc/chronopolis
# cron timers for the scheduled jobs; see http://www.quartz-scheduler.org/documentation/quartz-2.x/tutorials/crontrigger.html for documentation
cron:
repair: 0 0 * * * *
fulfillment: 0 0 * * * *
# storage locations for the repair to know where to stage data (for pulling without overwriting),
# as well as where to write data in when it has been validated
repair:
stage: /data/chronopolis/backup
preservation: /data/chronopolis/perservation
# ingest server configuration for communication
ingest:
endpoint: http://localhost:8000
username: my-user
password: my-pass
# rsync fulfillment configuration
# path: the path to substitute in when creating the rsync link. e.x. ucsd@test-server.umiacs.umd.edu:bags/...
# stage: the storage area to stage bags to
# server: the server to rsync from. e.x. ucsd@test-server.umiacs.umd.edu:bags/...
# note that the username for the rsync is determined by whoever requested the repair
rsync:
path: bags/
stage: /export/outgoing/bags
server: test-server.umiacs.umd.edu
# ace configuration
# am: the local ace-am endpoint to connect to for communication with ace
ace:
am: http://localhost:8080/ace-am/
user: ace
password: ace
# the active profiles to use
# develop|default : if running in development mode or production
# rsync : if fulfilling with rsync or ace
spring.profiles.active: default, rsync
# the location of the main repair log
logging.file: /var/log/chronopolis/repair.log
Running
The Repair Service ships with a SysV style init script and has the basic start/stop/restart options. Customization of the script may be necessary if your java location needs to be specified.
- service chron-repair start|stop|restart