Activities review
- [name=Robyn]
- Wrapping up poster following translations
- Draft PR for GHCR open - finishing it up after poster
- [name=Rushiraj]
- Extending viz-workflow for changes from latest release (issu#69)
- Documentation for viz-workflow (issue#62)
- [name=Trey]
- Merged ogdc-runner PRs allowing workflow config spec in recipes (see: #98)
- Wrapping up PR fixing bug w/ viz-workflow when a remote recipe repository is used (see issue #101)
Discussion: plans and priorities
- Wrapup production release of ogdc-helm
- Setup meeting w/ Matthew B.
- Can usually be async - just message Matthew.
- Document release workflow for future versions
- Portal updates: prepare in advance of GSW (Nov. 7)
- Data publication: publish to a web-accessible location (e.g,. DataONE)
- ogdc-runner web service: setup a web service that sits in front of Argo and acts as the public-facing API.
- Deployed with helm alongside argo/minio, so storage specifics do not need to be known in advance. Relevant discussion: (TODO)
- Other benefits:
- We gain more isolation of cluster resources/permissions
- Relatively straightforward auth (?)
- https://github.com/QGreenland-Net/ogdc-helm/issues/25 - can setup auth in front of web service and not have to do that ^
- Service can track recipe outputs and serve output data that isn’t published to DataONE
- We have been anticipating this for a while. Our high-level architecture diagram shows this.
- Use data one Hash Store for data inputs/ outputs
- we have some stories for this and it sort of is the other end of publishing to a web-accessible location - working towards end to end implementation
- We think this makes sense to tackle after we complete work on publishing outputs.
- Planning for researcher workshop / hackathon.
- Not an immediate priority, but we should be thinking about this for year 3!