You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Time/Place

This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:

Attendees 

  1. Danny Bernstein 
  2. David Wilcox 
  3. Jared Whiklo 
  4. Peter Winckles 
  5. Daniel Lamb  
  6. Ben Pennell
  7. Calvin Xu 
  8. Michael Ritter 
  9. Demian Katz (star)
  10. Geoff Scholl

Agenda

  1. Announcements
    1. Camel Toolbox Sprint - first week in October.
  2. Review of  Work in Progress (round robin)
    1. Camel Tool Box (CTB) Update 
      1. completed :
        1. fcrepo-indexing-triplestore
        2. on/off switches or services
        3. Mega-PR with instructions for testing solr and fuseki.
      2. PRs
        1. Ready to be merged: https://github.com/fcrepo-exts/fcrepo-camel/pull/163
        2.  New PR which depends  on the  above  PR: https://github.com/fcrepo-exts/fcrepo-camel-toolbox/pull/160
      3. TODO
        1. Dockerization / Compose 
        2. microservices still needing to be upgraded:
          1. fcrepo-audit-triplestore
          2. fcrepo-fixity
        3. Integration tests for the spring app
        4. Documentation
        5. Consolidate / Rationalize Property Names
  3. Configurable HTTP Service for Camel Toolbox
  4. Dangling PRs:
    1. docker multi architecture builds.
      1. https://github.com/fcrepo-exts/fcrepo-docker/pull/14
      2. https://github.com/fcrepo/fcrepo/pull/1923 
  5. Releases
    1. fcrepo-upgrade-utils  - 6.1.0 - not done yet
  6. Additional Priorities for Sept/October?
  7. Your topic


Tickets

  1. In Review

    type key summary assignee reporter priority status resolution created updated due

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  2. Please squash a bug!

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  3. Tickets resolved this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  4. Tickets created this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes

  1. Announcements
    1. Camel Toolbox Sprint - first week in October.
      1. Focus on reaching 1.0 release
      2. One-week sprint should be enough; things are already "mostly there."
  2. Review of  Work in Progress
    1. Camel Tool Box (CTB) Update 
      1. Danny finished triplestore indexer this week, completing main goal of Camel Tool Box upgrade
      2. 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.
      3. 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.
      4. You can also test the new PR using Docker configs (see notes in PR description for details)
      5. Major remaining TODOs:
        1. porting fixity and audit-triplestore, which is just pulling logic out of OSGI and updating tests.
        2. Could use a smoke test for the spring app as well.
        3. Solr integration test would be nice
        4. 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.
      6. 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).
        1. A diagram might be a good addition to the README as this matures further.

Actions

  • No labels