DirAuths should expose bwauth bandwidth files

Currently, DirAuths that vote on bwauth files do not expose the raw voting file they used. This data would be good to archive for debugging and transparency purposes.

changed milestone to %Tor: 0.4.0.x-final

added 035-removed-20180711 040-backport 040-roadmap-proposed actualpoints::0.3 authority-test-done component::core tor/tor metrics-needs milestone::Tor: 0.4.0.x-final owner::juga parent::25925 points::0.2 priority::high resolution::fixed reviewer::ahf severity::normal status::closed tor-bwauth tor-dirauth type::enhancement labels

The ticket blocks archiving the data in collector, #21378 (moved)

Trac:
Keywords: N/A deleted, tor-dirauth metrics added
Milestone: N/A to Tor: unspecified

Trac:
Priority: Low to High

This is now fixed in sbws, though is still not being use by any DirAuth.

It is not planned to add this to Torflow.

Trac:
Keywords: tor-dirauth metrics deleted, tor-dirauth metrics tor-bwauth added

Trac:
Cc: N/A to teor

Replying to juga:

This is now fixed in sbws, though is still not being use by any DirAuth.

It is not planned to add this to Torflow.

This ticket is about archiving exposing the entire v3bw file, not just the headers.

Can you explain how this is fixed in sbws?

Trac:
Summary: DirAuths should expose bwauth votes to DirAuths should expose bwauth bandwidth files

My mistake, didn't re-read the title of the ticket. No, sbws does not fix this.

Changes to dir-spec commented https://trac.torproject.org/projects/tor/ticket/21378#comment:7 implemented in my branch. Please let me know if i should create a different ticket for the spec.

Edit: correct url to the comment

Trac:
Status: new to needs_review

Replying to juga:

Changes to dir-spec commented https://trac.torproject.org/projects/tor/ticket/21378#comment:7 implemented in my branch.

I think the pull request is: https://github.com/torproject/torspec/pull/21

In future, please link to the branch or pull request, so I know which one you want me to review.

Please let me know if i should create a different ticket for the spec.

Yes, please open a different ticket, otherwise this ticket will close when we merge the spec.

Please see my comments on the pull request.

Trac:
Status: needs_review to needs_revision
Milestone: Tor: unspecified to Tor: 0.3.5.x-final

Created #26694 (moved) for the spec changes.

Trac:
Parent: N/A to #25925 (moved)

Changing status since the ticket for the spec is #26694 (moved)

Trac:
Owner: N/A to juga
Status: needs_revision to accepted

These tickets are being triaged out of 0.3.5. The ones marked "035-roadmap-proposed" may return.

Trac:
Milestone: Tor: 0.3.5.x-final to Tor: unspecified
Keywords: tor-dirauth metrics tor-bwauth deleted, tor-dirauth, tor-bwauth, 035-removed-20180711, metrics added

We would like to implement this ticket in 0.3.5, but we want a working bandwidth scanner first.

Trac:
Keywords: N/A deleted, 035-roadmap-proposed added

The refactor in #26797 (moved) will involve storing a copy of the bandwidth file in RAM or on disk, so let's do it first.

0.3.5 is closed to new features, moving to 0.3.6 proposed.

Trac:
Keywords: 035-roadmap-proposed deleted, 036-roadmap-proposed added