...
Depending on where the data is bound, there are several configuration options available
Chronopolis
Prefix
Specifying Replicating Nodes
DPN
Sample application.yml with all properties
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
# Cron timer for how often the bridge is polled bridge: poll: 0 0 0 * * * # Bagging Configuration ## bag.unit: The unit for the maximum size of a Bag ## bag.max-size: The maximum size a Bag is allowed to be ## bag.dpn.node-address: The 'DPN-Node-Address' information field for dpn-info.txt ## bag.dpn.node-contact: The 'DPN-Node-Contact' information field for dpn-info.txt ## bag.dpn.node-email: The 'DPN-Node-Email' information field for dpn-info.txt bag: max-size: 2 unit: GIGABYTE dpn: node-address: University of California, San Diego, 9500 Gilman Dr, La Jolla, CA 92093 node-contact: Sibyl Schaefer node-email: - sschaefer@ucsd.edu - chronopolis-support-l@mailman.ucsd.edu # General chron configuration chron: node: chron bagsworkDirectory: /export/bags tokenstmp/chronopolis stage.bags: posix.id: 4 posix.path: /export/tokensscratch0/bags ingest.api: preservationendpoint: /data/preservationhttp://localhost:8000/ restorationusername: /export/restoreadmin prefixpassword: bridge-admin ace.ims: ingestendpoint: localhost port: 8080 endpointwaitTime: http://localhost:8081/6000 constraints: nodes: username: ingest-admin - name: aptrust size-limit: unit: TERABYTE password size: replace-me10 replicatingTo: members: - member-uuid-0 - ucsd member-uuid-1 - umiacsmember-uuid-2 # DPN Configuration - the server to use when creating replications # and connection information for the registry dpnReplicationServer: dpn-staging.ucsd.edu dpn: endpoint: http://localhost:3000/ username: chron api-key: replace-me # Duracloud Bridge Configuration # The storage areas the bridge app writes in to # Connection information to query the bridge duracloud: bridge: - name: bridge-0 snapshots: /exportbridge-0/snapshots/ restores: /export/restore/ bridge: bridge-0/restore/ username: replace-me password: replace-me endpoint: http://localhost:8080/ - name: bridge-1 snapshots: /bridge-1/snapshots/ restores: /bridge-1/restore/ username: bridgereplace-me password: replace-me endpoint: http://localhost:80808081/ # Push settings to decide what networks to push the snapshots into pushDPN: false pushChronopolis: false # Logging configuration logging: file: /var/log/bridgeintake/intake.log level: org.springframework: ERROR org.hibernate: ERROR org.chronopolis: debug org.chronopolis.intake.duracloud.config: trace # Extraneous settings # disable SNI on https connections - false automatic cleaning of staging areas (not well tested) # only perform dry-runs when the Cleaner runs # disable SNI on https connections - false is the default and recommended value cleanerEnabled: false cleanDryRun: false disableSNI: false |
...
is the default and recommended value
disableSNI: false
|
Multi-Bridge Support
As of Release 2.4.0, configuration for querying multiple bridges is supported. This is done in the application.yml under the
Highlight | ||
---|---|---|
| ||
Duracloud |
properties. e.g.
Code Block | ||
---|---|---|
| ||
duracloud:
bridge:
- name: Dev Duracloud Bridge
snapshots: /duracloud-bridge/snapshots/
restores: /duracloud-bridge/restore/
username: dura-api-username
password: dura-api-password
endpoint: https://duracloud-bridge-dev.ucsd.edu/
- name: Dev Chronopolis Bridge
snapshots: /chrono-bridge/snapshots/
restores: /chrono-bridge/restore/
username: chrono-api-username
password: chrono-api-password
endpoint: http://tdl-bridge-dev.ucsd.edu/ |
Release Notes
Release 2.4.0
11 January, 2019
- Bridge consolidation work to bring multiple bridge querying to a single service
- Update notification of missing Depositors to fire only once for the lifetime of the bridge
- Fix Bug resulting in successive snapshot runs not being processed if a check against the Depositor fails
- Update ChronopolisIngest for 3.0.0 workflow
Release 2.3.2
09 August, 2018
...