-
Notifications
You must be signed in to change notification settings - Fork 24
Add data retention policy #188
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
Conversation
Remove unnecessary (and unclosed paren
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is good for the starting point. After implemented/deployed we will see how it could be improved
doc/design/data-retention-policy.md
Outdated
- `nwb_cache` | ||
- Yarn Cache | ||
- `__pycache__` | ||
- pip cache |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In case user is still active -- I think it would be useful to report to the long running users, after reaching some threshold on any of those folders (e.g. 50MB) asking to clean them up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @asmacdo, should we add a separate point here about monitoring and reporting the quotas of cache directories for active users?
doc/design/data-retention-policy.md
Outdated
- large file list | ||
- summarized data retention policy | ||
- Notice number | ||
- request to cleanup |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
meanwhile it might be worth creating a simple data record schema to store those records as well so they could be reused by the tools to assemble higher level stats etc.
Co-authored-by: Yaroslav Halchenko <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, @asmacdo. This is great. A few suggestions are listed above.
Hi @asmacdo, please let me know when this is ready for review. And then we can update the DANDI Terms and Policies as needed. |
@asmacdo Continuing the discussion from Slack. As we work to ephemeral environments and given our current strategy of notifying users monthly, perhaps we should just have a policy that users with data totaling more than 10 GB would get an email notice? Proposed updated email template:
|
I will provide some suggestions based on the recent standup meeting where we decided to reset home directories after 45 days of not logging in to JuptyerHub. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @asmacdo, I have simplified the policy based on our team meeting this week. Please review suggestions and once you are ready we will need to update the DANDI Terms and Policies as needed.
Co-authored-by: Kabilar Gunalan <[email protected]>
Co-authored-by: Kabilar Gunalan <[email protected]>
This policy is inline with the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @asmacdo, just one more suggestion and then we can merge this document.
Co-authored-by: Kabilar Gunalan <[email protected]>
lgtm |
Heres a sketch of a possible data retention policy. Lets iron out what we want here prior to implementation.
Fixes: #182
from Yarik's initial thoughts : #177 (comment)