Closed
Bug 616555
Opened 14 years ago
Closed 14 years ago
Need a long-term storage solution for partner repacks
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: coop, Assigned: aravind)
Details
I'm not sure where partner repacks are living right now (kev's personal dir on people, maybe?), but we should have a dedicated place for them, be it a new server or subdir on an existing server. Reqs: * externally accessible so partners can retrieve their builds * accessible from build network so we can move builds there as part of the release process * not mirrored * big enough to accommodate current usage + growth (kev can hopefully provide more detail here)
Updated•14 years ago
|
Assignee: server-ops → aravind
Comment 1•14 years ago
|
||
Partner repacks are currently pushed to surf:/mnt/netapp/stage/releases.mozilla.com/archive/partners/<partnername>/<version>/<platform>/<locale>/ and https://partnerbuilds.mozilla.com/ points at .../archive/partners as the root. we should probably incorporate an aging system similar to what's on stage, although I'd probably suggest we archive major releases and decay point releases. some discussion on that needed, as a release is currently around 3.5GB.
Assignee | ||
Comment 2•14 years ago
|
||
Is there any IT action here? As kev pointed out, these builds now live on surf. How you want this aged out and trimmed is between kev and releng. Please let me know if I am wrong and there is some IT action.
Reporter | ||
Comment 3•14 years ago
|
||
(In reply to comment #2) > As kev pointed out, these builds now live on surf. How you want this aged out > and trimmed is between kev and releng. Please let me know if I am wrong and > there is some IT action. Filed Bug 622566 to cover the retention issue.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•