Closed
Bug 1222011
Opened 9 years ago
Closed 9 years ago
Need Public URL to direct download of Nexus 4 & 5 builds on Participation Hub
Categories
(Participation Infrastructure :: MCWS, task)
Participation Infrastructure
MCWS
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jgong, Assigned: jonasfj)
References
Details
User Story
Need two public facing URL for Participation Hub essential creation of 2 index links. A) Use the index link Just use the links for the index or the queue directly. It has some redirects, a bit of latency. But if your load is very high this could be bad. I have load-tested most of these things to 100 req/s per dyno, we run a few of these... Our nodes only do redirects, so most likely they'll handle the load. How many downloads do you really expect? (notice that size of the download is irrelevant as we redirect to a CDN for the actual heavy lifting)
Need two Public URL to direct download of Nexus 4 & 5 builds on Participation Hub
|
Reporter | |
Updated•9 years ago
|
Assignee: nobody → jopsen
|
|
Reporter | |
Updated•9 years ago
|
User Story: (updated)
|
|
Reporter | |
Updated•9 years ago
|
User Story: (updated)
|
||
Comment 1•9 years ago
|
||
Hey - is this something MOC is taking care of, or do you need Community Ops' help here?
|
|
Reporter | |
Comment 2•9 years ago
|
||
(In reply to Tanner Filip [:tanner] from comment #1) > Hey - is this something MOC is taking care of, or do you need Community Ops' > help here? Jonas is already taking care of this. Jean
|
|
Reporter | |
Comment 3•9 years ago
|
||
We will be using below the index link on the Website for Nexus 5 https://index.taskcluster.net/v1/task/gecko.v1.mozilla-central.latest.linux.nexus-5-user.opt/artifacts/public/build/nexus-5-l.zip Nexus 4 https://index.taskcluster.net/v1/task/gecko.v1.mozilla-central.latest.linux.nexus-4-kk-user.opt/artifacts/public/build/nexus-4-kk.zip
|
Assignee | |
Comment 4•9 years ago
|
||
Just use the pattern: https://index.taskcluster.net/v1/task/<namespace>/artifacts/<name> That was the whole proposal. Nothing special is needed as we don't expect these URLs to be hit with 100s of requests per second... We currently handles spikes with 5-7000 req/min, and phone builds are unlikely to have spikes higher than that... Note: all heavy lifting is redirected to a CDN, we only do table storage lookups and redirects in our servers.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
|
||
Comment 5•5 years ago
|
||
Bulk move of bugs
Component: Community IT: Others → MCWS
Product: Infrastructure & Operations → Participation Infrastructure
You need to log in
before you can comment on or make changes to this bug.
Description
•