Closed
Bug 858114
Opened 12 years ago
Closed 5 years ago
Balrog should be able to filter on IP geolocation
Categories
(Release Engineering Graveyard :: Applications: Balrog (backend), defect, P3)
Release Engineering Graveyard
Applications: Balrog (backend)
x86
macOS
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: akeybl, Unassigned)
References
Details
(Whiteboard: [lang=python])
Balrog should be able to filter on IP geolocation, in case we ever have to do country-specific builds.
Updated•12 years ago
|
Whiteboard: [balrog]
Updated•11 years ago
|
Component: Release Engineering → Release Engineering: Automation (General)
Priority: -- → P3
QA Contact: catlee
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Comment 1•11 years ago
|
||
Not committing to do anything with this for now, but this looks like it would need some zeus tweaks to do anything. Currently, REMOTE_ADDR ends up being a zeus ip - it would have to forward along the real client ip for us to analyze it. If/when we do this we should also consult on webdev on how best to do this.
Comment 3•8 years ago
|
||
I spoke with Tarek about absearch today, and he told me that it makes the client do geolocation (using MLS or Google's location service), which takes a huge burden off the server.
Updated•8 years ago
|
Priority: P3 → P2
Whiteboard: [balrog] → [lang=python]
Updated•8 years ago
|
Priority: P2 → P3
Comment 4•5 years ago
|
||
This hasn't come up in a long time. We'll re-open as a Github Issue if it becomes relevant again.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
Updated•5 years ago
|
Product: Release Engineering → Release Engineering Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•