Skip to content
This repository has been archived by the owner on Mar 2, 2019. It is now read-only.

Implement basic ISP integration #24

Open
micolous opened this issue May 7, 2012 · 4 comments
Open

Implement basic ISP integration #24

micolous opened this issue May 7, 2012 · 4 comments

Comments

@micolous
Copy link
Owner

micolous commented May 7, 2012

Implement a new ProviderPeriod model, which has the ISP's billing period specified in it. Provider periods may overlap (unlike Events), and will encompass the area of many events.

The purpose of this is it will aggregate many EventAttendances for the user, and show a combined total usage. It will also allow easier correlation of usage with data that the ISP provides, and identify potential irregularities (such as use of internet not through tollgate, or accounting errors in tollgate or the ISP's systems).

There should also be a pluggable API allowing you to import ProviderPeriods from the ISP's data, and act as a meter of what the ISP thinks you've done.

@kleinig
Copy link
Contributor

kleinig commented May 7, 2012

Here is the Adam Internet api info
http://whirlpool.net.au/wiki/adamfaq_api

API XML I receive with critical info removed :P
http://pastebin.com/N98gx7cJ

@micolous
Copy link
Owner Author

micolous commented May 8, 2012

This implements many ISP usage meters:
http://netusage.iau5.com/

@twoolie
Copy link

twoolie commented Jul 24, 2012

what about unmetered usage? would that mess with the totals?

@micolous
Copy link
Owner Author

Unmetered usage is never counted anywhere in the system at this time, so if the list of unmetered content and metered content is different between you and the ISP, then it would not match up.

For example, you may have some non-Internet WAN links that you want to meter, or you do not wish to unmeter all content that the ISP does (for example, to prevent indiscriminate leeching of file mirrors on a highly contested link).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants