[tor-dev] Dealing with critical sbws tickets

[teor]

Hi,

> On 4 Jun 2019, at 15:29, juga <juga at riseup.net> wrote:
> 
> teor:
>> Hi juga,
>> 
>> I read your meeting notes from this week's network team meeting:
>> 
>> juga(offline):
>>   Week of 05/20 (planned)
>>      - Add Tor version to the bandwidth file (#30196)
>>   Week of 05/20 (actual)
>>   Week of 06/03 (plan)
>>      - Continue with #30406: Refactor header constants in sbws to
>> use Stem's one
>> 
>> For the next few weeks, can you focus on fixing critical sbws bugs,
>> and helping with authority deployments?
> 
> Yes, i'll do my best with the little time i've to continue with sbws.

Thanks!

Please let us know if you need help.

Until we get more sbws funding, we won't have much time to spend
on sbws features (like extra diagnostic information). But we can
spend a bit of time fixing critical sbws bugs.

>> Here's what I think we could do:
>> 
>> I would like us to deploy sbws to 3/6 bandwidth authorities some time
>> in June. We can do this deployment as soon as another directory
>> authority operator is ready.
> 
> There's another authority operator ready. If you think we don't need to
> fix any bug before a 3rd directory authority runs sbws, i can tell them
> to start running sbws.

Yes please!

>> 
>> To deploy more than 3 sbws instances, we need to fix these critical sbws
>> bugs:
>> 
>> We need sbws to generate bandwidth lines for all relays with results,
>> even if they are not Running in the sbws tor client's current consensus.
>> https://trac.torproject.org/projects/tor/ticket/29710#comment:13
>> 
>> We need sbws to use MaxAdvertisedBandwidth from the latest descriptors:
>> https://trac.torproject.org/projects/tor/ticket/30733
>> 
>> We also need to look for any more critical bugs in sbws. Here are some
>> ways we can check for bugs:
>> 
>> We need to check if all sbws instances exclude some relays, to help us find
>> any more bugs in sbws:
>> https://trac.torproject.org/projects/tor/ticket/30735
>> 
>> 90% of sbws measurement attempts fail. But these are internal errors, not
>> network errors. So it looks like sbws has a relay selection bug:
>> https://trac.torproject.org/projects/tor/ticket/30719#comment:2
>> 
>> After we do these tasks, we can deploy sbws to 4 bandwidth authorities.
>> 
>> What do you think?
>> 
> I'll look at all these bugs more in detail.
> How many directory authorities would we like to be running sbws (after
> those bugs are fixed) by which date?.

I think switching one per month is a good idea:

https://lists.torproject.org/pipermail/tor-dev/2019-June/013869.html

> BTW, longclaw's sbws did not have network for ~1 days (which for sure
> has affected to some metrics), i should have documented that somewhere,
> not sure there's a better place for that than trac.

I'm not really sure. Sending a quick email to tor-dev might be a good idea.

T
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20190605/7e8132ed/attachment.html>