[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #21272 [Metrics]: Onionperf deployment

#21272: Onionperf deployment
-------------------------+------------------------------
 Reporter:  hiro         |          Owner:  metrics-team
     Type:  enhancement  |         Status:  needs_review
 Priority:  Medium       |      Milestone:
Component:  Metrics      |        Version:
 Severity:  Normal       |     Resolution:
 Keywords:               |  Actual Points:
Parent ID:               |         Points:
 Reviewer:               |        Sponsor:
-------------------------+------------------------------

Comment (by karsten):

 robgjansen, thanks for the great suggestions above!  I think we can make
 this work.  Here are my suggestions:

  - ''Source names'': Maybe we should just pick a naming scheme that works
 for the moment without expecting that it will scale in the future.  Your
 example of an instance moving from the U.S. to Canada is a great example.
 Sure, you could split the data into two sets and pick different names.
 But if we open up contributions to other community members, which I think
 we should, we'll see similar changes happening, and we can't expect other
 operators to get the naming right.

    My suggestion for the source name of your instance would be to just
 stick with 'phantomtrain'.  The only change that you'd have to make though
 is make the data (also) available under
 http://phantomtrain.robgjansen.com:8081/.  The reason is that we're
 currently parsing the first part of the domain name and comparing that to
 the beginning of file names and source names contained in the data.  If
 this is not an easy change for you, we can look into making CollecTor a
 little more flexible.  But maybe it's just a simple configuration change
 for you.

  - ''Local IP address'': Even if we pick source names that don't indicate
 locations, we could resolve instance IP addresses to country codes and AS
 numbers when displaying results on Tor Metrics.  But therefore we'll have
 to find out the public IP address and include it in the data.  I'm yet
 unsure how we'd do that.  I mean, "endpoint_remote" contains a host name
 and IP address, but only for direct downloads, but this information is
 also relevant for onion services.

    Hmm, I don't really have a good suggestion for this.  Do you have an
 idea?

  - ''Ports 80, 6666, and 8080'': I agree that the difference is minimal,
 and we probably don't even have to mention this on Tor Metrics.  But still
 I'd like to preserve this information somewhere in the data.  Because who
 knows if somebody wants to run an OnionPerf instance with a rather unusual
 port.

    I wonder if we can include both `--tgen-listen-port` and `--tgen-
 connect-port` in the output?  Maybe we'll have to add a new field
 "endpoint_connect" with remote host name, remote address, and connect
 port?  Or maybe there's a better way to include this information, possibly
 even related to the previous change where we include the local IP address?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21272#comment:49>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs