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

Move our archival storage bucket to 'archive' class #3389

Closed
yuvipanda opened this issue May 19, 2022 · 4 comments
Closed

Move our archival storage bucket to 'archive' class #3389

yuvipanda opened this issue May 19, 2022 · 4 comments
Assignees
Labels

Comments

@yuvipanda
Copy link
Contributor

Our storage archiver now moves home directories into this GCS bucket.

It's currently set to 'standard' storage class, but that offers us a level of performance that we just do not need. These are barely accessed, and we keep them for a while now. If we switch them to the 'archive' class, it drops our storage pricing by about 94%
(see https://cloud.google.com/storage/pricing).

So let's do that?

@balajialg
Copy link
Contributor

balajialg commented May 20, 2022

@yuvipanda Looks like a good optimization from a cost perspective and I am in! Thanks for thinking about this :)

@felder Should chime in with his verdict here as this affects his day-to-day to a certain extent!

@felder
Copy link
Contributor

felder commented May 20, 2022

@yuvipanda like a good idea. How about I setup a lifecycle rule to transition all objects in the bucket to the archive storage class after 30 days? That way if necessary I have a window to remove them before we end up with a 365 day commitment.

@yuvipanda
Copy link
Contributor Author

@felder great idea! Lmk if I can help :)

@felder
Copy link
Contributor

felder commented Jun 6, 2022

Did a quick test to make sure signed urls could be created and fetched if an object was in archive storage class.

They can be.

Setup a bucket lifecycle rule to transition all objects over 30 days old to the archive storage class.

@felder felder self-assigned this Jun 6, 2022
@felder felder added the support label Jun 6, 2022
@felder felder closed this as completed Jun 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants