Fedora4 Team Completes Fifth Beta Phase Sprint: Refining Fedora 3 to 4 Upgrade Feature
Submitted by on Fri, 2013-10-25 15:53
Winchester, MA The Fedora team has completed the fifth sprint within the "Beta Phase" of Fedora4 development. The work of this and each sprint is planned and completed thanks to the contributions of Fedora stakeholder institutions which allocate developer time. If you would like to be involved with Fedora4 development, please send an email to Andrew Woods email@example.com, or the Fedora Steering Committee firstname.lastname@example.org. If you have comments on the work from this sprint, please also send an email or comment directly on the wiki.
Read the the Sprint B5 summary:
About Sprint 5, Beta Phase
Michael Durbin - University of Virginia
Ye Cao - Max Planck Digital Library
Osman Din - Yale University
Nigel Banks - Discovery Garden
A. Soroka - University of Virginia
Frank Asseg - FIZ Karlsruhe
Fedora 3 to 4 Upgrade
This sprint had a focus on refining the Fedora 3 to 4 Upgrade feature.
The previous implementation enabled connecting to a Fedora 3 repository, and exposing its objects in a flat, single-level structure within the Fedora 4 repository. In an effort to improve the performance of the connector used to project over a Fedora 3 repository, these objects are now internally structured as a multi-level tree with a configurable number of children nodes at each branch-point in the tree. The result is that accessing any given node now leverages tree searching logic, and load-time is reduced to only what is required in loading the objects at a given point in the tree.
More description of the Fedora 3 to 4 Upgrade capability can be found on the wiki .
Although the Islandora/Fedora 4 integration does not generally involve updates within the Fedora codebase, this work is included in sprints due to the importance of ensuring Islandora expectations and Fedora development remain synchronized.
This sprint initiated the effort of retooling the Islandora/Fedora connector (Tuque) to dynamically construct the appropriate Fedora client based on the discovered version of the backend Fedora repository. This sprint represents a significant step towards enabling Islandora's support for either a Fedora 3 or Fedora 4 backend.
One of the limitations of Fedora 3 has been the inability to scale the repository horizontally in support of increased access requests, high-availability, and/or bulk ingesting.
Fundamentally, Fedora 4 inherits clustering capabilities from the underlying ModeShape platform. This sprint started the process of provisioning two independent clusters from stakeholder institutions and establishing performance benchmarks over those clusters. The configuration and tuning of Fedora 4 clusters will be a common sprint theme until appropriate performance numbers have been achieved.
One of the hallmarks of an agile development process is the inherent commitment to continual refinement and refactoring of the codebase.
In the course of implementing and testing the Fedora 3 to 4 Upgrade capability, performance limitations were discovered when loading hundreds of thousands of objects. The ground-work for addressing these issues was laid during this sprint. Namely, the underlying model of iterating over objects and properties was introduced in replacement of the approach of loading these all into memory.
Subsequent sprints will expose this iteration model at the Fedora user API level.