Tester worker

[rgaudin]

Tester worker is the independent speedtest image/container that does the actual speedtest.

It's input is an URL to test and returns test results as JSON

{
  "started_on": "ISO formatted datetime",
  "status": "success|error",
  "error": "Error reason",
  "ip": "Current Public IP",
  "asn": "Current Public IP AS",
  "isp": "Current Public IP ISP",
  "country": "Current Public IP Country",
  "location": "Current Public IP City",
  "latency": "Average Ping result to netloc of URL",
  "size": "Size in bytes of downloaded URL",
  "duration": "Duration in seconds (micro?) of the download",
  "speed": "Speed in bytes per second of the download"
}

I'm not sure about IP-related data. We don't want to store just the IP as associated data might change over time and we want the DB to have all meaningful data. Still we could:

• query an online service (simplest but prone to failures or denial)
• embedded a free IP database (need to check if we can get it all in free sets) but it's more work and needs periodic updates
• submit just the IP and have the backend do what's on the previous line

[rgaudin]

It is important that the downloads are made using a custom User-Agent that would include speedtester/robot (see #3)