...
- Announcements
- Camel Toolbox Sprint - first week in October.
- Focus on reaching 1.0 release
- One-week sprint should be enough; things are already "mostly there."
- Camel Toolbox Sprint - first week in October.
- Review of Work in Progress
- Camel Tool Box (CTB) Update
- Danny finished triplestore indexer this week, completing main goal of Camel Tool Box upgrade
- Also added on/off switches for reindexer, Solr and Triplestore (all off by default); Fedora service is always on by default and has no switch (assumed to be needed). ldpath service is also always on.
- Mega-PR of changes has been put up (https://github.com/fcrepo-exts/fcrepo-camel-toolbox/pull/160). Please look (even if just a section) and critique; Danny will extrapolate your comments to apply changes to all relevant files. There has been a focus on integration tests, since APIs and style/conventions have changed since the earlier version of Camel.
- You can also test the new PR using Docker configs (see notes in PR description for details)
- Major remaining TODOs:
- porting fixity and audit-triplestore, which is just pulling logic out of OSGI and updating tests.
- Could use a smoke test for the spring app as well.
- Solr integration test would be nice
- Some property names are inconsistent; Danny kept them as-is for now during migration, but it would be good to revisit and make them more logically normalized. All properties have been documented on the README test.
- Demian asked about production deployment; Danny suggested that this involves having a separate ActiveMQ server that receives ActiveMQ messages emitted by Fedora and stores them in a durable internal queue, and then the Camel Toolbox runs from that queue to avoid dropping of messages. (You should also configure Fedora to use a queue instead of a topic, to ensure that messages are not lost if something goes down outside of Fedora).
- A diagram might be a good addition to the README as this matures further.
- Camel Tool Box (CTB) Update