Hello everyone,
In our diskless infrastructure [0][1], we store all configurations
generated by the node inside the TPM's memory. These memories are very
limited (1-9k), but more than sufficient for saving the long-term keys
of the relays.
However, we have a problem: when rebooting the machines, we lose the
state file and, with it, the bandwidth measurements of the various
relays. This is quite annoying because upon reboot, our relays all start
up announcing 0 B/s, and it takes them days to regain their bandwidth.
Unfortunately, these files are too large to be stored in the TPM. We
would like to be able to generate the BWHistory configurations based on
some arbitrary values that we write into the node configurations, and
then let the node handle redoing the measurements upon reboot. However,
among all the configurations, it's not clear to us which ones are
important for our needs and which others we can leave empty.
In general, we would like to open a discussion, in view of Arti, about
the organization of the datadir. Currently, it's not very clear which
files are important for runtime, which are for persistence, etc. From
our point of view, it would be quite useful to be able to group
persistent data into just a few files, for example, one for all keys and
one for states/configurations.
Thank you,
g
[0]:
https://osservatorionessuno.org/blog/2025/05/patela-a-basement-full-of-amnesic-servers/
[1]:
https://osservatorionessuno.org/blog/2025/12/patela-v2-from-certificates-to-hardware/
_______________________________________________
tor-relays mailing list -- [email protected]
To unsubscribe send an email to [email protected]
