Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #24429

Closed (moved)
Open
Opened Nov 27, 2017 by iwakeh iwakeh@iwakeh

Provide fallback mirror data in Metrics

Tor's fallback mirror list changes regularly. Relay Search also provides the information per relay based on a manual update process and local data. This process should be improved and automated in the following way:

  • All fallback mirror lists should also be provided by CollecTor (including historic lists).
  • Parsing functionality for these lists should be provided as part of metrics-lib.
  • And, finally, based on the above, Onionoo should provide the information enabling Relay Search to simply query Onionoo instead of maintaining its own list.

This is the summary ticket for discussion of overall approach and timing. The child tickets take care of the actual implementations in the various Metrics products.

References: information about list update process information about fallback mirrors

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#24429