Opened 18 months ago

Closed 6 months ago

Last modified 6 months ago

#24804 closed task (fixed)

Run an opt-in process for relay operators to become fallbacks in 2018

Reported by: teor Owned by: phoul
Priority: Medium Milestone: Tor: 0.4.0.x-final
Component: Core Tor/Fallback Scripts Version:
Severity: Normal Keywords: s8-bootstrap, fallback, 034-triage-20180328, 034-removed-20180328, 035-roadmap-subtask, 035-triaged-in-20180711, 035-can
Cc: Actual Points:
Parent ID: #24786 Points: 2
Reviewer: Sponsor: Sponsor8-can

Description

This involves mailing tor-relays and asking if stable relay operators want to become fallbacks.

Child Tickets

Change History (16)

comment:1 Changed 18 months ago by teor

We can also personally email operators of high-bandwidth relays, and ask them to opt-in their relays.

And we can find existing operators of groups relays on the fallback whitelist, and ask them to opt-in their other relays. (Operators can opt-in any number of fallbacks, and we will select up to 7 fallbacks per operator.)

comment:2 Changed 15 months ago by nickm

Keywords: 034-triage-20180328 added

comment:3 Changed 15 months ago by nickm

Keywords: 034-removed-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

comment:4 Changed 15 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: unspecified

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

comment:5 Changed 14 months ago by teor

Milestone: Tor: unspecifiedTor: 0.3.4.x-final
Owner: set to teor
Status: newassigned

We should do this task in 0.3.4 or 0.3.5, but hopefully we have a relay operator support coordinator by then.

comment:6 Changed 14 months ago by teor

Owner: teor deleted

I hope the relay support,coordinator will do this

comment:7 Changed 14 months ago by teor

Milestone: Tor: 0.3.4.x-finalTor: 0.3.5.x-final

8/150 = 5% of fallbacks are currently down.
https://consensus-health.torproject.org/graphs.html
At this rate, it will be 2019 before we reach our 25% failure threshold.
So we don't need to do a fallback rebuild in 0.3.4.

comment:8 Changed 12 months ago by phoul

Owner: set to phoul

comment:9 Changed 12 months ago by teor

Hi phoul,

Here's an example: https://lists.torproject.org/pipermail/tor-relays/2017-December/013898.html (without the DDoS bit)
Please add that we choose up to 7 relays per operator.

comment:10 Changed 12 months ago by nickm

Keywords: 035-roadmap-subtask added

comment:11 Changed 12 months ago by teor

Cc: teor@… removed

Remove useless CC

comment:12 Changed 11 months ago by nickm

Keywords: 035-triaged-in-20180711 added

comment:13 Changed 10 months ago by teor

25% of fallbacks are failing, so these tickets need to be done in 0.3.5.

comment:14 Changed 7 months ago by nickm

Keywords: 035-can added

comment:15 Changed 6 months ago by teor

Keywords: s8-bootstrap added
Milestone: Tor: 0.3.5.x-finalTor: 0.4.0.x-final
Resolution: fixed
Sponsor: Sponsor8-can
Status: assignedclosed

This task is done, we're about to merge the whitelist in #24805, and we're generating the new hard-coded list in #24803.

Phoul, if you can update this ticket's "Actual Points" with the number of days you spent on this task, that will help gaba with the project management.

comment:16 Changed 6 months ago by teor

Summary: Run an opt-in process for relay operators to become fallbacksRun an opt-in process for relay operators to become fallbacks in 2018

New whitelist changes can go in #28794.

Note: See TracTickets for help on using tickets.