14:59:20 #startmeeting metrics team meeting 14:59:20 Meeting started Thu Aug 20 14:59:20 2020 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:59:20 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:59:55 first meeting after a few weeks. yay! 15:00:06 I added some topics to the agenda. feel free to add more. 15:01:44 maybe let's just start with the agenda and add more topics to the end, in case something comes up. 15:01:51 OnionPerf 0.6 release, new op-??4 instances, turning off op-??3 instances 15:02:09 so, onionperf 0.6 is out and running. 15:02:23 I sent mail about that to the team mailing list. 15:02:30 nice! 15:03:05 I'll turn off op-??3 instances this week. unless there's a reason to keep them running? 15:03:42 if there is, please let me know. 15:03:58 hmm, I don't recall seeing an email about this 15:04:03 oh. 15:04:33 https://lists.torproject.org/pipermail/metrics-team/2020-August/001154.html 15:04:44 just a few days ago. 15:05:19 ...makes sense, looks like I'm not subscribed 15:05:24 thank you for the link 15:05:25 oh! 15:05:35 sure. feel free to subscribe. :) 15:05:53 better late than never :D 15:05:56 heh 15:05:59 okay, moving on: 15:06:03 Moving op-hk? to AWS, possibly more in the future 15:06:25 we're going to lose our hong kong hosting in a few weeks from now. 15:06:41 the idea is to setup a new one in aws 15:06:46 for now only for hk 15:07:00 in fact, the reason why we have an op-hk4 now is that it's really op-hk2 with a changed hostname. they don't let us start new instances in hong kong anymore. 15:07:29 right. I'm going to start a new instance on AWS soon. 15:07:59 if we stick to the monthly release cycle, it might make sense to wait for 0.7 to be released and deploy that as op-hk5. 15:08:12 would be interesting to see how the aws instance compares to the greenhost one 15:08:15 along with op-nl5 and op-us5 on the current hoster. 15:08:59 yes, good point. I think we'll learn that even with the 0.7 changes. 15:09:17 none of them should affect default behavior. unless I'm overlooking something. 15:09:22 yes 15:09:50 great. so, I'll start the new AWS hong kong instance in ~1.5 weeks from now. 15:09:59 that gives us a few weeks for figuring out any issues. 15:11:12 okay. 15:11:15 updated the pad. 15:11:25 now, shall we talk about the roadmap? 15:11:39 IIRC, our current roadmap ends in 1 week. 15:11:51 and we only have 6 issues left on our board. 15:12:07 I went through these 6 issues and made notes what remains to be done. 15:12:20 and how much time that remaining work would take us. 15:12:40 shall we go through these 6 issues together? 15:12:56 works for me 15:12:58 the estimates are ok on my end 15:13:13 sounds good 15:13:39 okay! 15:13:40 tpo/metrics/onionperf#33432 15:14:08 phw, does the pad make sense regarding this issue? 15:14:31 should we estimate more hours for finishing this? 15:14:38 yes, makes sense 15:14:49 okay! 15:14:55 i think 1h is fine. maybe 2h to be conservative 15:14:59 (for you) 15:15:14 changed. 15:15:23 tpo/metrics/onionperf#33420 15:15:45 I added a long comment to that one yesterday. 15:16:06 I guess reading through that comment and the rest of the ticket and thinking about all of that is going to take an hour. :) 15:16:30 if that plan makes sense, doing just step 1 there will be relatively fast. 15:16:44 maybe we should ask mikeperry about this one, too. 15:17:17 should I do that? 15:18:11 silence means yes here. I'll to that. :) 15:18:14 i think i lack the context to have something useful to say here 15:18:29 yes, it takes quite a while to get the necessary context for this. 15:18:31 same 15:18:32 yes 15:18:33 okay. 15:18:39 mikeperry is afk but will be back in a week 15:18:48 ah. 15:19:25 then this won't make it into 0.7. should be fine, though. 15:19:44 actually he should be back on monday 15:19:49 aha! 15:19:51 * gaba just looked at the calendar 15:19:52 then it might work. 15:19:57 ha, ok 15:19:57 I'll ask him. 15:20:00 sounds good 15:20:04 tpo/metrics/onionperf#33260 15:20:20 acute and I discussed a trillion alternatives for a good user interface extension there. 15:20:38 current state is that it needs review and careful consideration. 15:20:51 I really like separating the filtering step 15:20:54 oh, and some coding on my side. 15:20:59 also I've started the review, there will be a couple of small revisions 15:21:01 great! 15:21:11 sounds good! 15:21:35 tpo/metrics/onionperf#40001 15:22:17 I'll need to sit down to do this. it just takes a block of 4 undisturbed hours, or it won't work out as well. 15:22:31 then it will need review and discussion. 15:22:36 but, all doable. 15:23:00 tpo/metrics/onionperf#34231 15:23:15 ah, I have some wip for this one :) 15:23:20 nice! 15:23:44 if you have something for review, I'll happily take a look! 15:23:56 excellent, thank you! 15:24:21 finally, tpo/metrics/onionperf#33421 15:24:39 I added some next steps to that issue before this meeting. 15:24:42 it's ... a project. 15:25:26 which is why I moved this to the end of the list. maybe we'll have to move part of this to the next roadmap month. 15:25:59 okay. 15:26:02 ok 15:26:13 anything else on these issues? (or others?) 15:26:46 nothing from me. 15:27:00 nothing from me 15:27:04 karsten: do you have any preferences on what i should be working on after #33432 is done? 15:28:17 well, how much do you know about how tor uses guards? 15:28:33 I briefly looked at the spec and the tor logs there, and it's non trivial (to me). 15:28:54 this is related to the first step of tpo/metrics/onionperf#33421 15:29:32 i'd probably have to do some reading before getting started 15:30:38 okay. feel free to also look around at the other issues and see whether they would be a better fit. 15:30:49 okay, i will 15:31:02 perfect. thanks! 15:31:19 anything else for today's meeting? 15:32:17 nothing from me 15:32:36 same 15:32:45 if not, thank you, everyone, and talk to you next week! :) 15:32:53 bye! o/ 15:33:02 bye! o/ 15:33:18 o/ 15:33:29 #endmeeting