...
- Danny Bernstein
- Andrew Woods
- David Wilcox
- Peter Winckles
- Ben Cail
- Aaron Birkland
- Ben Pennell
- Paul Cummins
- Bethany Seeger
- Jared Whiklo
- Yinlin Chen
Part 2:
Agenda
- Announcements
- #sprints channel
- #github channel?
- kubernetes support in Deployment Tooling
- #general channel community issue
- fcrepo-upgrade-utils
- Minimal 4 →5 migration needs testing and code review:
- Update on Fedora 6 Pilots (NLM, Docuteam, UWM)
- migration-utils PRs
- Java 11: When?
- Sprint Planning
- 6.0 Architecture Review
- Transaction Sidecar Spec Update
- OCFL community feedback on OCFL client with Database as authoritative metadata source
- https://github.com/pwinckles/ocfl-java-parent
- Problems requiring design
- Tombstone Support in 6.0.0
- Caching/indexing strategy
- What caches and indexes do we need(ie in what layer(s)?)
- OCFL client
- Persistence Implementation (OCFL)
- Kernel Implementation
- Physical location of the cache (assuming we want to plan for horizontal scalability support)
- Cache per instance?
- synchronizing changes across instance
- 1 Global cache/index?
- Cache per instance?
- What caches and indexes do we need(ie in what layer(s)?)
- Your topic here...
...
- Announcements
- sprints channel open & participants invited
- #github - Slack integration with github for PRs, ... - Jared will create the new #github channel.
- What should we do with GitHub issues?
- fcrepo4-docker - has kubernetes support now: Deployment Tooling
- #general channel - i- issue with simple file persistence error. Size is wrong.
- point Islandora to mysql or postgres for default configuration.
- look at updating documentation.
- The hyrax setup instructions (https://github.com/samvera/hyrax/wiki/Production-Installation-Overview)
links to Deploying Fedora 4 Complete Guide
which says to use https://github.com/fcrepo4/fcrepo4/blob/4.7-maintenance/fcrepo-configs/src/main/resources/config/file-simple/repository.json
which uses the simple file system persistence approach
- The hyrax setup instructions (https://github.com/samvera/hyrax/wiki/Production-Installation-Overview)
- fcrepo-upgrade-utils
- should work for basic setups. People should try it out. Doesn't work with ACLs yet, but that's next.
- Fedora 6 pilots
- OCFL client (https://github.com/pwinckles/ocfl-java-parent) - implements most of the spec.
- API - put/get at object level, read/update for individual files. Automatically commits (in single version) at the end of the object update changes.
- Doesn't handle multiple clients writing at the same time (& Go client doesn't currently support that, either).
- OCFL spec talks about deposit directory for staging content, but defines content at rest, not content in motion.
- Aaron suggested OCFL RFCs repo - implementation patterns, definitions, clarifications, ...
- What functionality should an OCFL client have? It should be written up.
- OCFL client (https://github.com/pwinckles/ocfl-java-parent) - implements most of the spec.
- Java 11
- Peter's code uses 11. Should make a decision at some point and switch everything.
- Ideal scenario: all fedora eco-system tooling (fcrepo4, fcrepo-came-toolbox, fcrepo-import-export, fcrepo-upgrade-utils) will compile Java 11 source.
- bytecode compatibility ? Should that go to 11 as well?
- Draft JVM policy re-wording https://docs.google.com/document/d/1ulXLOF2dL-vEUKhUFjkL8UG97wjXJ-9dbmytKVwzDMM/edit
Current Oracle LTS is Java 11
We should likely move to Java 11 this calendar year
How hard is it for the community to move to Java 8
Andrew to email to community list
What is our plan?
LTS releases: 4.7
Fedora 6 to use openjdk-11
needs Java 11 to run
- Sprint planning
- OCFL implementations
- OCFL Community meeting next week, Wednesday
Conversation to continue on Slack
- Request for Aaron B to document thoughts
- Separation of concerns: what does Fedora need to know, what is internal to the OCFL client
- Danny to update diagram (include 'deposit' space and 'versions')
- Request for Aaron B to document thoughts
- Transaction sidecar spec
- https://github.com/fcrepo/fcrepo-specification-atomic-operations
- Peter E is working on this
- Interest in scoping transactions at the Archival-Group
- OCFL client with database as metadata store
- https://wiki.duraspace.org/display/FF/Fedora+2019+Architectural+Diagrams#Fedora2019ArchitecturalDiagrams-OCFLClientwithpersistentdatabaseasauthoritativemetadatasource
- Diagram needs to be re-worked
- Fedora transactions will need support from underlying OCFL client
- An OCFL client backed by a database may be able to support transactions that span multiple OCFL objects
- Diagram details an OCFL interaction with transactions scoped to a single OCFL object
- Todo: design how an OCFL client would support transactions over a single OCFL object
- Todo: design how an OCFL client would support transactions over multiple OCFL objects
- https://wiki.duraspace.org/display/FF/Fedora+2019+Architectural+Diagrams#Fedora2019ArchitecturalDiagrams-OCFLClientwithpersistentdatabaseasauthoritativemetadatasource
Conversation to continue on Slack
- Request for Aaron B to document thoughts
- Separation of concerns: what does Fedora need to know, what is internal to the OCFL client
- Danny to update diagram (include 'deposit' space and 'versions')
- Request for Aaron B to document thoughts
- OCFL implementations
Actions
- Danny Bernstein will reach out to Greg about DRASTIC test results
- Aaron Birkland to work with Andrew Woods to get the Go client working on travis.
- Aaron Birkland to look explore notion of OCFL client with database as authoritative metadata source + asynchronous writing of the inventory.json file
- Peter Eichman and maybe Ben Pennell to make recommendations re transaction side car specification.
...