14:59:41 #startmeeting metrics team 14:59:41 Meeting started Thu Mar 16 14:59:41 2017 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:59:41 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:59:47 https://pad.riseup.net/p/3M7VyrTVgjlF <- agenda pad 15:00:07 please add more topics if you want. 15:00:33 in the meantime, admire this new page: https://metrics.torproject.org/metrics-lib.html 15:00:41 yes! 15:00:50 and do the tutorials ! 15:00:56 oh, yes! 15:01:03 rather after the meeting, though ;-) 15:01:43 should we start, or wait a bit longer? 15:01:51 anyone missing? 15:01:58 hiro won't be able to join us today. 15:02:07 but I have some status to report about onionperf. 15:02:12 (later) 15:02:38 okay, if anything else comes up during the meeting, please add it to the agenda. 15:02:41 let's start. 15:02:45 - Tor Metrics pages (karsten) 15:02:52 - metrics-lib.html (exists; Git/Ant) 15:02:58 that's the link I just pasted. 15:03:10 the part that's missing is javadocs. 15:03:26 iwakeh: did you have the chance to look into that yet? 15:03:44 not yet, but the submodule should work 15:04:05 stating that from the bird's eye perspective. 15:04:20 yes, I don't see any major obstacles there, 15:04:31 Basically, git checkout and some file copying. 15:04:37 but there are probably a few details. 15:04:43 right. 15:04:49 ok. 15:04:50 (ant docs run in between) 15:05:08 I'll look at it this week. 15:05:22 neat. and I think the other new pages are related. 15:05:27 onionoo.html and collector.html. 15:05:28 One idea 15:05:32 yes? 15:05:37 that just came to mind. 15:05:57 could the intro pages from onionoo for example 15:06:12 be used as the javadoc overview page, which 15:06:16 is still missing. 15:06:29 there's indeed some overlap. 15:06:34 Just until we write a real intro. 15:07:07 and, it would be nice to have the protocol in the javadoc 15:07:14 regarding onionoo. 15:07:44 I just have that in mind, too, when looking at the other topic. 15:07:50 I could see how we're using existing content until we have more time to write new content. 15:08:13 I'm a bit worried about keeping two pages that are almost the same. 15:08:26 right, this way there is only one. 15:08:27 because we tend to forget one of them and let it rot. 15:08:41 oh, well, 'age'. 15:08:44 heh 15:09:07 sounds plausible. 15:09:12 having only 1 page. 15:09:35 regarding onionoo, I was wondering what to do with the table of contents. 15:09:37 and, there we don't publish javadoc yet on a web site. 15:09:52 toc? 15:09:53 because none of the pages on metrics.tpo has a table of contents. 15:09:59 the box with on-page links. 15:10:03 ah 15:10:13 doesn't hurt? 15:10:34 maybe. but then we might consider having one on other pages, too. 15:10:42 anyway, not the most pressing issue. 15:11:07 how do we move forward? do you want to look at git/ant things for all three pages this week? 15:11:09 true, wait for feedback. 15:11:32 sure, it's one from the technology perspective. 15:11:44 yep. 15:12:13 okay, cool! maybe we can move these pages before AMS, because there will be a website discussion, and having metrics.tpo done would be nice. 15:12:32 doable. 15:13:06 RaBe: by the way, I might not be in town on monday. maybe we can do the meeting via irc? 15:13:33 yes, sure! 15:13:36 to do any remaining polishing. 15:13:43 cool! 15:14:07 move on? 15:14:14 yep. 15:14:14 * karsten just added another topic after this one. 15:14:19 - Atlas (RaBe) 15:14:23 irl: you around? 15:14:34 how's atlas going, 1.5 weeks after the blog post? :) 15:16:11 RaBe: ^ 15:16:27 well, there are some patches ready for review, and i'll see if I can do some more after they're merged :) 15:16:45 sounds good! 15:17:21 okay, no pressing questions/things to discuss here, right? 15:17:27 no 15:17:31 ok :) 15:17:57 okay, moving on: 15:18:01 - OnionPerf progress (karsten) 15:18:26 hiro set up 3 instances in the cloud plus 1 instance on a Tor VM. 15:18:30 was there a naming problem? 15:18:39 yes, with the Tor VM. 15:19:04 we're still looking into that. 15:19:09 well, into how to work around it best. 15:19:22 there are other minor bugs in onionperf. or in the setup. 15:19:28 https://people.torproject.org/~karsten/volatile/onionperf-2017-03-16.pdf 15:19:37 ^ that's a quick plot of the three instances. 15:19:48 so, they're all producing data now. 15:20:21 complete/1000 (what unit?) 15:20:44 it's hard to say when the setup will be bug-free enough to put data on collector/metrics. 15:21:00 complete is milliseconds, so the displayed unit is seconds. 15:21:06 log scale. 15:21:10 are there tickets? 15:21:14 for the problems. 15:21:19 yes, on github. 15:21:57 similar to the website, it would be great to have data by AMS. 15:22:04 which seems doable. 15:22:12 Can I help somewhere? 15:22:23 yes. the collector patch. 15:22:29 * karsten finds the ticket number.. 15:22:54 #21272 15:22:55 #21272 15:22:59 so close! 15:23:02 I won :-) 15:23:12 you did. 15:23:28 " iwakeh, patch looks good, pushed to ​my task-21272 branch. Thanks! Do you want to change anything else, or can I squash and merge?" 15:24:01 oh, these should be two tickets. 15:24:10 I'll reply after the meeting. 15:24:17 and once it's merged, we'll need to decide when to deploy. 15:24:22 yes, maybe even more than 2. 15:24:41 true; deploy != release 15:24:43 ? 15:24:57 hmm, fine question. 15:25:07 we could release, too. 15:25:09 and then deploy. 15:25:20 before AMS???? 15:25:22 unless we need to resolve many other tickets for that. ;) 15:25:47 I think deploy without release is fine, as there are not that many tests... 15:26:12 sure, we can do that, too. 15:26:20 having the data is what matters most, I think. 15:26:28 and putting it on metrics-web. 15:26:34 Otherwise mirror operators feel forced to udate, too. 15:26:50 which is easy and might not require code changes. I didn't look. (<- metrics-web changes) 15:27:02 good point re: mirror operators needing to update. 15:27:21 ok? 15:27:40 one question is what we do if we learn that data is invalid, because of an onionperf bug. 15:27:55 we could just delete that data. 15:28:03 we're indending to collect in parallel for a while? 15:28:29 yes, buggy data should be deleted. 15:28:30 yes, but we'll provide both torperf and onionperf data. 15:28:42 and clients might not notice the difference. 15:28:44 Label onionperf as beta? 15:28:58 where? 15:29:00 :) 15:29:02 Until the next release? 15:29:08 it's the .tpf file format. 15:29:18 On the first deployment. 15:29:19 @type torperf 1.0 or whatever. 15:29:38 yes, but where would we label it as beta? 15:30:05 Would it hurt to change the version? 15:30:16 or type ? 15:30:38 changing the type would break metrics-lib, for example. 15:31:07 changing the version might break, too. 15:31:10 hmm, 15:31:25 it's different data. 15:31:55 we didn't consider this in the beginning. 15:32:00 yeah.. 15:32:05 but, actually it is different and 15:32:11 it's different data using the same data format. 15:32:16 should be marked as such. 15:32:16 * irl appears slightly late 15:32:27 so that existing tools can use it without change. 15:32:32 hi irl! 15:32:39 okay, needs more thoughts. 15:32:47 third ticket. 15:32:56 we'll continue debugging onionperf while we think about that. 15:33:03 yep. 15:33:13 okay, moving on? 15:33:18 sure 15:33:23 - tech report (iwakeh) 15:33:30 just before tech reports 15:33:35 ok 15:33:50 i'll say that tomorrow i'm writing a paper and for breaks i'll be merging atlas patches 15:33:56 hehe 15:34:03 because writing a paper is not fun but atlas patches can be 15:34:21 sounds great! and good luck with the non-fun part of that! 15:34:25 but nothing is currently a question, it's just merging patches 15:34:41 sorry i missed the actual atlas slot 15:34:52 no worries. thanks for the update. :) 15:34:55 (: 15:35:11 iwakeh: over to you 15:35:17 thanks :-) 15:35:34 I'll mail some reading material tomorrow and 15:35:56 just put 'TODO' on the roughest edges. 15:36:04 sounds good! 15:36:19 what's the plan for mailing the draft to others? 15:36:19 I'll keep it below 40 p. 15:36:25 including AMS attendees? 15:36:50 Maybe we plan that after you 15:36:59 read something more? 15:37:17 Would be a good goal. 15:37:23 yep. my hope is that we can maybe send it out on monday. 15:37:32 could be an internal list. 15:37:52 but it would be good to have it for discussions in AMS. 15:38:02 definitely 15:38:06 "didn't you read the bottom of page 37??? out here!!!" 15:38:18 okay, cool! 15:38:31 well, maybe I add even more for obfuscation. 15:38:42 ;-) 15:38:44 heh 15:38:53 okay, moving on? 15:39:00 fine. 15:39:01 (nothing for the (...) part) 15:39:07 - AMS preparation (karsten) 15:39:27 https://people.torproject.org/~karsten/volatile/open-metrics-tickets-2017-03-13.pdf 15:39:34 always good to start with a graph.. 15:39:43 I looked at open tickets earlier this week. 15:39:59 this is one thing I'd like to talk about in AMS: 15:40:03 oh, well but this is a bit like comparing apples and skyscrapers ... 15:40:18 yeah, had to start somewhere. 15:40:24 true 15:40:45 I'd like to talk about the future of some components there. 15:40:55 like Analysis and Censorship analysis. 15:41:05 what's the difference? 15:41:09 and also Compass, and whether this is in scope. 15:41:35 Makes sense 15:41:37 I think CA is just a bit more specific than A. 15:41:48 like CA is not really metrics only, 15:41:56 it is based on tor metrics. 15:42:12 tbh, I haven't looked much at those tickets. 15:42:30 It's somewhat about possible 15:42:35 another goal would be to close more tickets. 15:42:36 censorship events. 15:42:45 always fine. 15:42:47 yes, it is. 15:42:59 perphaps I can also help here. :) 15:43:09 like focusing on defects and assigning enhancements to milestones. 15:43:15 please do, Samdney. :) 15:43:42 or did you mean help in AMS? 15:43:47 defects need milestones too 15:43:49 both 15:44:26 we should talk in AMS, where I can help. ;) 15:44:31 Could we do that in the meeting in AMS. 15:44:33 okay! 15:44:44 I mean the ticketing related things. 15:44:56 yes, let's talk more about this in AMS. 15:45:01 Many tickets are context for each other or need context. 15:45:18 and the general development idea in the background 15:45:57 okay, let's talk more about this in AMS. I don't yet know how much time we'll have for this on the 23rd/24th. 15:46:12 During dinner? 15:46:13 but maybe it's enough to get started and continue the more detailed discussion after AMS. 15:46:16 hehe 15:46:27 :) 15:46:41 right. 15:46:43 another topic: 15:46:47 operation of metrics services. 15:47:08 my hope is that none of them will break while I'm in AMS. 15:47:15 yes 15:47:23 or that our collector sync strategy prevents any major problems. 15:47:33 what could possibly go wrong. 15:47:49 well, if the main collector goes away there two others. 15:47:51 and of course I'll deploy the new version just in time before departing. 15:48:08 right. 15:48:11 well, life is a risk. 15:48:37 heh, yes. but maybe we can come up with a better plan. 15:48:43 for the future. 15:48:59 okay, I don't have a nice graph for that one, sorry. 15:49:03 didn't we plan that at the beginning of the year? 15:49:07 what else should we prepare? 15:49:09 yep. 15:49:15 for ams? 15:49:18 for our berlin meeting. 15:49:29 when? 15:49:35 the one that didn't happen. 15:49:59 ah, ok. 15:50:00 so, yes, we'll discuss this in AMS. 15:50:18 what else? 15:50:50 the changes coming up 15:51:06 which changes? 15:51:09 from what will be implemented from the tech report. 15:51:14 oh, yes. 15:51:52 sounds good. 15:52:18 - OnionPerf second user model 15:52:25 maybe we'll just use the onion service measurements. 15:52:31 we should talk to rob about that. 15:52:39 yes. 15:53:07 okay. 15:53:23 if something else comes up for AMS, let's use the mailing list. 15:53:41 fine. 15:53:46 next week there won't be an irc meeting. 15:54:14 seems like we're done for today. :) 15:54:23 ok. 15:54:39 alright. thanks, everyone! :) 15:54:47 Bye! 15:54:50 bye, bye! 15:54:53 see most of you next week in AMS! bye. 15:54:58 bye! 15:55:04 #endmeeting