Opened 3 years ago

Closed 2 years ago

#22263 closed enhancement (implemented)

Raise @type torperf version produced by OnionPerf from 1.0 to 1.1

Reported by: karsten Owned by: metrics-team
Priority: Medium Milestone:
Component: Metrics/CollecTor Version:
Severity: Normal Keywords:
Cc: robgjansen, hiro Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

OnionPerf adds a few keys to Torperf's @type torperf 1.0 format that parsers for that version don't recognize. That's what we have the version number for. We should change that annotation to @type torperf 1.1 to reflect this backward-compatible format change.

Next steps:

  • Change version number in the OnionPerf sources.
  • Update to latest OnionPerf on our three OnionPerf instances and produce new .tpf files on our OnionPerf instances back to April 11, 2017.
  • Download updated .tpf files in CollecTor and re-create tarballs.
  • Update CollecTor website to describe new keys in version 1.1 (branch follows in a bit).

Child Tickets

Change History (4)

comment:1 Changed 3 years ago by karsten

My branch task-22263 contains the website changes for that last step there. We should do the others first, though.

comment:2 Changed 3 years ago by robgjansen

Onionperf has been updated to export files with @type torperf 1.1 instead of @type torperf 1.0. Change has been pushed to master:
https://github.com/robgjansen/onionperf/commit/3b40d4993fd657e3e8fe063507d9f8a7cdcdec3a

Last edited 3 years ago by robgjansen (previous) (diff)

comment:3 Changed 2 years ago by karsten

I just looked and found that all three op-* instances have been updated (long ago). Thanks, robgjansen and hiro! I just re-created CollecTor tarballs since April 2017.

The remaining step is:

  • Update CollecTor website to describe new keys in version 1.1 (branch follows in a bit).

comment:4 Changed 2 years ago by karsten

Resolution: implemented
Status: newclosed

I just merged and deployed the remaining website changes. Closing.

Note: See TracTickets for help on using tickets.