wishlist about ipasn-history HOT 7 OPEN

Just a few notes on the wish list (based on the current status in the dev branch):

• UI: there will a a swagger interface, but nothing else, this interface is meant to me used by a tool (such as BGP Ranking)
• huge refactor and cleanup is ongoing as alex said, with deps upgrage, use of flask-restx, requires python 3.8...
• data feeds: there will be differences, bit this has to be investigated (currently, caida and RIPE rrc00 are imported)
• The Python API is a standalone project, and will be on PyPi (https://github.com/D4-project/pyipasnhistory)
• kvrocks replaces ardb

Stream ready/enricher, not sure what you mean, but I'm not sure it is something possible with the current architecture. IPASN HIstory is meant for fast lookup but in order to do that efficiently, we must have a complete view of all the routes as a specific time. If you have BGP table available you want to export in the same format as what RIPE is doing, it is possible to add a module, but just adding updates isn't an option, as the architecture requires to have complete dumps at a specific time. An option is to load dumps every hour, but that will increase the resources needed quite a bit.

from ipasn-history.

Thanks for the list. For the replacement, it's kvrocks. I'm using it with hashlookup-server and it's working really well on SSD.

from ipasn-history.

New WiP on https://github.com/D4-project/IPASN-History/commits/dev including the move to kvrocks, OpenAPI interface and UI.

from ipasn-history.

v2.0 released, with the relevant python module (https://pypi.org/project/pyipasnhistory/)

from ipasn-history.

installing... :)

from ipasn-history.

feel free to update the doc, it's definitely not complete :]

from ipasn-history.

Added some items to the wishlist so that I don't forget them myself :) Will take a look if I manage to send a PR for those.

from ipasn-history.