-
Notifications
You must be signed in to change notification settings - Fork 65
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
[Platform Initiative] Implement per-user home directory quotas #5010
Comments
@Gman0909 @yuvipanda Do you have suggestions/preferences for which community to be the other one migrated with VEDA? And does a conversation with them need to happen? |
I'm actually thinking it could be AWI-CIROH, because I saw a message from them about wanting quotas. Let's confirm with @jmunroe. |
Since our initial rollout was in AWS, I spoke instead to NMFS-Openscapes and Cryocloud. They're both very happy to be the next. Since NMFS-Openscapes is much newer, let's start there. |
@sunu is currently working on the following two epics:
The next tasks he'll be tackling are:
I am tackling the migration effort, following Yuvi's suggestion above, starting with #5066, then #5067, before returning to #4835 |
@sunu has made great progress on #5061 and #5062 and I feel good that we'll close out #5002 and #5004 before the end of the year. @yuvipanda and I agreed that only ONE of either #4835 or #5067 is required to close this epic, and CryoCloud will be ready to go during the next sprint. That just leaves #5187 which Yuvi and I agreed we'll tackle in the new year |
Love that, thanks @sgibson91 |
This issue tracks rolling out 'per user home directory quotas' as an initiative within the product & services team.
Team
External Links
Definition of Done
The text was updated successfully, but these errors were encountered: