Opened 17 months ago

Last modified 10 months ago

#25925 assigned defect

bwauth improvements (ex-parent ticket for SoP planned tasks)

Reported by: juga Owned by: juga
Priority: Medium Milestone: sbws: unspecified
Component: Core Tor/sbws Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description


Child Tickets

TicketStatusOwnerSummaryComponent
#3723closedReport version of bwscanners in votesCore Tor/Tor
#7177newUnderstand how accurate the bandwidth authority estimates areCore Tor/sbws
#8494closedjugaDocument MaxAdvertisedBandwidth in the bandwidth list specCore Tor/Tor
#21377closedjugaDirAuths should expose bwauth bandwidth filesCore Tor/Tor
#24104closedjugaDelay descriptor bandwidth reporting on established relaysCore Tor/Tor
#25947closedjugaCreate unit test for dirserv_read_measured_bandwidthsCore Tor/Tor
#25960closedjugaAllow additional header lines in bandwidth measurements documentsCore Tor/Tor
#26004closedAllow Tor to accept node_id at the end of a bandwidth file lineCore Tor/Tor
#26007closedteorStop logging stack contents when reading a zero-length bandwidth fileCore Tor/Tor
#26155closedteorBandwidth file Timestamp is the latest scanner result, not the file creation timeCore Tor/Tor
#26200closedBandwidth List format specification: add KeyValues counting errors in Bandwidth LinesCore Tor/Tor
#26223closednickmAllow longer bandwidth lines in bandwidth filesCore Tor/Tor
#26692closedsbws must not overwrite the bandwidth file, to avoid race conditionsCore Tor/sbws
#26796closedteorUse a consistent name for the bandwidth-file-headers lineCore Tor/Tor
#26848closedjugaCreate Debian package for sbwsCore Tor/sbws
#26937closedjugasbws: Warn when there is not enough disk spaceCore Tor/sbws
#27047newAuthorities should keep recent consensuses, votes, and bandwidth filesCore Tor/Tor
#27107closedTransition plan from Torflow to sbwsCore Tor/sbws
#28403closedtomLink to bandwidth files from Consensus HealthMetrics/Consensus Health
#28547closedjugaMonitor relays that are not measured by each sbws instanceCore Tor/sbws
#28572closedteorsbws should check the minimum number of measurements after excluding measurementsCore Tor/sbws
#28585closedjugaRelease 1.0.3Core Tor/sbws
#28599closedbandwidth-file-spec.txt: bandwidth-avg is not calculated from any bandwidth burst optionCore Tor/Tor
#28600closedRefactor: store the minimum of the bandwidth values from the consenus in the resultsCore Tor/sbws
#28602closedjugaThe call to generate the bw file is passing an old argumentCore Tor/sbws
#28639closedAfter several days, most of the circuits timeoutCore Tor/sbws

Change History (9)

comment:1 Changed 17 months ago by teor

Hi juga, please make the other trac tickets in your list of work into children of this task.
You can make a ticket into a child of this ticket by setting its Parent ID to "#25925".

comment:2 Changed 17 months ago by juga

I did it, but without "#", fixed.
That has changed old parents of some bugs.

comment:3 Changed 13 months ago by nickm

Component: Core Tor/TorCore Tor/sbws

comment:4 Changed 13 months ago by juga

Now that SoP finished, should this ticket be closed?, should the remaining opened tickets be made:

  • childs of a new parent ticket (PF?)
  • assigned a component (what about having a tor-bwauth component and not just keyword?)
  • tagged as tor-bwauth?
  • leave orphan?

comment:5 in reply to:  4 Changed 12 months ago by teor

Replying to juga:

Now that SoP finished, should this ticket be closed?, should the remaining opened tickets be made:

  • childs of a new parent ticket (PF?)

Some of these tasks are important, and others are not.

Let's:

  • work out which tasks we need to do
  • find out if any tasks are missing
  • put the tasks we need to do under a new parent ticket
  • assigned a component (what about having a tor-bwauth component and not just keyword?)

In Core Tor, we have a component for each piece of software. (The DirAuth component is for directory authority config changes.)

"tor-bwauth" is not a component, it's a group of related tasks in different components. These tasks are already assigned to Tor, sbws, Torflow, and Chutney.

  • tagged as tor-bwauth?

Good idea!
We can also tag them with bwauth-sop-2018 so we know which tasks used to be under this ticket.

  • leave orphan?

If a task is not important, it can be an orphan.

comment:6 Changed 10 months ago by juga

Summary: Bandwidth scanner parent ticket for SoP planned tasksbwauth improvements (ex-parent ticket for SoP planned tasks)

Change title to reflect current situation.
Not creating a new parent or changing children at the moment.

comment:7 Changed 10 months ago by teor

Milestone: sbws: unspecified

comment:8 Changed 10 months ago by juga

I think this parent would be more useful to track only Core-Tor tickets, since sbws can be track by component.
If you agree, i'll remove the children that are sbws and leave only the Core-Tor ones.

comment:9 in reply to:  8 Changed 10 months ago by teor

Replying to juga:

I think this parent would be more useful to track only Core-Tor tickets, since sbws can be track by component.
If you agree, i'll remove the children that are sbws and leave only the Core-Tor ones.

Ok, that works.

Or you can just use a keyword to track Core Tor tickets. Whatever is easier for you.

Note: See TracTickets for help on using tickets.