Date: Thu, 28 Mar 2024 20:29:55 -0400 (EDT)
Message-ID: <257120573.29282.1711672195640@lyrasis1-roc-mp1>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_29281_1184517969.1711672195640"
------=_Part_29281_1184517969.1711672195640
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
2018-05-22 DuraCloud Contributor Call
2018-05-22 DuraCloud Contributor Call
Call Det=
ails
Attendees
Agenda
(If you have an agenda suggestion/addition, please leave a comment!)
- Report from the Mozilla Global Sprint
- Communicating as a group (email, slack, gitter, etc)
- Working together
- Sprints or more independent work? How to coordinate and collaborate?
- Development priorities=20
- Needs expressed by customers (example: se=
arch)
- Operational needs
- Secondary storage providers=20
- Reasons to add a provider
- Requirements to add a provider
- Providers worth considering (example: O=
racle)
- TDL and 4Science experience with use and implementation of DuraCloud=20
- Pain points
- Customer feedback/response
- How could this be made easier for others in the future?
Minutes
- Report from the Mozilla Global Sprint=20
- Learned a lot from the open leaders program. Will pull together the res=
ources from that experience for other projects and for DuraCloud to pay att=
ention to being open and inviting and having resources to share. Global spr=
int was a little disappointing, so one dropped in but it was worth the plan=
ning. We learned we need to be really intentional about engagement and reac=
hing out. Not terribly surprising but useful to know. Could get a lot done =
in a small period of focused time on a DuraCloud sprint. Background work fo=
r the sprint was valuable. Person hours used? Could look at hours to see. C=
ould be done more quickly now with template in place. Timing was poor and o=
utside our control, so one planned with this group would be much better.
- Communicating as a group (email, slack, gitter, etc)=20
- Used Gitter for the sprint, but within DuraSpace Slack is more commonly=
used and would be easier. Is that true for this group? Everyone is in Slac=
k already, lowest barrier. Separate Slack channel, or communicate via email=
? Email for now while the group is small, and could invite to a Slack chann=
el.
- Working together
- Sprints or more independent work? How to coordinate and collaborate? Tr=
ying to understand our varying priorities and what could move us forward. C=
ould do a development sprint or a higher level sprint that would give an op=
portunity to do some prioritizing and organizing. Having user feedback ahea=
d of a sprint would be useful for prioritizing. 1 or two day sprint for pri=
oritizing needs and a coordinated development sprint, but it is all a matte=
r of timing. Development deep dives would be useful, a two week sprint or a=
little longer to figure out how long things take. 1 day planning dash=
to share user feedback and discuss priorities, and then follow with a deve=
lopment sprint looking at priorities from the dash.
- October 5th for planning dash, October 15-26 for development work
- Development priorities=20
- DuraSpace working on transitioning to multipart upload on file transfer=
s. Partway into that work, hoping to be done by fall. Also sprint in place =
for updating streaming from Flash based to HTTP livestreaming.
- Customers have been asking for search feature. What does that mean and =
would that be a priority? Tag and file name search. File name search would =
be really helpful for TDL as well. Might be better framed as a find feature=
.
- Other features that are requested? Duplication among regions? 4Science =
is looking at this. Question if this is the best approach, as Amazon built-=
in application for cross-region replication might be a better approach. Bil=
l: would want to do some verification. 4Science will update on this. <=
/li>
- Operational needs: TDL: more informative error handling, better sync to=
ol tooltips. Release notes for new versions, with a list of changes. Option=
s to customize emails for registration in management console. Nick will add=
to JIRA.
- Secondary storage providers: 4Science working on setting up support for=
another European provider, which also allows multipart upload. Andrea will=
provide an update on what they support. New kind of S3 storage that is not=
replicated has been introduced, is only in one data center and is cheaper,=
could be a good option to pair with another provider location. 4Science is=
looking into this. It is 25% less expensive than standard S3. =20
- Some TDL customers want to be able to create spaces and push content to=
secondary providers. Issue comes up often with one client. Currently it is=
set up for replication only to simplify the workflow. REST API can be used=
to create spaces on the secondary provider if they are an admin. Taken out=
of UI. Bit checking is not being done on Glacier, so that is why there is =
not a Glacier only option. TDL does have customers with Glacier as a primar=
y and it has caused issues.
- Current way that we limit secondary providers isn't ideal. Something to=
discuss on the next call, how users want to engage with secondary provider=
s. DuraSpace has heard questions from prospects but not from current custom=
ers; current customers are focused on secondary storage as a backup. Using =
Glacier in other regions and as a secondary store.
- Providers worth considering, example: O=
racle supports full API but have not done any testing.
- TDL and 4Science experience with use and implementation of DuraCloud: i=
mportant to discuss on our next call.
Actions
- Nichola=
s Woodward to add TDL operational needs to JIRA=
(more informative error handling, better sync tool tooltips, options t=
o customize emails for registration in management console, etc)
------=_Part_29281_1184517969.1711672195640--