Time/Place

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

• Time: 11:00am Eastern Daylight Time US (UTC-4)
• Audio/Video Conference Link: https://lyrasis.zoom.us/j/396037251
  
  • 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/

Attendees 

1. Danny Bernstein
2. Andrew Woods 
3. Peter Winckles 
4. Ben Pennell 
5. Ben Cail 
6. Jared Whiklo
7. David Wilcox
8. Calvin Xu 
9. Thomas Bernhart

Agenda

1. Announcements/Updates
   
   1. Sprint is coming up in two weeks.
2. Planned Breaking Changes (standing topic)
3. Mementos
   1. Wrap up: Binary and Binary Description Mementos:  to version together or apart?
      1. Delete mementos?
4. PR Round Up
   1. Update fcrepo-storage-ocfl to touch related resources (I need this for my PR to use fcrepo-storage-ocfl in core)
   2. A little db cleanup
   3. Update migration-utils to use fcrepo-storage-ocfl
5. Fedora 6 Testing
   1. Pilot testing
      1. Current
         1. NLM test fedora 6 deployed on tomcat 9 mysql 8, there is a RecoverableDataAccessException timeout error even with autoReconnect and tcpKeepAlive set to true FCREPO-3401
         2. latest migration utility 0727 keeps stopping on bad id, eg <Migration utility problem - stop on bad id Unable to resolve internal ID "nlm:nlmuid-9514335-bk+MARCXML+MARCXML.0"!> https://jira.lyrasis.org/browse/FCREPO-3402
      2. Future
   2. Testing tools update/invitation
6. High availability
   1. The use case we've been hearing about
   2. What would it take for us to support

7. Your Topic Here

   Tickets resolved this week...

   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.

Tickets

1. In Review

   Click here to expand...

   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!

   Click here to expand...

   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:

   Click here to expand...

   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:

   Click here to expand...

   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. Upcoming sprint - focusing on fedora 4/5 migration, container support, valkyrie compatibility (if anyone is available to test, otherwise will likely focus on unimplemented search API)
   2. Fedora User group meeting was successful, slides are online now. There's another one for european timezones in about 2 weeks.
2. Breaking Changes
   1. no new ones
3. Mementos
   1. Binary/Description mementos - reached a conclusion on this last week, to version them together
   2. Deleting Mementos
      1. Fedora 5 allows you to delete mementos. That is not possible in Fedora 6 without rewriting the OCFL object.
      2. Support for delete of mementos is MAY in a specification
      3. Conclusion is to disallow, Peter will add it to the breaking changes document
4. PR Round Up
   1. Need to wrap up the fcrepo-storage-ocfl so that PR can be opened against fedora core before the sprint
   2. Will add jiras to document the changes
   3. We will move fcrepo-storage-ocfl into the fcrepo4 core github organization
   4. Is it time to rename fcrepo4 organization to fcrepo?
      1. We will move almost everything in it over to the new name, old path should redirect
      2. Danny and Andrew will tag team this next week
5. Fedora 6 Testing
   1. Pilot Testing
      1. NLM has mysql setup, sometimes there are some db connection issues
         1. Index came up in a reasonable amount of time. Is just 100 migrated records.
         2. Updated migration util keeps stopping when it hits bad ids, when it is unable to resolve an internal id to a fedora object. Previously it did not halt.
            1. Calvin will create a Jira ticket to flag this issue, indicate the desired behavior
      2. Thomas will be able to test migration from 3 to 6 in the next 3-4 weeks
      3. Emory has gotten support to invest time in testing
   2. Test tooling
      1. Andrew has been testing jmeter tests on AWS, using mariadb in docker. First test died in less than 100k objects, something DB related. Will try again with beefier instance.
6. High Availability
   1. How far is fedora 6 from supporting this?
      1. Transactions are central to the databases, so it would probably work as long as the databases are used across fedoras
      2. Need object locking
      3. Need to have shared staging for changes, and shared OCFL storage/repository
      4. Could fedora be setup with one writer and many readers?
         1. There is no way to tell fedora 6 that it is in read only
         2. If you don't use any other ACLs, you could configure a read only root WebACL for some servers to block writes
   2. Danny will start a document for this topic and the discussion so far

Actions

• Danny Bernstein to ensure that a JIRA exists for scenario of transaction does not succeed completely, but rollback does succeed (see: 2020-08-13- Fedora Tech Meeting)
• Peter Winckles to create a JIRA to investigate support for optimistic locking and mutable head (see: 2020-08-13- Fedora Tech Meeting)
• Who:  Clarify in documentation that multiple simultaneous writes to OCFL are not supported
• migration-utils - translating RELS-EXT/INT into RDF in Fedora 6: is the functionality there? If not, add it.