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

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

changed milestone to %Tor: 0.4.0.x-final

added 034-removed-20180328 034-triage-20180328 035-can 035-roadmap-subtask 035-triaged-in-20180711 component::core tor/fallback scripts fallback milestone::Tor: 0.4.0.x-final owner::phoul parent::24786 points::2 priority::medium resolution::fixed s8-bootstrap severity::normal sponsor::8-can status::closed type::task labels

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.)

Trac:
Keywords: N/A deleted, 034-triage-20180328 added

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

Trac:
Keywords: N/A deleted, 034-removed-20180328 added

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

Trac:
Milestone: Tor: 0.3.4.x-final to Tor: unspecified

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

Trac:
Status: new to assigned
Milestone: Tor: unspecified to Tor: 0.3.4.x-final
Owner: N/A to teor

I hope the relay support,coordinator will do this

Trac:
Owner: teor to N/A

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.

Trac:
Milestone: Tor: 0.3.4.x-final to Tor: 0.3.5.x-final

Trac:
Owner: N/A to phoul

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.

Trac:
Keywords: 034-removed-20180328 deleted, 034-removed-20180328 035-roadmap-subtask added

Remove useless CC

Trac:
Cc: teor@torproject.org to N/A

Trac:
Keywords: 034-removed-20180328 035-roadmap-subtask deleted, 035-roadmap-subtask, 035-triaged-in-20180711, 034-removed-20180328 added

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

Trac:
Keywords: N/A deleted, 035-can added

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

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.

Trac:
Milestone: Tor: 0.3.5.x-final to Tor: 0.4.0.x-final
Keywords: N/A deleted, s8-bootstrap added
Resolution: N/A to fixed
Status: assigned to closed
Sponsor: N/A to Sponsor8-can

New whitelist changes can go in #28794 (moved).

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

closed

changed time estimate to 16h

mentioned in issue #24805 (moved)

mentioned in issue tpo/core/tor#24805 (closed)

moved to tpo/core/fallback-scripts#24804 (closed)