14:29:42 #startmeeting metrics team 14:29:42 Meeting started Thu May 11 14:29:42 2017 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:29:42 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:29:44 hello! 14:29:53 https://pad.riseup.net/p/3M7VyrTVgjlF has the agenda. 14:30:00 anything else we want to discuss today? 14:30:06 hello 14:30:10 hi! 14:30:14 hi hiro! 14:30:17 hi 14:30:19 hi all 14:31:12 irl: you around? 14:31:46 I wanted to ask what happened with the webstats stuff, it seems april 6th was the last time it was mentioned. If no ping is needed sorry for the noise :) 14:32:16 argh. 14:32:23 oh! 14:33:47 okay, we have a few topics. 14:33:52 shall we start? 14:34:08 yes! 14:34:17 - webstats migration to CollecTor (Sebastian) 14:34:44 is everything in everyone's inboxes, or are there some quick links we could put in the action item here? 14:35:01 Who's inbox? 14:35:10 yours? mine? 14:35:17 I don't know. 14:35:22 Me neither. 14:35:45 Guess, this should be moved to higher prio? 14:36:11 Sebastian: where's the current code? 14:36:35 https://gitweb.torproject.org/webstats.git/ 14:37:01 it's fine if it takes time, I just wondered because nobody asked me about it. 14:37:10 getting it completely forgotten would be annoying :) 14:37:17 it's buried under many other things. 14:37:19 it was. 14:37:23 Now we can look at it 14:37:27 it's not much code, right? 14:37:44 no 14:37:50 the awestats stuff is unused? 14:37:54 awstats 14:38:08 like 140 lines 14:38:10 yes 14:38:17 alright. 14:38:20 let's prioritize this. 14:38:23 fine. 14:38:27 who does this? 14:38:46 * iwakeh could do that. 14:39:00 sounds great! 14:39:06 what about sync? 14:39:12 is it easier to leave that out for now? 14:39:18 I'll see. 14:39:20 and just download and sanitize? 14:39:38 okay. happy to review code in early stages even. 14:39:42 and will make some plans with optional functionality. 14:39:43 I imagine syncing could be easy as it's just one file per day, per target 14:39:57 but I don't know metrics that well. 14:40:02 ah, syncing in the collector sense, as in: sync from other collector hosts. 14:40:13 We have a sync mechanism in place. 14:40:21 That will be expanded. 14:40:40 okay. 14:40:43 thanks for the reminder. 14:41:06 - longterm or not at all(?): can metrics benefit from easily integrated document parsers etc that get written during the Rust experiment? (Sebastian) 14:41:17 let's talk about that next. 14:41:21 What kind of experiment? 14:41:36 that's the rewrite-tor-in-rust experiment, right? 14:41:42 Tor is doing an experiment of putting some of its code in Rust 14:41:50 Oh, I'd suggest Java :) 14:42:21 Fine, and the result is a parser? 14:42:25 I was thinking that metrics might benefit from re-using some of the rust code we're writing to parse stuff and put it in a database. Or maybe that's crazytalk. Just an idea. 14:42:26 First result? 14:42:45 No, this is just wondering whether while we're fleshing out the Rust stuff we should think about metrics at all. 14:43:01 so, we were thinking about improving parsers using a different approach: 14:43:03 ANTLR. 14:43:13 which is similarly long-term. 14:43:16 Well, a rusty tor would need to produce the same descriptors. 14:43:35 I'm mostly thinking that as Tor changes, you always need to keep up by implementing the same thing in Java 14:43:47 and wouldn't it be neat if you could make use of the code already written for tor 14:43:55 Not really with ANTLR 14:44:15 antlr uses grammar for generating parsers in many languages. 14:44:19 the question is, would you be able to use ANTLR for generating rust code? 14:44:29 and, grammar would benefit tor again for 14:44:32 to avoid writing that code yourself at all. 14:44:35 defining the protocol. 14:44:53 there was a (short) discussion on tor-dev a while ago. 14:45:00 that's more a question for the C people at this point I think 14:45:02 so, an even more unifying approach. 14:45:11 not really. 14:45:11 if they specify a grammar for documents, we'd generate the parser of course. 14:45:58 This is more long term. I think. 14:46:11 But I'd like to look at the code. 14:46:31 Curious :-) 14:46:46 I agree that this is more long-term. 14:47:21 I'd say don't worry too much about metrics here for the moment. 14:47:22 Where is the code to be found? 14:47:42 after all, we already have a quite comprehensive parsing library to work with. 14:47:46 iwakeh: let's discuss that offline? It's an ongoing project with a couple of branches here and there, hopefully soon in tor.git 14:47:47 true 14:48:06 Sebastian: fine. 14:48:07 okay, great! 14:48:11 but ok, will not worry about metrics. Thanks 14:48:19 thanks for asking. :) 14:48:20 Thanks! 14:48:30 * karsten moves irl's topic to the end. 14:48:33 - metrics-lib "easy" tickets (Samdney) 14:48:44 ah that's me 14:48:50 did you enjoy the two easy tickets I mentioned last week? :) 14:49:01 anything you need to move forward? 14:49:12 I'm interested in #21751 14:49:14 How easy? 14:49:23 good question. 14:49:33 easy as in: does not need tons of metrics-lib context before starting. 14:49:40 This is rather invvolved, I'd say. 14:49:43 I have to finish something private at first which need more time like I thought 14:49:57 I hope I will find time at the weekend :) 14:49:59 can you come up with an easier one? 14:50:01 Samdney, how easy? 14:50:13 Does it need to be metrics-lib? 14:50:24 no. 14:50:36 I'd have something to get started in Java coding the Metrics-Team way. 14:50:45 I only looking for something for getting familiar with the code ... :) 14:50:55 Sure. 14:51:03 * iwakeh looking for the ticket 14:51:38 This ticket needs a little more work #20546 14:51:51 I didn't get around reviewing yet. 14:52:09 the code is modular and will serve 14:52:20 future improvements of CollecTor. 14:52:37 okay. 14:52:50 Will have a look the next days. 14:52:56 great! 14:53:03 I could mail some more info to you, Samdney? 14:53:15 That would be great :D 14:53:21 About what is left, or post it to the ticket. 14:53:29 ok, mail then. 14:53:33 cool! 14:53:37 moving on? 14:53:45 fine for me. 14:53:51 iwakeh: do you have my email address? 14:54:13 I think we were on the same thread somewhere. 14:54:28 ok, else ping me ;) 14:54:39 sure 14:54:42 - metrics-lib release planning (karsten) 14:54:47 1.7.0 14:54:55 so, I touched almost all metrics-lib tickets in the past 1.5 weeks. 14:55:04 yes, 1.7.0 and 2.0.0. 14:55:04 hehe, noticed. 14:55:25 I wonder if we should have another meeting where we go through them all and discuss them more synchronously than via email/trac. 14:55:43 That might be helpful. 14:56:06 how's your friday afternoon? 14:56:21 Later afternoon ought to be fine. 14:56:41 15:00 UTC? like in 24 hours? 14:56:50 perfect! 14:57:28 great! 14:57:38 next: 14:57:40 - Wrapping up OnionPerf's onion server stats on Metrics (#22112) (karsten) 14:57:47 sorry about the renaming confusion. 14:57:49 ;) 14:58:00 so, if we finish that ticket, we can invoice for the deliverable. 14:58:15 and we'll want to invoice for three remaining deliverables in may and june. 14:58:30 maybe we can finish this one by the end of this week? 14:59:42 still here? 15:00:10 yes 15:00:14 ah. :) 15:01:25 I replied to 22112 15:02:08 mixup, not to comment3 yet. 15:02:31 so many tickets.. 15:02:50 Well, those permutations of ones and twos everywhere ... 15:02:56 hehe 15:03:15 I'll take a look after this meeting. 15:03:19 perfect! 15:03:25 - CollecTor operation (karsten) 15:03:37 not sure whether there's much to discuss at this point. 15:03:44 Hi, Tor metrics team. I would like to contribute for the summer. How can I get started? 15:03:51 just thought I'll put it in as placeholder. 15:04:11 I'll try to access and that should be fine; now that I know how to get there ;-) 15:04:21 hi kiki101, we have something on the wiki for volunteering. let's see where that page is.. 15:04:49 https://trac.torproject.org/projects/tor/wiki/org/teams/MetricsTeam/Volunteers 15:04:56 https://trac.torproject.org/projects/tor/wiki/org/teams/MetricsTeam/Documentation 15:05:09 for more general questions. 15:05:25 and guide docs on the bottom of the page. 15:05:48 Samdney: do you have a trac persona? 15:05:52 Thanks, I'll check them out. 15:05:54 yes 15:06:01 same as here? 15:06:06 yes 15:06:14 kiki101: maybe take a look around, and if you find something, come back next week and we can answer questions? 15:06:35 Yep, I will do that. 15:06:41 okay, moving on: 15:06:45 - OnionPerf deployment state (hiro) 15:06:52 sure. 15:07:00 I haven't heard back from irl 15:07:08 and I can see his op-ab is timing out 15:07:13 ok. :/ 15:07:14 maybe he is having the same issues I was having 15:07:46 but I am not sure since I haven't accesso to his setup at the moment 15:08:16 and op-se isn't deployed yet as Ln5 reported in the email to tor-team 15:08:33 reagarding op-hk, were you able to clean those old data? 15:08:40 ah, yes. 15:08:42 ah great 15:08:45 found a metrics-lib bug while doing so. 15:08:56 but the data on metrics.tpo should be good now. 15:08:57 perfect 15:09:22 and I briefly talked to rob about adding phantomtrain, but I still owe him a reply. 15:09:38 yes regarding the old data 15:09:57 so, he said he's fine with keeping the server for testing. 15:10:18 but he'd also prefer if we'd add past data up to this point. 15:10:32 from last year or so. 15:10:41 any reasons against doing that that I'm overlooking? 15:10:59 should be ok. 15:11:23 okay. it feels a bit odd to touch all the tarballs to add new data, but I didn't find compelling reasons not to do it. 15:11:34 well I do not know about metrics, but if he was measuring without our setup maybe some of his data would have the same issue that the first data I was generating were having 15:11:48 good point 15:11:48 with "our setup" I mean port 80 forwarding and such 15:11:50 I think he used port 8080. 15:11:59 without port forwarding. 15:12:04 Could we keep the data separate? 15:12:15 I have no idea how much that could change tho :) 15:12:28 separate as in: experimental data? 15:12:43 I was thinking about such a thing in the past. 15:12:54 Well, it is measured in a different manner 15:12:57 we did a few experiments with torperf and never put the data anywhere. 15:13:00 slightly at least. 15:13:16 the question here is: would we include the data on tor metrics? 15:13:20 probably not. 15:13:22 that should be reflected/recorded in some way. 15:13:50 let's think more about that! 15:13:54 It will be stored on rob's server anyway? 15:14:08 well, the value would to mirror it and also document what it is. 15:14:26 true; needs more thinking. 15:14:33 which makes sense if we add 10 other data sets from 5 different people. 15:14:47 yes, but it's an interesting idea. 15:15:05 Yes, and could be the new data we need nextt year. 15:16:01 the goal would be slightly different though. 15:16:12 but let's think more about this and talk offline. 15:16:23 fine. 15:16:30 - Atlas 1.0 (irl) 15:16:37 no sign of irl, I think? 15:16:57 anything else for today? 15:17:03 I'm fine. 15:17:15 is the meeting 30 minutes now? 15:17:27 originally 45min 15:17:32 ah that's perfect then 15:17:34 always on time 15:17:37 :) 15:17:37 :) 15:17:38 hehe 15:17:38 right now we're at 48 minutes. 15:18:08 okay, let's talk more about metrics-lib tomorrow at 15 utc and about all things metrics next week! 15:18:13 thanks, everyone! bye, bye! 15:18:16 #endmeeting