Opened 15 months ago

Closed 7 months ago

#27107 closed defect (implemented)

Transition plan from Torflow to sbws

Reported by: juga Owned by:
Priority: Medium Milestone: sbws: unspecified
Component: Core Tor/sbws Version:
Severity: Normal Keywords: sbws-1.0-must-moved-20181128, sbws-11x-final-removed-20180318
Cc: Actual Points:
Parent ID: #25925 Points:
Reviewer: Sponsor:

Description (last modified by juga)

Ticket for the tasks related to get sbws in production.
These would include work we have been already doing, but probably we should need to add more tasks:

  1. Get sbws in Debian (#26848)
  2. Check that the bandwidth files results are similar to Torflow: We have being doing this in https://github.com/pastly/simple-bw-scanner/issues/182, though is growing. So far we checked:
    • sbws raw results compared to torflow: shape is quite different
    • sbws raw results compared to sbws scaled: big relays get bigger bw, but shape still different from torflow
    • sbws raw results compared to sbws raw results having a bigger time for downloading: they're similar
    • sbws raw results compared to sbws raw results resting the rtt from the dowload time: they're similar
    • implement parsing Torflow raw files
    • sbws raw results compared to Torflow results: they are similar, so it is the scaling method which makes results different
  3. i'd create child tickets for the WIP
    • implement torflow scaling
    • check sbws using torflow scaling compare to Torflow
    • change specification
    • ...
  4. Get one bwauth to run sbws
  5. Archive bw files (#21378)
  6. Compare Tor bw files from bwauths running Torflow and from the one running sbws
  7. ...

Edit:

  • formatting

Child Tickets

TicketStatusOwnerSummaryComponent
#27108closedjugaImplement torflow's scaling method in sbwsCore Tor/sbws
#27336closedjugaDoes sbws need a node cap?Core Tor/sbws
#27339closedWork out a policy for resolving differences between torflow and sbwsCore Tor/sbws
#27690closedjugaUpdate bandwidth-file-spec with scaling methodsCore Tor/Tor
#27692closedjugaUpdate documentation with torflow scaling and other changesCore Tor/sbws
#27705closedjugaWhat to change on stem release 1.7Core Tor/sbws
#27976closedUse torflow scaling/aggregation option as the defaultCore Tor/sbws
#28085closedjugaUpdate key/values in the bandwidth file specCore Tor/Tor
#28224closedMonitor dirauth running sbws in productionCore Tor/sbws

Change History (7)

comment:1 Changed 15 months ago by juga

Component: - Select a componentCore Tor/sbws
Description: modified (diff)

comment:2 Changed 11 months ago by teor

Keywords: sbws-1.0-must-moved-20181128 added
Milestone: sbws 1.0 (MVP must)sbws 1.0.4

Moving all sbws 1.0 must planning and feature tickets to 1.0.4.

comment:3 Changed 11 months ago by teor

Milestone: sbws 1.0.4sbws 1.1

Milestone renamed

comment:4 Changed 11 months ago by teor

Milestone: sbws 1.1sbws: 1.1.x

Milestone renamed

comment:5 Changed 11 months ago by teor

Milestone: sbws: 1.1.xsbws: 1.1.x-final

Milestone renamed

comment:6 Changed 7 months ago by juga

Keywords: sbws-11x-final-removed-20180318 added
Milestone: sbws: 1.1.x-finalsbws: unspecified

Removing from 1.1.x-final because the 2 remaining open tickets are removed from 1.1.x-final

comment:7 Changed 7 months ago by juga

Resolution: implemented
Status: newclosed

All children are closed.
We can open new tickets when we'll change the torflow scaling algorithm.

Note: See TracTickets for help on using tickets.