Hyrax Infrastructure Maintenance Steps - January 28, 2022

Owned by Juliet Hardesty
Last updated: Jan 28, 2022
2 min read

  • Attending: Tamsin Johnson, Daniel Pierce, Alexandra Dunn, Matthew Critchlow, Tao Zhao, Julie Hardesty

  • tamsin sharing steps for publishing hyrax packages as part of a release; making sure current Hyrax Maintenance Working Group folks have permissions to do this

  • folks need right permissions

  • all things published to ghcr (https://github.com/orgs/samvera/packages)

  • moved hyrax package to charts so it is now named charts/hyrax (wasn't showing in packages list initially but did show up - maybe a problem on the Github side?)

  • fcrepo and dassie images are published and publish base hyrax image; these instructions are for how to do this publish step

  • Daniel's fcrepo PR ready to test this - Daniel can't publish for fcrepo4 package (docker-fcrepo in samvera-labs)

  • names of packages should be redone to make organization clearer

  • Daniel can push to packages (granted access)

  • Samvera Admins group on Github should have admin access to all packages

  • Hyrax group will have write access

    • need to publish these 2 policies somewhere; Julie will do this somewhere on wiki and talk to Heather

  • settings on Github has place to recover missing packages that have been deleted in last 30 days

  • all packages really should be based on code that is in http://github.com/samvera (not samvera-labs, like docker-fcrepo - https://github.com/samvera-labs/docker-fcrepo)

  • READMEs on github are not policies but reflect current status of things (updating READMEs today while sharing instructions)

Hyrax Helm Chart

Dassie image

  • push process is similar to helm chart but without helm stuff

  • https://github.com/samvera/hyrax/blob/main/CONTAINERS.md

  • docker build and then docker tag commands

  • need token based on your user account (these tokens will time out!)

  • helm is not docker so these are different things and have different login requirements

  • release involves pushing new hyrax package and dassie package

  • new chart release not necessarily part of hyrax release; chart users can do that update if needed (Surfliner) - it is OK for chart to lag behind a little for Hyrax releases

  • need hyrax worker published as well (doesn't really happen now but would be good if it did)

  • Dockerfile shows all of the images that are built (hyrax-base, hyrax, hyrax-worker-base, hyrax-worker, hyrax-engine-dev, hyrax-engine-dev-worker)

  • could use 2 separate images for each release - base and worker images but isn't really happening this way

Follow-up/Actions

  • Daniel says IU is building image using Github Actions and it is working so this might be something that could be automated; HMWG can look at automation

  • unclear how Hyrax releases will go this year since HMWG might have people coming in and out

  • Julie follow up with Heather about where to host on wiki about policy decisions for publishing images