14:29:45 #startmeeting metrics team 14:29:45 Meeting started Thu Aug 16 14:29:45 2018 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:29:45 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:30:11 we already have a few topics. should we add more before we start? 14:30:30 i did not have any other topics 14:30:34 okay. 14:30:39 * Onionoo 6.2-1.17.0 deployment vs. 6.2-1.17.1 release (#27163) and deployment (karsten) 14:30:50 I saw your last comment after adding this topic. 14:31:04 so, should we postpone deployment until tomorrow? 14:31:20 yes, i don't want to rush considering which other tests may be missing 14:31:27 makes sense! 14:31:40 but it also doesn't make as much sense to deploy today and once again tomorrow. 14:31:45 so, postponed, I'd say. 14:32:02 ok 14:32:08 * Onionoo tickets from last week's questions (irl) 14:32:17 I found those questions on the pad. 14:32:23 did you want to create tickets for them? 14:32:42 otherwise we can carry them over to today's notes. 14:32:58 i was trying to work out what those tickets were before i created them 14:33:07 sounds good, too. 14:33:15 essentially we want to be in a place where if there are no new files then nothing should be written to disk 14:33:39 i've been looking already at making sure nodestatus is deterministic, but i've not yet looked at detailsstatus 14:34:02 we can carry those notes over here and i will think about it more 14:34:09 okay, great. 14:34:44 reordered the next two. 14:34:45 * Reconfigure collector2.tp.o (#27076) (karsten) 14:34:59 just a friendly reminder. 14:35:28 it's a lot of text, but I think it's not a hard decision. 14:35:35 unless I overlooked something. 14:36:12 i think we can make this change 14:36:35 okay. can you comment on the ticket? 14:36:51 i plan to be setting up a collector at the university, which would sync, so we would still notice if that functionality breaks 14:37:01 sounds good! 14:37:09 hi y'all, just wanted to mention that I'm here and it's my first time at a Tor meeting. I'm interested specifically in the metrics team. 14:37:30 hi nevro! 14:37:39 welcome. :) 14:37:47 hi nevro (: 14:37:56 thank you, karsten! I've been reading several of your papers over the past week or so, so it's great to meet you! 14:38:02 hi irl :) 14:39:12 cool! flexlibris mentioned that you might join us today. she also mentioned that you might be interested in volunteering. 14:39:37 do you want to watch the remaining few topics on the agenda, and then we talk about the volunteering part? 14:39:44 sounds like a plan! 14:39:50 btw, I did not paste the agenda link here... 14:40:09 https://storm.torproject.org/shared/5h1Goax5eNusxjXJ_Ty5Wl7hFR1uqCReUiN8xdlBG8T <- agenda pad 14:40:13 okay, great! 14:40:26 glad you're here nevro :) 14:40:44 hi flexlibris! thanks for making the introduction. :) 14:40:55 happy to :) 14:41:10 okay, I think that's all for #27076. 14:41:13 next is: 14:41:15 * Remote database dump (karsten) 14:41:28 so, I'm just curious if there's a better way to do this: 14:41:50 I'm currently dumping the exonerator database via ssh. 14:42:01 the reason is that I'd want to try to optimize it. 14:42:25 the thing is, it's 260G large on the server, and there's no way to dump it to the disk there. 14:42:47 that's why I'm using ssh with a command and piping the output into a local file. 14:43:06 it's running for hours now. is there a smarter way to do this? 14:43:19 ssh materculae "pg_dump -U exonerator -h localhost -Fc" > exonerator-2018-08-16.sql 14:43:23 is what I'm doing now. 14:43:33 have postgres data directory in a zfs dataset 14:43:44 periodically make snapshots and do zfs send recv over ssh 14:44:05 probably this won't work though 14:44:11 because we don't have zfs 14:44:15 right. 14:44:26 do you do this often? 14:44:35 every couple of years. 14:44:43 oh, then just run it over ssh 14:44:49 this is probably not worth optimising 14:44:52 but, if it's easier, I'd probably do it more often. 14:45:13 i think the only optimisations i can think of involve having things updated every hour at least 14:45:33 either live replication, or something with filesystem snapshots 14:45:48 but longer periods of time maybe the diffs turn into transferring everything anyway 14:46:00 hmm, ok. 14:46:03 this is very similar to the problem with onionoo 14:46:08 true. 14:46:11 there's not enough local disk space to make a copy of the status directory 14:46:16 :( 14:46:19 so getting a consistent copy of it is impossible 14:46:22 not even compressed? 14:46:47 i didn't try that, but that's a lot of cpu time still 14:47:22 so, okay, not something we can solve easily today. 14:47:27 nope 14:47:29 but 14:47:32 I'll keep the ssh running then. 14:47:36 when i get these test instances up at the university 14:47:39 they would have zfs storage 14:47:44 and we can experiment with this 14:47:50 sounds good. 14:48:07 okay, last topic on the agenda: 14:48:09 * Roadmap change: complete 13, defer 18, resume subset of 1, 3, 9, 12, 15 (karsten) 14:48:17 let me explain. 14:48:34 I don't think we can make much progress on 18 before mexico city. 14:48:59 on the other hand, I could imagine that we finish 13. 14:49:13 and then we could resume some of the tasks we deferred earlier. 14:49:26 just to burn down the burndown chart. 14:49:46 and to not to have to add these partial tasks to the next roadmap. 14:50:02 because we still want to do them. they're useful. 14:50:26 I was thinking about picking up 9 and 1. 14:50:39 and I was wondering whether you'd want to pick up 3 and/or 12. 14:51:04 i guess 12 is part of #24422 14:51:12 right. 14:51:14 yes, 3 and 12 look like things i can do 14:51:28 i was actually earlier this week talking with ux team about progressing that 14:51:35 neat! 14:52:13 okay, sounds like a good new plan then. 14:52:36 I'll not update the roadmap just yet but save that for the next meeting, if that's okay. 14:52:47 i may not be here for the next meeting 14:52:49 but yes, this is ok 14:52:50 just in case you or I figure out that there are obstacles we didn't see now. 14:53:04 or the meeting in 2 weeks. 14:53:16 yep ok 14:53:30 so, regarding next week, 14:53:47 although i may also not be at that one because i'll be on a train 14:53:50 (in two weeks) 14:53:52 do you have branches open that are changing major parts of a codebase? 14:54:04 i do not have any major changes open, no 14:54:04 we can pick a different date for that meeting then. 14:54:42 okay. then I'd just go ahead and make larger changes to the codebases if necessary. 14:54:45 we could do a meeting on monday 27th? i'll be just back from sigcomm then would have tues+wed before going to emf 14:54:55 like, change logging or date/time types, etc. 14:55:02 yes that's ok, no problem 14:55:12 27th sounds fine to me. 14:55:29 14:30utc? 14:55:50 sure. 14:56:07 cool 14:56:21 great! 14:56:25 nevro: still around? 14:56:29 yup! 14:56:44 very cool that you're going to sigcomm irl 14:57:40 so, when flexlibris mentioned your interest in metrics things I came up with two quick ideas where we need help. 14:58:03 they are both related to our roadmap item 13 that we just said we'd complete by the end of september. 14:58:09 * karsten finds a link 14:58:28 https://trac.torproject.org/projects/tor/wiki/org/teams/MetricsTeam#Research 14:58:59 we recently finished two documents that are supposed to help folks understand better what we're doing. 14:59:05 https://metrics.torproject.org/reproducible-metrics.html 14:59:10 https://metrics.torproject.org/stats.html 15:00:02 you're new to most of this stuff, so I wonder if you'd like to take a look at those and tell us whether they make any sense to you. 15:01:12 did I just successfully overload you with information? :) 15:01:28 I've seen both of these, as flexlibris mentioned them to me. /stats.html is straightforward in the sense that it gives an overview of each of the graphs on the metrics page. That all was rather easy to go through. 15:01:38 okay, cool! 15:01:47 The other page on the other hand, a tad bit more convoluted 15:02:24 I'm not exactly sure who the intended reader is though. Like is it much of a problem if I cannot easily read the reproducible metrics page? 15:02:58 well, we should attempt to fix that. 15:03:19 I'd be curious which parts are hardest to understand. 15:03:50 Sure, so one thing I can do is go through it and make notes? 15:04:05 that would be very useful. and add questions. 15:04:14 Great, yeah, I can do that! 15:04:39 awesome! that would be really cool. 15:05:15 is that what you had expected when talking about volunteering? or did you expect to hack on something? maybe we could find something else, just in case this turns out to be less fun than expected. 15:05:45 Well, before I do anything, I need to understand how all of this works under the hood. I think this is a great first task. 15:05:53 okay, great! 15:05:54 I admit that it's all very intimidating. 15:06:06 But eventually, I would like to get my hands a bit dirtier. This is a great way to start imo 15:06:08 let's fix that, too. :) 15:06:16 okay! 15:06:20 ty :) 15:06:43 so, next meeting is on the 27th, as you might have seen earlier. 15:06:52 I'll send out another reminder to the team list. 15:07:07 if you have anything until then, just post to the team list. 15:07:25 or create a ticket in one of the Metrics/* components. 15:07:50 okay. I think that's all for today. unless there's more. 15:08:10 by the way, pg_dump just finished. I have a 52G file here now. hope it works. 15:08:40 (: 15:08:48 alright. ending the meeting. thanks, irl and nevro! talk to you in 11 days. bye! 15:08:53 bye! 15:08:54 bye bye! 15:08:59 #endmeeting