This serves as a discussion and tracking ticket for our GeoIP setup, since it is currently out of date with the new format provided by upstream.
Copying my comment from #6022:
@smooge I rewrote the geo-dns one, it's a different setup (but same source database I believe) than the rest. It looks like there's a new version of the geoip python library for the new format (https://github.com/maxmind/GeoIP2-python) -- but in the geo-dns script I parsed the data myself. Do all of these use the roles/geoip-city-wsgi/app/files/geoip-city.wsgi python script? Or is there more that I'm missing somewhere? I can work on rewriting it.
A few other thoughts:
/cc @kevin @smooge
I'm not sure how mirrormanager uses this yet. Does it call out to the WSGI through an actual HTTP request? Does it use the database directly itself?
MirrorManager has a copy of the database. It still uses the old format in the version we have deployed. Upstream MirrorManager already uses the new format, but it has not been deployed yet in Fedora's instance.
Metadata Update from @codeblock: - Issue priority set to: None (was: Next Meeting)
Metadata Update from @cverna: - Assignee reset
We are now two years later. Does this ticket still stand? Is there anything we need to/can do?
MirrorManager is using GeoIP2 and https://geoip.fedoraproject.org/ is also running with the new database.
@adrian is it ok to close this then?
Metadata Update from @smooge: - Issue tagged with: medium-gain, medium-trouble, ops, websites-general
It is not totally clear to me if this is only about geoip.fedoraproject.org and MirrorManager, but if it is only about those two things it can be closed.
It was for us. Thanks!
Metadata Update from @smooge: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Issue status updated to: Open (was: Closed)
Issue status updated to: Closed (was: Open) Issue close_status updated to: Fixed
Log in to comment on this ticket.