/
Samvera Tech Call 2021-04-14

Samvera Community Wiki

Samvera Tech Call 2021-04-14

Apr 14, 2021

Meeting Logistics:

Agenda

(meeting notes below)

 

Moderator: @tamsin johnson

Notetaker: @Juliet Hardesty

Attendees:

  • @tamsin johnson

  • Rob Kaufmann

  • Collin Brittle

  • Lynette Rayle

  • @Thomas Scherz

  • @Lea Ann Bradford

  • you!

 

Meeting Process

  1. Standing pre-agenda items (moderator)

    1. Welcome

      • "Welcome everyone, please add your name to the Attendees list.  If you are unable to do so, please let us know, and someone will add you. To any newcomers, Welcome, and please feel free to ask questions. Likewise for all attendees. We strive for an open and accessible conversation around Samvera technology."

    2. Call for new agenda items

  2. Follow Agenda from above (facilitated by moderator) and record notes in Notes section below (note taker)

  3. Standing post-agenda items (moderator)

    1. call for next moderator and note taker (moderator)

      1. Moderator:

      2. Notetaker:

    2. Samvera help follow-up (moderator)

    3. Pull request review (moderator)

  4. Post-meeting action (note taker)

    1. After call, this week's notetaker should create the agenda for the next call:

      1. Open template agenda titled "Samvera Tech Call 2021-xx-xx"

      2. Click on ... in the top right corner, and select copy.

      3. Popup will open for location. It should contain:

        1. Space: Samvera

        2. Parent page: 2021

      4. Select copy. New page should be created.

      5. Modify the title to remove "copy of", update it with the next date, add moderator, notetaker, and any carry-over agenda info. Click Publish. 

 

Notes

  • Samvera Community artifact registries?

    • https://github.com/samvera/hyrax/issues/4854

    • Publishing the Hyrax and FCRepo helm charts?

    • public registry is good boost - have used Docker Hub previously but rules have changed

    • Docker Hub has limited number of users who can manage images

    • CI pipelines are also being disrupted by Docker Hub when Docker Hub decides too many calls are being made

    • Helm charts are in same situation

    • Discussion

      • Docker Hub is using Samvera accounts

      • changes to Docker Hub policies are recent

      • can ask to be an open source org - LD4P is doing this but haven't heard back on request, not sure what that allows

        • seemed to be pretty quick form to fill out to make request

        • need to check in with @Heather Greer Klein about this before we do it

        • have to be sure we could actually sign on to whatever this form is asking so this might be more long-term than short-term solution, if it is even a possibility

      • is it viable to have a registry for CI/basic builds and then publish final image to Docker Hub? one account is bot account and other account is just for checking in if something breaks

        • might be possible but people that currently have access to Docker Hub would have to relinquish access or convert to service accounts for this use

        • this would be maintaining automated presence on Docker Hub and that is Samvera's only presence there

        • then there are more options for less public registries

      • discussion about moving off of Github - where is that right now?

        • WG working on this but might be waiting on some deliverables

      • Github might also be offering public registries

        • Tamsin needed auth token to pull the last time they tried but it's been a year or so

        • ended up on Docker Hub because of this

        • credential delivery for CI pipelines might be easier so this might be a possibility to use

        • Rob will look into what is possible with Github - can access public registries anonymously according to docs

      • Harbor might also be an option but has to be hosted

      • Harbor, Artifactory, and Chart Museum being tried at UCSD but Chart Museum for sure would not work

      • Harbor or something Samvera hosts might be a reasonable stop-gap but not long term

        • Samvera.cloud might be workable but it could end up being a large amount of S3 data (in terms of cost to store/maintain)

      • If Docker Hub is going away something else is likely to replace it, so that is something else to keep in mind

      • Decision: use Github registry

        • Publish Hyrax images to Github registry and then publish Helm chart to Github registry; automate both of those publishes

        • Helm chart is template for deploying to Kubernetes (cloud-based install)

        • Hyrax image is Docker build

    • Samvera Help follow-ups?

      • none

    • PR

    • next moderator: Lynette Rayle

    • next notetaker: Thomas Scherz