...
- Time: 11:00am Eastern Daylight Time US (UTC-4)
- Audio/Video Conference Link: https://lyrasis.zoom.us/j/3960372517012102599
- Meeting ID: 396 037 251
- Find your local number: https://lyrasis.zoom.us/u/ad6Xb7q3ia
Join fedora-project.slack.com on the "tech" channel
- Self-register at: http://slack.fcrepo.org/
...
- Danny Bernstein
- Andrew Woods (out)
- Peter Winckles
- Ben Pennell (out)
- Ben Cail
- David Wilcox (out)
- Daniel Lamb
- Calvin Xu
- Demian Katz
- Geoffrey Scholl
Agenda
- Announcements/Updates
- IMLS Grant for Fedora Migration Path
- Planned Breaking Changes (standing topic)
- dedicated slack channel for breaking changes or other critical notifications?
- Meeting with Emory Team Debrief
- Hyrax F6 integration
- Testing interests
- Fedora 3-6 Migration
- Fedora 4/5 → Migration
- OCFL on S3
- Other interests: high availability
- Sprint Planning
- Fedora 4/5 → migration
Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3391 Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-33933392 Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-33923393 Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3394
- External Binaries
- Other
Jira server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3395
- Fedora 4/5 → migration
- Fedora 6 Testing
Your Topic Here
Expand title Tickets resolved this week... Jira server DuraSpace JIRA jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
...
In Review
Expand Jira server DuraSpace JIRA jqlQuery filter=13100 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Please squash a bug!
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets resolved this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 Tickets created this week:
Expand Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
Notes
- Slack channel for breaking changes during as Fedora 6 is being developed?
- Move most development conversations into a "bleeding edge" channel (which will replace the "sprint" channel), and then post to the "tech" channel if a backwards breaking change is made
- Demo Server
- Auto-updating on AWS every time a new image is pushed to Dockerhub (in theory)
- REST API is working, but UI isn't available. Andrew Woods and Danny Bernstein will circle up so they both have access and can work on it.
- "Next Demo" topic pushed back until David Wilcox gets back from vacay
- Committers / Leaders Call Debrief
- Getting everyone on Fedora 6 is top priority
- For 4/5
- Export content using Import/Export tooling (this exists)
- Import the exported content (does not exist yet)
- How best to manage the fact that you've got to double the data? Unavoidable, most likely just needs to be clearly explained to the user in documentation.
- Is there a chance to share common code between the other tooling (migration utils, import/export, etc...) when moving to Fedora 6?
- Migration tooling must be there before 6 can be an alpha
- Migration tool strategy:
- extract abstraction layer for writing fedora objects to ocfl from core into a common library
- extract read fcrepo4/5 export functionality from fcrepo-import export tool into another common library
- Use above libraries in the fcrepo-upgrade-util for transforming an export to Fedora OCFL.
- Danny Bernstein to create JIRAs to organize this work.
- Proposals for topic August 10th Fedora usergroup is still open
- There will be no code breaking changes this week, last week had two
- Emory user group are looking into fedora 4/5 migration to fedora 6 in Hyrax stack integration/connector should start in about 6 weeks
- Emory user group is also interested in running multiple fedora instance in cluster against one ocfl directory load-balanced for high availability
- f4-5→ 6 upgrade plan:
- create an abstraction layer that encapsulates the translation of a Fedora resource into an OCFL resource.
- use it in fcrepo-migration-utils
- then (potentially) insert it into the core between the OCFLObjectSession and the Persister layers
- Do we need progress meter for index rebuild activity? Is this even feasible?
- How about "resume" index build functionality?
- We would have to be able to assume that the OCFL repo had not changed
- We also do not know at this time how long it takes to iterate over the repo (without doing any index updates).
- How about "resume" index build functionality?
- Next steps:Calvin Xu will try using a separate database server (mysql, mariadb or postgres) on a small subset of items (1000) to measure performance improvement and will report back on next week's call.
Actions
- Danny Bernstein to ensure that a JIRA exists for scenario of transaction does not succeed completely, but rollback does succeed (see: 2020-07-30- Fedora Tech Meeting)
- Peter Winckles to create a JIRA to investigate support for optimistic locking and mutable head (see: 2020-07-30- Fedora Tech Meeting)
- Who: Clarify in documentation that multiple simultaneous writes to OCFL are not supported
- Peter Winckles Create a Jira to update the locations files stored in OCFL
- migration-utils - translating RELS-EXT/INT into RDF in Fedora 6: is the functionality there? If not, add it.
...