The code is already designed around an externally-stored probelist. I.e. probelist code has the concept of reading and updating /24s as if they are stored in an external source (e.g. redis).
This work would involve:
- extending
trinarkular_probelist to actually support an external store (e.g. redis or ardb or even maybe postgres) [1wk]
- Implementing a mechanism to automatically generate new probelists [1day]
- update metadata dbs (geo/as/pfx)
- update history file
- Implementing a system to update (distributed) stores with new probelists. [<1wk]
The code is already designed around an externally-stored probelist. I.e. probelist code has the concept of reading and updating /24s as if they are stored in an external source (e.g. redis).
This work would involve:
trinarkular_probelistto actually support an external store (e.g. redis or ardb or even maybe postgres) [1wk]