-
Notifications
You must be signed in to change notification settings - Fork 0
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
Unused home directory cleanup feature #32
Comments
yuvipanda
referenced
this issue
in yuvipanda/pilot-hubs
Jan 2, 2024
Only enables this for openscapes, which is using it as described in https://github.com/2i2c-org/infrastructure/issues/3562.
Yet another request for this, now from Smithsonian: https://2i2c.freshdesk.com/a/tickets/1359 |
ateucher
added a commit
to NASA-Openscapes/2i2cAccessPolicies
that referenced
this issue
May 18, 2024
Original at: 2i2c-org/features#32 (comment) Co-authored-by: Yuvi Panda <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While helping openscapes folks cleanup their user access list (2i2c-org/infrastructure#3240), I also helped them cleanup unused home directories. This isn't a service 2i2c offers to users yet, but I wanted to open this to track work to be done here long term - otherwise it just increases costs monotonically for our users (2i2c-org/infrastructure#3240 (comment)). This issue mostly currently tracks the one-off job I helped do for them, but needs more work to be rolled out sustainably to others.
I wrote an impromptu script that helped us archive home directories of a list of users given in the commandline to S3.
python script
It has some additional features to make sure we don't accidentally delete user home directories before they are properly archived.
There's currently no automatic way for folks to retrieve their home directories post archival, nor guidance about home directory policies that can be given to users before they sign up. For openscapes, their admins have access to s3 buckets via the web console and have taken on the role of sending users their home directories if so desired. 2i2c engineers can not be the ones doing this manual retrieval, however.
An s3 bucket that would move objects to archival status 3 days after was created, and this bucket was used to hold the archive. This was preferred as it would allow us to experiment with creating / deleting archives without incurring the additional cost that comes from doing create / delete operations on archival class objects (see pricing per GET / POST requests for standard vs Glacier Instant retrieval in https://aws.amazon.com/s3/pricing/).
The text was updated successfully, but these errors were encountered: