search

Hubs-Foundation / turkey-portal

Mozilla Public License 2.0
0 stars 2 forks source link

Content Storage Limit Not Updating / No Method to Delete Assets #327

Open mikemorran opened 1 year ago

mikemorran commented 1 year ago

@bryanenders @nickgrato @robinkwilson @nikk15 We continue to receive reports that EA subscribers cannot reduce their content storage counter. I met with a user today who walked through the process of setting an asset's state to "removed" in the admin panel and deleting assets in spoke's asset manager, waiting 5-10 minutes, and still seeing no change in their content storage limit. In spoke, the user only had about 12 small media assets, but was still over the 2Gb limit on the dashboard.

It seems that there is either no true method to delete assets from the database via the Admin Panel or Spoke, or that the storage limit is not updating properly.

tanfarming commented 1 year ago

oh this is worse than it looks -- turkey instance's storage is shared and auto scales, leave it unchecked it will eventually blow up our infra budget Brain did a write up on this https://mozilla-hub.atlassian.net/wiki/spaces/Hubs/pages/14517613/PRD+reticulum+file+storage the cleanup/delete of files is a reticulum feature, I thought this was done somehow @bryanenders you are the owner of reticulum codebase, can you prioritize this? reticulum needs to be able to "garbage collect" junk files

bryanenders commented 1 year ago

@tanfarming With the formation of the Subscription Team, I’m no longer the owner of Reticulum. My recommendation would be to capture what needs to happen and put it to John and Jacob to be assigned to either Engine or Subscription Team and prioritized.

tanfarming commented 1 year ago

@tanfarming With the formation of the Subscription Team, I’m no longer the owner of Reticulum. My recommendation would be to capture what needs to happen and put it to John and Jacob to be assigned to either Engine or Subscription Team and prioritized.

oh sry I thought you still own reticulum

@johnshaughnessy @Jacob-Ervin so it seems that we have problem here -- nobody owns reticulum and high priority bugs (like this one) and security issues are stacking up, i can own it (as in dig in and fix the issue) i have to, but it will be a "best effort" tho, since i'm already owning too many codebases, also doesn't help with our "bus number" problem

tanfarming commented 1 year ago

finally updated the "essential services" section for turkey's system design doc so we can track codebase ownership there reticulum will definitely need an owner, it's our main security issue generator