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

modify EU storage #2951

Merged
merged 1 commit into from
Feb 20, 2025
Merged

modify EU storage #2951

merged 1 commit into from
Feb 20, 2025

Conversation

pavanvidem
Copy link
Member

@pavanvidem pavanvidem commented Feb 20, 2025

The article reads well and super clear. But I have a few concerns on the terminology used in unshared storage which led to confusion between storage and quota.

  • The unshared storage is not really a separate storage, it is part of regular long-term storage. On the contrary, the short-term, user-owned are real storages. On the storage dashboard, does user see unshared storage as a separate entity?
  • Is this statement true? "Data on this storage cannot be used for public datasets"
  • Should we add storage of sensitive data as a usecase for unshared storage?

As I see, there 3 quota classes, long-term, short-term and user-owned. There are sharable and unsharable storage (or space) of long-term user quota.

@bgruening
Copy link
Member

The article reads well and super clear. But I have a few concerns on the terminology used in unshared storage which led to confusion between storage and quota.

* The unshared storage is not really a separate storage, it is part of regular long-term storage. On the contrary, the short-term, user-owned are real storages. On the storage dashboard, does user see unshared storage as a separate entity?

Technically it will be a separate storage. An additional S3 bucket. But the quota spans two storages.

* Is this statement true? "Data on this storage cannot be used for public datasets"

Yes, I think so.

* Should we add storage of sensitive data as a usecase for unshared storage?

It is meant for this use-case - maybe in the future. But we should not advertise it as long as our terms do not allow sensitive data.

As I see, there 3 quota classes, long-term, short-term and user-owned. There are sharable and unsharable storage (or space) of long-term user quota.

Its really 4 options. unshareable is a separate bucket. We probably want to safeguard those private data in a special way and not mix it with the other data in long-term storage.

@pavanvidem
Copy link
Member Author

Technically it will be a separate storage. An additional S3 bucket. But the quota spans two storages.

Then I misunderstood it. All good.

@bgruening bgruening merged commit b0349e4 into galaxyproject:master Feb 20, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants