Hyrax Fedora 6 Working Group Update

[Arran Griffith]

Hi Everyone,

I hope you’ve all had a nice week. I wanted to share an update from today’s Hyrax Fedora 6 Working Group meeting. The full meeting notes can be found here: https://samvera.atlassian.net/wiki/spaces/samvera/pages/2411921409/2024-03-28+Hyrax+Fedora+6+Working+Group

 

Overview:

• Hyrax Maintenance Working Group (HMWG) sprints have not focused on Sirenia yet, but they will be working toward Hyrax 5.1 which will include outstanding bug fixes for Sirenia, and updating components to work with the pair-tree changes enabled with Fedora 6.5.
• There is no fixed timeline for delivery on Hyrax 5.1, but hopeful it will be before Hyrax Tech Lead term is over.
• The next HMWG sprint will start April 15, 2024.
• Emory University has been continuing work building out their production instance of Hyrax 5 with Fedora 6.x
• They are moving one instance from Fedora 3 to 6 + Hyrax 5 but using the fcrepo-import-export tool in lieu of the 3-6 migration-utils tool then plan to re-ingest all of the data via Bulkrax.
• Will continue to share updates as they work through local configurations.
• The WG will begin to move toward initial planning for performance testing of Hyrax 5 + Fedora 6.x and Valkrie.

 

The last update we want to share is that we have officially updated the Scope and Deliverables of the Hyrax Fedora 6 Working Group. The WG was originally created to evaluate, document and scope the work required for Hyrax to use Fedora 6.x as a back end - See the original charter here, however, much of the pre-work initially identified was either in-progress or completed by the time the group was beginning to look at it.

As of January 2024, the WG has committed to continuing to support the efforts to see Hyrax 5.0 released and working with Fedora 6.x via Valkyrie. This working group will be responsible for the following:

Deliverables & Timeframe

The following work aims to be accomplished before the end of the calendar year:

1. Sirenia as a fully functional application of Hyrax 5.0 + Fedora 6.x with Valkyrie.
1. Acceptable % of tests passing, as defined by the WG, from the following: Hyrax 5.0.0 sirenia testing .xlsx
2. Identify and create tickets for issues related to failing tests from the testing sheet above.
1. From the identified tickets, the WG will be responsible for distributing workload and/or recruiting community involvement to resolve the outstanding tickets.
2. Performance Testing of Hyrax 5.0 + Valkyrie + Fedora 6.x

1. Using the use cases gathered (Stakeholder Use Cases) as a starting point, identify what performance metrics are considered essential and would be of interest to the community more broadly.

1. Review any other available performance results from Hyrax 5 testing with other backend solutions (ie. Postgres).

2. Using Nurax, or an established testing environment, explore the current performance of the repository infrastructure under a pre-defined set of profiles and situations

1. Establish limits for pass/fail
2. Identify issues and document recommendations for optimization
3. Compare testing results to any other available metrics from Hyrax 5 testing with other backend solutions (ie. Postgres).

3. The results of the performance testing will be shared with the community as outputs of this work.

3. Migration Considerations

1. The WG will continue to discuss migration efforts required to move from older versions of Hyrax + Fedora 4.x to Hyrax 5.x + Fedora 6.x and continue to explore options for this work.
2. The WG may be able to provide recommendations for migration tooling or documentation based on the outputs of these on-going discussions.

 

We are excited to be moving forward with this work and look forward to continuing to share updates with the community. If you would like to get involved or have capacity to participate, please reach out to myself (arran.g...@lyrasis.org) or Heather Greer Klein (hea...@samvera.org) and we can connect you with the correct individuals. Many hands make light work 😉

 

Have a great weekend everyone!

Cheers,

Arran – on behalf of the Hyrax Fedora 6 Working Group

---

Arran Griffith

Program Manager, Fedora Program

Lyrasis