This is a cursory summary of changes to various storage-inventory components. Check the README in specific modules for details.
In minoc.properties
:
- added
org.opencadc.minoc.trust.preauth
- removed
org.opencadc.minoc.publicKeyFile
- added
org.opencadc.minoc.readable
- added
org.opencadc.minoc.writable
A minoc
instance will download a public key from each trusted service and
use the public key(s) to validate URLs that include a preauth token.
A minoc
service will advertise (via inventory.StorageSite record in the database) the
readable and writable status; this information is synced to global inventory and
used by raven
to determine if it should generate PUT or GET URLs that use the minoc
service(s) at that site. The configuration of readGrantProvider(s) and
writeGrantProvider(s) implicitly determines the status (readable and writable
respectively); configuration of any trust.preauth will also implicitly make make the
status readable and writable.
The explicit readable and writable configuration options will override the above implicit logic and set the status accordingly. This is currently optional but may be required in a future version.
New optional config files:
- added
cadc-log.properties
- added
cadc-vosi.properties
in catalina.properties
:
- added
org.opencadc.raven.inventory
connection pool
A raven
service uses this pool to perform database initialization.
In raven.properties
:
- added
org.opencadc.raven.keys.preauth
- removed
org.opencadc.raven.publicKeyFile
andorg.opencadc.minoc.privateKeyFile
When configured to do so, a raven
service will generate it's own public/private key pair
and use the private key to sign minoc
URLs. All the minoc
services known to the global
raven
service must also be configured to trust raven
.
New optional config files:
- added
cadc-log.properties
- added
cadc-vosi.properties
In cadc-tap-tmp.properties
:
- must configure a
org.opencadc.tap.tmp.StorageManager
A luskan
service now uses the DelegatingStorageManager` so this config file must
specify which storage manager implementation to use along with existing
implementation-specific configuration options.
New optional config files:
- added
cadc-log.properties
- added
cadc-vosi.properties
This is a new service that implements the IVOA VOSpace 2.1 REST API to provide user-managed
hierarchical storage. vault
is deployed with it's own database and an associated inventory
database, uses inventory services (minoc
) for file storage and access.