The replication service talks to the ingest-server and will pull data when it is ready to the local preservation area. It then registers the token store and collection with ACE, completing ingestion of content into chronopolis.
Installation
Prereqs
- ACE - The replication shell will need to talk to ACE in order to register collections
- SSH + Rsync - Replication is done with rsync over ssh, so keys must me exchanged to any nodes planning on distributing content so that file transfers can occur.
- Preservation Area - The replication shell pulls from the ingest server directly to your preservation area on a posix file system. In the future we may expand this, for now it's local disk.
RPM
The replication shell is packaged in an rpm for ease of install
- Download the rpm from our build server
- Use yum to install the rpm: `yum install replication-shell-$version.rpm`
Installed files are as follows
User Creation
A 'chronopolis' user is also needed as part of the install process who can write to /var/log/chronopolis and into the preservation storage defined in the configuration. This is no longer handled by the rpm installation process but must be done manually.
Configuration and Running
The replication shell reads the configuration file in /usr/local/chronopolis/replication/applicayion.yml
Notes on Configuration
- The replication.cron timer sets how often the replication-shell queries the ingest-server for active replications. It uses a cron style formatting:
- See http://www.quartz-scheduler.org/documentation/quartz-1.x/tutorials/crontrigger for an overview of the formatting used
- 0 0 * * * *: The default timer, at the top of every hour
- 0 */1 * * * *: A faster timer, once per minute
- The development profile can be used for testing configuration options. It remains in the foreground and has a limited set of commands.
- Currently multiple ingest servers will not be queried, only the first one on the list.
- The mail configuration (smtp) is set to send by default.
- If you don't want to send mail, or have a server which does not have smtp capabilities you can turn it off by setting smtp.send: false
- If the storage is not set up correctly, the replicationd process will not run. This includes existence, and r/w/e permissions
- The pid file likely should not be changed. If you do update it make sure to update the init scripts which rely on it as well.
Running
If using EL6, use the init.d script `service replicationd start`
If using EL7, use systemd `systemd start replicationd`
Errors
This will be filled out as we experience problems. Check /var/log/chronopolis/replication.log to see if there are any stack traces.
Current Implementation
- Query Ingest RESTful API for available transfers
- Transfer data (bag + tokens) to local preservation area
- Register to ACE
- Load tokens for collection in ACE
- Issue audit for collection in ACE
- Update Ingest API with the status of the transfer