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. Andrew Woods  
  3. Peter Winckles 
  4. Ben Pennell  
  5. Ben Cail  (out)
  6. Jared Whiklo 
  7. David Wilcox 
  8. Calvin Xu 
  9. Thomas Bernhart
  10. Daniel Lamb (star)

Agenda

  1. Announcements/Updates
    1. F4->F5→F6 migration
    2. Terraform deployment tool
    3. UVA Pilot Kick-off
    4. 2020-09 Fedora 6 Sprint
  2. Planned Breaking Changes (standing topic)
  3. Getting to Alpha 
    1. Migration
    2. Direct/Indirect Containers
    3. Comprehensive testing of (question) features
    4. ?
  4. PR roundup:
    1. core: https://github.com/fcrepo4/fcrepo4/pulls
    2. fcrepo-docker : https://github.com/fcrepo4-labs/fcrepo-docker/pull/10
  5. Fedora 6 Testing
  6. Ben Pennell 'sTwo Questions:
    1. What should be the outcome of PUTing the default GET response back to the server in general?
    2. Should fedora attempt to filter out any generated triples?
  7. Your Topic Here

    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

    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. 4 → 5 → 6 migration has landed.  Many thanks toPeter Winckles
      1. 4 → 5 misses versions, but otherwise quite functional. 
      2. Danny Bernstein will document the process
    2. Terraform deploy tool will be pushed to Github soon
    3. UVA pilot migration kicking off for the IMLS grant
      1. Migrating one (potentially 2) Fedora 3 instances
    4. Recent Sprint Recap
  2. Planned breaking changes
    1. Nothing coming up, but Jared Whiklo may have some changes where a reindex would be recommended
  3. Getting to alpha
    1. Migration stuff is done
    2. Direct/indirect containers work is ongoing
    3. Performance testing
      1. After around 3,000,000 objects Andrew Woods started to experience db connection fails
      2. Also noticed a significant drop in performance after a period of time.  E.g. 6000 objects a minute at first but eventually it drops to 600 objects a minute
      3. Hard to recreate / do anything about it without some sort of metrics
  4. PR Roundup
    1. Did not discuss PRs in depth, but will try and prioritize open PRs and touch base with Jared Whiklo and Ben Pennell
  5. Ben Pennell's questions
    1. It would be preferable to continue to support the 'lenient' prefer header, ignoring server managed triples in the message body if that header is provided

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)
  • Danny Bernstein document the process of migrating from 4 → 5 → 6
  • 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.
  • Danny Bernstein to organize a special topic call around the topic of high availability.





  • No labels