...

1. Danny Bernstein   
2. Andrew Woods
3. David Wilcox

Agenda

1. Announcements
   1. Docker options: Deployment Tooling
   2. Fedora 5.1.0  Release 
2. Update on Fedora 6 Pilots (NLM, Docuteam, UWM)
   1. migration-utils work
      1. Configure "fedora4Client" to new implementation of the Fedora4Client.java interface
      2. Writing to OCFL instead of Fedora4/5/6 API
3. Sprint Planning
   
   1. 6.0 Architecture Review
   2. Problems requiring design
      1. Transaction and Lock Management
         1. Transactions scope:  what do we need to support?
            1. Individual Resources
            2. Groups of resources
            3. Containment hierarchies 

         2. A Fedora transaction may span multiple HTTP Requests.   Assuming that we do not want to commit anything to OCFL until the Fedora Transaction is committed, how do we maintain the state of open OCFL Sessions 

            1. across requests?

            2. across instance reboots?
            3. across multiple horizontally scaled instances? 

            4.  How also do we ensure that two requests using the same transaction ID against the same OCFL object do not stomp on each other

         3. Globally accessible state (for horizontal scalability)
      2. Caching/indexing strategy 
         1. What caches and indexes do we need(ie in what layer(s)?)
            1. OCFL client 
            2. Persistence Implementation (OCFL) 
            3. Kernel Implementation
         2. Physical location of the cache (assuming we want to plan for horizontal scalability support)
            1. Cache per instance? 
               1. synchronizing changes across instance
            2. 1 Global cache/index?  
4. OCFL implementation updates
   1. migration-utils pull-request
   2. Peter Winckles work-in-progress
      1. https://github.com/pwinckles/ocfl-java-parent
      2. https://github.com/pwinckles/ocfl-java-api
      3. https://github.com/pwinckles/ocfl-java-core
      4. https://github.com/pwinckles/ocfl-java-filesystem
5. Your topic here...

...