Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

/etc/chronopolis
/etc/chronopolis/repair.yml
/etc/init.d/chron-repair
/usr/lib/chronopolis
/usr/lib/chronopolis/chron-repair.jar
/var/log/chronopolichronopolis

Configuration

The configuration for the repair service is done in the repair.yml under /etc/chronopolis

Code Block
titlerepair.yml
linenumberstrue
collapsetrue
# Application Configuration for the Chronopolis Repair

# cron timers for
## cron.repair: how often to check the Ingest scheduledServer jobs; see http://www.quartz-scheduler.org/documentation/quartz-2.x/tutorials/crontrigger.html for documentationrepair endpoint
## cron.fulfilment: how often to check the Ingest Server fulfillments endpoint
cron:
  repair: 0 0/1 * * * *
  fulfillment: 0 0 * * * *

# storagegeneral locations for the repairproperties
## repair.stage: staging area to knowreplicate wherefiles to stagebefore datathey (for pulling without overwriting),
# as well as where to write data in when it has been validatedare moved to preservation storage
## repair.preservation: preservation storage area
repair:
  stage: /dataexport/chronopolisrepair/backupstaging
  preservation: /datapreservation/chronopolis/perservationbags

# Chronopolis Ingest API configuration
## ingest.endpoint: the url of the ingest server configuration for communication
## ingest.ucsername: the username to authenticate as
## ingest.password: the password to authenticate with
ingest:
  endpoint: http://localhost:8000
  username: my-usernode
  password: my-passnodepass

# rsync fulfillment configuration
# for fulfillments
## rsync.path: theused pathif tochrooting substituteusers inrsyncing when- creatingthe thepath rsyncunder 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 repairthe chroot context
## rsync.stage: a staging area which fulfillments will be copied to
## rsync.server: the fqdn of the server nodes will replicate from 
rsync:
  path: bags/export/repair/outgoing
  stage: /export/repair/outgoing/bags
  server: test-serverloach.umiacs.umd.edu

# ACE aceAM configuration
### ace.am: the local ACE ace-am endpoint to connect to for communication with aceAM webapp
## ace.username: the username to authenticate as
## ace.password: the password to authenticate with 
ace:
  am: http://localhost:8080/ace-am/
  userusername: aceadmin
  password: aceadmin

# spring the activeproperties
## spring.profiles.active: the profiles to use
# develop|default : if running in development mode or production
# rsync : if fulfilling with rsync or ace
spring.profiles. when running
##                         recommended: default, rsync
spring:
  profiles:
    active: default, rsync

# logging properties
## logging.file: the location of the main repair log file to write logging statements to
## logging.level: the log level to filter on
logging.file: /var/log/chronopolis/repair.log
logging.level.org.chronopolis: INFO

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

Release Notes

Release 1.5.0

...