Matt Traudt
2018-04-26 10:58:28 UTC
Next meeting is 3 May 2018 at 0930 UTC.
http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-04-26-09.59.html
https://pad.riseup.net/p/6292yqhUOuHC (copy/pasted below)
Simple Bandwidth Scanner Meeting 25 April 2018
==============================================
This pad:
https://pad.riseup.net/p/6292yqhUOuHC
Previous week's notes:
https://lists.torproject.org/pipermail/tor-dev/2018-April/013084.html
Witty quote
- Unknown
Updates
===========================================
pastly:
last 7 days:
- sbws is now open source
https://github.com/pastly/simple-bw-scanner
https://sbws.readthedocs.io/en/latest/
- fix some bad bugs in 'sbws cleanup' command while writing tests for it
- integrate with Travis CI and automatically test against python 3.4,
3.5, and 3.6
- integrate with Read the Docs
- gather intel on the environments our users will be running sbws in
https://github.com/pastly/simple-bw-scanner/wiki/Information-regarding-sbws's-target-user-base
- did some research regarding library support for various distros.
incomplete
- remvoe filelock dependency
- brainstorm what I think a switch to http(s) should look like
https://sbws.readthedocs.io/en/latest/proposals/001-switchtohttp.html
next 7 days:
- start implementing the switch to http(s)
- verify sbws works with library versions that aren't the absolute
newest
misc notes section (not udpates)
juga's tor tickets:
https://trac.torproject.org/projects/tor/query?status=!closed&cc=%7Ejuga
juga:
Not sure which week was (since we changed from Monday to Thursday):
- review, comment on debug option not being used #85
- add logging conf to log to file/system #87
- review Periodically test reachability of helpers #93
- create issue Include file where to write ``generate`` results in
the config #91
suggest having options both in config and cli and cli overriding
conf
- report about problem with init and helpers #95
- create issue about adding software to header #96
- review using kilobytes #97, #98
Past week:
- fix conf issues locally and in testnet after "megacommit"
- more changes on the spec, after new teor review
https://github.com/torproject/torspec/pull/4/commits/54ef4d4355d2b475466bf11e80ad4bc57c7e7ec3
- create improve deployability #99
- create issue Debian package #101
- Work on issue software and sofware_version in v3bw files #112
- create issue Include coverage in travis #117
- create issue Include travis and coverage badges in README
enhancement #118
Next week:
- debug what tor does to solve
https://github.com/torproject/torspec/pull/4/#issuecomment-384555243
- review the software/version ticket according to results from
previous (https://github.com/pastly/simple-bw-scanner/issues/96)
- review spec according to results from previous
- add a default output file for generate that can be overriden by
cli args (https://github.com/pastly/simple-bw-scanner/issues/91)
- improve deployability, this should also help to update instances
running in testnet (https://github.com/pastly/simple-bw-scanner/issues/99)
- update version sbws running in testnet
Things to communicate:
- i put as date of sbws release 1.0.0 (milestone 1) 1st May, but
i'd postpone
to later so that we've more time testing and fixing last details
- teor, can i make public the list of tasks you've proposed for
SoP?, any place you would propose?
- pastly: It's fine to close issues/PRs you think aren't apropiate
for any reasons, but please say so before closing (#111, #87)
- i stop attending net-team meetings until we need to disscuss
something there that we don't discuss in this meeting
List of tasks for 3 months proposed by T. (19th Apr)
- implement features we wanted in torflow in sbws instead (1 week)
- bwauth code needs to be smarter about failed circuits
https,//trac.torproject.org/projects/tor/ticket/16559
- assign the 10-second client timeout as the time for failed circuits?
- at least publish failure rates
https,//trac.torproject.org/projects/tor/ticket/7281
- Understand how accurate the bandwidth authority estimates are
https,//trac.torproject.org/projects/tor/ticket/7177
- integration tests (1 week)
- a practice transition in the test network (1 week, but split up)
- set up torflow
- set up sbws
- compare and switch
- work little-t tor needs (3 weeks)
- report version of bwscanners in votes
https,//trac.torproject.org/projects/tor/ticket/3723
- stop relays reporting zero observed bandwidths
https,//trac.torproject.org/projects/tor/ticket/24250
- relays should regularly do a larger bandwidth self-test
https,//trac.torproject.org/projects/tor/ticket/22453
- bandwidth testing circuits should use guards sometimes
https,//trac.torproject.org/projects/tor/ticket/19009
- report bandwidth more often on test networks
https,//trac.torproject.org/projects/tor/ticket/17036
- report bandwidth less often on large, public relays
https,//trac.torproject.org/projects/tor/ticket/24104
- non-essential tickets like
https,//github.com/pastly/simple-bw-scanner/77 and
https,//github.com/pastly/simple-bw-scanner/48 (2 weeks) - if time and
motivation
- Have sbws client launch tor itself
https,//github.com/pastly/simple-bw-scanner/77
- Evaluate using [not threads, but twisted instead (probably)]
https,//github.com/pastly/simple-bw-scanner/48
teor:
last week:
* made my test dirauth a trust pastly's and juga's dirauths
* monitored the average bandwidth on the testnet using this
script: https://pad.riseup.net/p/tor-vote-bw-average
* opened a ticket for getting similar features into
consensus-health: https://github.com/pastly/simple-bw-scanner/issues/120
this week:
* busy with deadlines
* eventually try to set up sbws on the testnet
Discussion
=========================================
### Topic: Switch to HTTP(S)
### (Proposed) Topic: SoP
- specific topics on this?
pastly: where can I find your proposed schedule again?
juga: mail
pastly: finally found it
- personally i'm not sure on how to organize the tasks we've said i'll
do for SoP, since that's in a month. Either i do now other stuff not
included there (doing so so far), or i start with those tasks and then
update to others during SoP
http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-04-26-09.59.html
https://pad.riseup.net/p/6292yqhUOuHC (copy/pasted below)
Simple Bandwidth Scanner Meeting 25 April 2018
==============================================
This pad:
https://pad.riseup.net/p/6292yqhUOuHC
Previous week's notes:
https://lists.torproject.org/pipermail/tor-dev/2018-April/013084.html
Witty quote
- Unknown
Updates
===========================================
pastly:
last 7 days:
- sbws is now open source
https://github.com/pastly/simple-bw-scanner
https://sbws.readthedocs.io/en/latest/
- fix some bad bugs in 'sbws cleanup' command while writing tests for it
- integrate with Travis CI and automatically test against python 3.4,
3.5, and 3.6
- integrate with Read the Docs
- gather intel on the environments our users will be running sbws in
https://github.com/pastly/simple-bw-scanner/wiki/Information-regarding-sbws's-target-user-base
- did some research regarding library support for various distros.
incomplete
- remvoe filelock dependency
- brainstorm what I think a switch to http(s) should look like
https://sbws.readthedocs.io/en/latest/proposals/001-switchtohttp.html
next 7 days:
- start implementing the switch to http(s)
- verify sbws works with library versions that aren't the absolute
newest
misc notes section (not udpates)
juga's tor tickets:
https://trac.torproject.org/projects/tor/query?status=!closed&cc=%7Ejuga
juga:
Not sure which week was (since we changed from Monday to Thursday):
- review, comment on debug option not being used #85
- add logging conf to log to file/system #87
- review Periodically test reachability of helpers #93
- create issue Include file where to write ``generate`` results in
the config #91
suggest having options both in config and cli and cli overriding
conf
- report about problem with init and helpers #95
- create issue about adding software to header #96
- review using kilobytes #97, #98
Past week:
- fix conf issues locally and in testnet after "megacommit"
- more changes on the spec, after new teor review
https://github.com/torproject/torspec/pull/4/commits/54ef4d4355d2b475466bf11e80ad4bc57c7e7ec3
- create improve deployability #99
- create issue Debian package #101
- Work on issue software and sofware_version in v3bw files #112
- create issue Include coverage in travis #117
- create issue Include travis and coverage badges in README
enhancement #118
Next week:
- debug what tor does to solve
https://github.com/torproject/torspec/pull/4/#issuecomment-384555243
- review the software/version ticket according to results from
previous (https://github.com/pastly/simple-bw-scanner/issues/96)
- review spec according to results from previous
- add a default output file for generate that can be overriden by
cli args (https://github.com/pastly/simple-bw-scanner/issues/91)
- improve deployability, this should also help to update instances
running in testnet (https://github.com/pastly/simple-bw-scanner/issues/99)
- update version sbws running in testnet
Things to communicate:
- i put as date of sbws release 1.0.0 (milestone 1) 1st May, but
i'd postpone
to later so that we've more time testing and fixing last details
- teor, can i make public the list of tasks you've proposed for
SoP?, any place you would propose?
- pastly: It's fine to close issues/PRs you think aren't apropiate
for any reasons, but please say so before closing (#111, #87)
- i stop attending net-team meetings until we need to disscuss
something there that we don't discuss in this meeting
List of tasks for 3 months proposed by T. (19th Apr)
- implement features we wanted in torflow in sbws instead (1 week)
- bwauth code needs to be smarter about failed circuits
https,//trac.torproject.org/projects/tor/ticket/16559
- assign the 10-second client timeout as the time for failed circuits?
- at least publish failure rates
https,//trac.torproject.org/projects/tor/ticket/7281
- Understand how accurate the bandwidth authority estimates are
https,//trac.torproject.org/projects/tor/ticket/7177
- integration tests (1 week)
- a practice transition in the test network (1 week, but split up)
- set up torflow
- set up sbws
- compare and switch
- work little-t tor needs (3 weeks)
- report version of bwscanners in votes
https,//trac.torproject.org/projects/tor/ticket/3723
- stop relays reporting zero observed bandwidths
https,//trac.torproject.org/projects/tor/ticket/24250
- relays should regularly do a larger bandwidth self-test
https,//trac.torproject.org/projects/tor/ticket/22453
- bandwidth testing circuits should use guards sometimes
https,//trac.torproject.org/projects/tor/ticket/19009
- report bandwidth more often on test networks
https,//trac.torproject.org/projects/tor/ticket/17036
- report bandwidth less often on large, public relays
https,//trac.torproject.org/projects/tor/ticket/24104
- non-essential tickets like
https,//github.com/pastly/simple-bw-scanner/77 and
https,//github.com/pastly/simple-bw-scanner/48 (2 weeks) - if time and
motivation
- Have sbws client launch tor itself
https,//github.com/pastly/simple-bw-scanner/77
- Evaluate using [not threads, but twisted instead (probably)]
https,//github.com/pastly/simple-bw-scanner/48
teor:
last week:
* made my test dirauth a trust pastly's and juga's dirauths
* monitored the average bandwidth on the testnet using this
script: https://pad.riseup.net/p/tor-vote-bw-average
* opened a ticket for getting similar features into
consensus-health: https://github.com/pastly/simple-bw-scanner/issues/120
this week:
* busy with deadlines
* eventually try to set up sbws on the testnet
Discussion
=========================================
### Topic: Switch to HTTP(S)
### (Proposed) Topic: SoP
- specific topics on this?
pastly: where can I find your proposed schedule again?
juga: mail
pastly: finally found it
- personally i'm not sure on how to organize the tasks we've said i'll
do for SoP, since that's in a month. Either i do now other stuff not
included there (doing so so far), or i start with those tasks and then
update to others during SoP