Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Epic] Automatic blob storage access from notebook servers #194

Closed
6 tasks done
brendangadd opened this issue Aug 13, 2020 · 4 comments
Closed
6 tasks done

[Epic] Automatic blob storage access from notebook servers #194

brendangadd opened this issue Aug 13, 2020 · 4 comments
Labels
area/engineering Requires attention from engineering: focus on foundational components or platform DevOps component/jupyter Kubeflow notebooks and associated container images component/kubeflow Kubeflow Related component/remote-desktop component/storage Persistence related (e.g. Minio, cloud, or user storage) kind/feature New feature or request priority/soon

Comments

@brendangadd
Copy link
Contributor

brendangadd commented Aug 13, 2020

As a user, I want easy access to all of my personal blob storage options directly from my notebook server without doing any special configuration.

  • I want to work with blob storage similarly to how I work with other types of storage.
  • I want to share storage with other project members; I don't want to give them access to my personal resources to do so.
  • I want easy access to the data from different notebook servers.
  • I want easy access to the data from different software within notebook servers.

Tasks

@zachomedia
Copy link

Fuse injection completed with https://github.com/StatCan/boathouse

@brendangadd
Copy link
Contributor Author

I took the Pachyderm MinIO tenant removal out of scope of this epic as that tenant is not being auto-mounted into notebook servers. We can do that cleanup using other issues.

@blairdrummond
Copy link
Contributor

This is pretty much done isn't it? Or maybe continue it for Boathouse DataLake business

@brendangadd
Copy link
Contributor Author

@blairdrummond Yep, let's consider this done and do enhancements post-epic. These features so far are epic enough on their own. :P

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/engineering Requires attention from engineering: focus on foundational components or platform DevOps component/jupyter Kubeflow notebooks and associated container images component/kubeflow Kubeflow Related component/remote-desktop component/storage Persistence related (e.g. Minio, cloud, or user storage) kind/feature New feature or request priority/soon
Projects
None yet
Development

No branches or pull requests

3 participants