NLnetLabs
Inode limit/RPKI of limited AS
Extracted from doc:
Inode Usage
Please keep in mind that the RPKI consists of a great number of small files. As a result, Routinator will use a large amount of inodes. You should accommodate for at least two million inodes. This will give you ample margin for the RPKI repositories to grow over time, as adoption increases.
Then for me it's not Lightweight. Any way to filter for only limited list of AS? Because in my case I plan have just need < 200 AS RPKI info, very small IXP. Only your software don't allow me use light hardware (ARM with uSD)
I’m not sure filtering for certain ASNs makes much sense – ROAs provide information for prefixes. Removing ROAs with a certain prefix means you end making all prefixes “unknown” that don’t have any of your specified ASNs, removing protection for them. In any case, we’d still need to download the full data to find the objects for your ASNs, so this doesn’t really help you limit the size of the data set.
Note that you can create a small file system with a large inode size – this requirement doesn’t mean you need a giant disk. Potentially reliability issue aside, something like a 32 Gig SD card should be totally sufficient.
Finally, with Routinator 0.14.0, we don’t really need that many inodes in normal operations any more. However, if a large repository fails to download via RRDP and falls back to rsync, lots of small files will appear again and you do may run out of inodes. For this reason, we left the recommendation in place.
we’d still need to download the full data to find the objects for your ASNs
No way to just download the minimal data ondemand? RAM only + ondemand + stale entry when no internet will be perfect for me.
There are a number of places that publish validated datasets in various formats. For instance, the RIPE NCC is running a Routinator instance and you can fetch its VRP dataset as a CSV here: https://rpki-validator.ripe.net/csv