Call Details
Attendees
Agenda
(If you have an agenda suggestion/addition, please leave a comment!)
- DuraCloud 6.0.0 release review
- Removal of DPN references
- Updated AWS client
- Update on COPPUL grant status
- Looking to be able to run DuraCloud outside of AWS
- Looking to connect their OpenStack Swift storage
- We may need to hold on multipart upload implementation until their approach is determined
- DuraSpace / Lyrasis merger update and impact
- Sprint/development activity plans
- Nick still available for dev work?
- Priority development work (see backlog)
- Priority issues list
Resources
DuraCloud documentation
- User documentation (wiki)
- Deployment documentation (github)
Minutes
- DuraCloud 6.0.0 release review
- Removal of DPN references – transitioning with Chronopolis, great opportunity to make this happen. Talked through TDL needs for Chronopolis bridge; would need to work that through with Sibyl and others at UCSD.
- Updated AWS client
- Update on COPPUL grant status
- Looking to be able to run DuraCloud outside of AWS. Want to run it on local systems and not be dependent on AWS pieces.
- Looking to connect their OpenStack Swift storage – Bill is hoping they can just use the S3 API connector, but they are running into problems. Might need to resurrect the OpenStack provider we removed. Bill would prefer not to do this if possible.
- We may need to hold on multipart upload implementation until their approach is determined. We dropped OpenStack to do this. Bill is on calls and will keep this group updated on the progress. They seem to have 3-4 developers putting time into this. Bill doesn't think a lot will need to change from the application standpoint.
- DuraSpace / Lyrasis merger update and impact
- Boards will vote this week on merger. We should know soon about moving forward. At this point looks positive. In terms of impact, nothing expected short term. Expected to be finalized in the summer. Longer term, less clear where Bill and Heather will land and who else will jump into project. Bill hopes it will be more people. LYR has expressed interest in using DuraCloud as a backend for their own services, expanding use seems likely. A lot of questions yet to answer. Feelings are positive about the prospects for DuraCloud as it seems likely to extend the reach and our ability to make people aware of it. Not sure how involved Danny will be, as he has mostly been working on Fedora.
- No real concerns right now, TDL expects that DC support will continue from merged organization.
- Sprint/development activity plans – Bill not included to schedule a sprint for March because of the need for merger-related time. Bill will continue to work on DuraCloud and might be able to pull in Danny for a bit.
- Nick still available for dev work? Nick – some flexibility before TCDL. Plenty of work to do in March. Should we wait until fall? Bill – no need to wait to fall, but reluctant to plan until we learn more about the LYR side and people/resources available. If we can bring people at LYR on board, would like to involve them in the sprint. April/May, summer are possibilities. Could continue to work and touch base and chat.
- Priority development work (see backlog)
- Priority issues list
- What needs to happen sooner rather than later. 1192 selected for development, some issues in the backlog. Could do 6.1 release with bug fixes before summer. Could also get a better understanding of sync tool UX, but Heather and Courtney are quite busy.
- Nick: could select priority issues and could dedicate some available time to a few issues and bug fixes for a June 1 release.
- Issues selected: 1192, 1186. From backlog:
Actions
- Determine tickets that are small enough to accomplish is a short period of time: 1192
- Bill Branan will check with Andrea about in-progress tickets
-
- Indicates who will be taking minutes