#7661 GeoIP
Opened 2 months ago by codeblock. Modified 2 months ago

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:

  • Is there any reason geoip.fp.o can't live in OpenShift?
  • Are we tied to Python here? This seems like a low risk enough service (it's already been out of date for a few months anyway) that maybe I could get away with playing with a different language here? Especially if we can move it to OpenShift.
  • 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?

/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.

Login to comment on this ticket.

Metadata