14:29:34 #startmeeting metrics team 14:29:34 Meeting started Thu Oct 26 14:29:34 2017 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:29:34 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:29:37 hello! 14:30:02 hello 14:30:09 hi irl! 14:30:31 iwakeh: ping 14:31:51 irl: we'll need iwakeh for the first topic. should we start with the atlas/onionoo topic? 14:31:58 we can do 14:32:09 * plan for implementing aggregations in Atlas (#23517, #23509) 14:32:12 Hi there! 14:32:19 hi! :) 14:32:26 hi iwakeh (: 14:32:33 :-) 14:32:47 so, my plan there was to keep using compass with a JSON interface, 14:33:00 and implement this in onionoo later. 14:33:10 I'm not sure if that's a good plan, though. 14:33:15 my thoughts are that onionoo already has all the data required to do compass things 14:33:31 true. 14:33:35 what speaks against? 14:33:41 it doesn't mean adding extra data, just a new document type with some aggregations in it 14:34:03 i'm not exactly certain what that document would look like yet 14:34:04 it's just a very different kind of operation that onionoo would do. 14:34:17 the aggregation part. 14:34:24 it is a lot more logic than i imagine is in existing document generation 14:34:31 but it's mostly just adding numbers together 14:34:38 and filtering 14:34:51 java streams could be great at this 14:34:57 maybe 14:34:58 What timeframe do we have? 14:35:23 it's an M in the short-term list 14:35:23 I assume, the step to let compass provide JSON is small. 14:35:25 well, we said Q4/2017, but we can easily say Q3/2018. 14:35:37 iwakeh: yep. 14:35:51 So, let's do this interim 14:36:08 and also decide what to do next. I also 14:36:32 think that another JSON document from Onionoo seems ok. 14:37:00 it's a question of how much effort we want to put into this now. 14:37:11 maybe this is easier after switching to a datbase. 14:37:13 database* 14:37:16 From 10000 feet: Onionoo is a JSON service. 14:37:22 not doing it in onionoo does mean that we can't shut down compass 14:37:40 irl: true. 14:37:40 We're first reducing compass at least. 14:37:41 and it would mean we can't advertise this to other users, as we do onionoo 14:37:48 because we're only going to break it anyway 14:38:03 okay. 14:38:14 maybe we can't decide this today. 14:38:18 We'd need to define the JSON doc? 14:38:27 yep 14:38:52 That would stay the same being transferred to onionoo. 14:39:01 right. 14:39:13 if we call the compass implementation a prototype, then i'm happier 14:39:14 so, we wouldn't break, just redirect. 14:39:21 fine. 14:39:38 it would be actually good, to find out the right JSON format. 14:39:51 maybe we should start with the doc. 14:39:57 think about what we need. 14:39:57 right. 14:40:08 How much code is already existing? 14:40:12 and then either do it by changing the existing compass a bit or by implementing it in onionoo. 14:40:24 how much compass code? 14:40:31 the aggregation code already exists in python 14:40:32 yes 14:40:46 but we need to swap out the html template for a jsonify 14:40:53 let's start with the doc and look further then. 14:40:57 ok 14:41:00 ok. 14:41:32 alright, let's talk about the most important topic for today. 14:41:48 most important, because we need to finish it today. 14:41:51 it == roadmap 14:41:57 * roadmap (karsten) 14:42:04 I read the mail thread and postponed my reply to here. 14:42:12 after this meeting we need to share our roadmap with the other teams. 14:42:26 let's discuss all open points now. 14:42:27 which is, I'm fine with the recent suggestions. 14:42:31 cool! 14:42:48 I also added (XY team might care) 14:43:06 so that the other teams can look out for whatever parts they should be reading. 14:43:06 XY? 14:43:18 XY = network, applications, ooni, etc. 14:43:26 Switch ExoneraTor and metrics-web from Tomcat to embedded Jetty, and harmonize directory structures (M) (admin team might care) 14:43:58 how about we go through the open suggestions on the doc? 14:44:03 and change/approve them. 14:44:21 ok. 14:44:35 Make Compass part of Atlas in order to provide aggregated search results and details pages on Atlas and to finally shut down Compass (M) 14:44:37 oh hang on "make a plan" turned into "do a thing" 14:44:41 yes. 14:44:47 (UX team might care) 14:44:59 (that was part of the paste) 14:45:17 so i can't really start on compass until atlas is merged into the website 14:45:28 because otherwise i'm maintaining two atlases 14:45:32 note that we don't have to complete this by end of 2017. 14:45:39 ah ok 14:45:43 The following list contains all goals that we‘d like to start or even complete within the remaining months of 2017. 14:45:44 * irl got scared 14:45:56 yes, starting it is ok 14:46:08 there's no way how we can finish 12 M tasks in 2017 and another 15 M tasks in Q1-Q3/2018. 14:46:21 true 14:46:33 maybe underline 'start' ;-) 14:46:36 hehe 14:46:59 let's just point at it if somebody is disappointed later. ;) 14:47:06 (: 14:47:16 so, is that one good to go in? 14:47:20 yep, smallprint. 14:47:24 heh 14:47:31 yes, that one is good 14:47:47 fine. 14:48:03 the next one is a format suggestion: 14:48:11 do we really need the ongoing and on-demand goals category? 14:48:24 it made more sense when there were more goals under that. 14:48:47 but I could imagine just merging those goals with medium-term goals. 14:48:50 what do you think? 14:48:53 i think it's good to keep some text that says that there are ongoing and on-demand tasks 14:48:59 but it doesn't need to be a seperate section 14:49:07 right. 14:49:22 want to edit the text under medium-term goals? 14:49:27 edit/extend? 14:49:53 or should we just copy over everything? 14:49:57 or, simply remove the additional headline? 14:50:19 keep: 'We realize ..." 14:50:20 yes, but then we should also put the goals under the categories. 14:50:26 above. 14:50:39 made a suggestion 14:50:52 with that, drop the headline and move the below tasks above 14:51:26 yes. 14:51:34 how about that? 14:53:33 looks good to me. 14:53:49 me too 14:54:11 ah, no, those goals are 12M and we reserve 3M 14:54:24 that works too 14:54:39 ok. 14:55:45 looks a bit easier to understand. 14:55:52 indeed 14:55:53 next one is onionoo and votes. 14:56:31 as agreed before. 14:56:54 and we have two more that I think we agreed on before. 14:57:03 in the long-term list, so what could go wrong. 14:57:29 yes. 14:57:33 looks good 14:57:39 okay! 14:57:57 I think that's it. 14:58:05 yep! 14:58:10 we should share it with the other teams. 14:58:25 which will share their roadmaps with us. 14:58:27 don't forget to remove the notes below. 14:58:35 other than that fine. 14:58:47 , 14:58:57 yes, will do. that is, print only pages 1--8 to a pdf. 14:59:17 next step after that: we might receive feedback. 14:59:20 from other teams. 14:59:29 either things they need us to do or do differently, 14:59:47 or from other teams' roadmaps saying what else we need to be involved in. 15:00:36 maybe, just remove the next steps? 15:00:43 yes, that's what I just thought, too. 15:00:55 it's isabela's process that we'll follow. 15:00:56 they're not actually part of the roadmap. 15:01:03 not next steps we need to keep in mind ourselves. 15:01:19 the roadmap will still be in a draft state for another few weeks. 15:01:28 but not because we need more time to think about goals. 15:01:29 good! 15:01:47 so, I'll remove next steps? 15:02:00 we did all the steps 15:02:04 they're previous steps now 15:02:11 yep! 15:02:14 true 15:02:21 okay, removing. 15:02:59 great! that's this agenda topic then. 15:03:06 moving to the next? 15:03:11 +1 15:03:15 * robustness for collector and onionoo 15:03:35 - Extend Onionoo's nagios script to all known frontends (#23984) 15:03:38 - Are there other things we should monitor? 15:03:42 there are. 15:03:45 who will work on the nagios script? 15:03:49 fine question. 15:04:04 the nagios script looks simple enough 15:04:10 where the first step might be to make a list of all the things we want to be notified about. 15:04:17 ah, the onionoo one. 15:04:18 yes 15:04:49 checking the other onionoo frontends is just one step towards making that check even better. 15:04:53 it has been very useful in the past. 15:05:05 but there are 20 other things we should be checking automatically. 15:05:21 we even have a roadmap item for this: Deploy better notification system for operational issues (M) (admin team might care) 15:05:48 i was thinking we probably have enough systems to monitor it would justify us having our own monitoring system 15:06:02 should we hold a pad meeting to brainstorm possible things to monitor? 15:06:07 yes. 15:06:10 ok 15:06:19 irl: what's the advantage over using tor's nagios? 15:06:32 karsten: i can't add checks to tor's nagios 15:06:52 there are parts only the tor system has access to, like filesystem etc. 15:07:05 I can't do that either, but we can ask the admins to do it for us. 15:07:51 ok, let's make a list first and see what it is we need to monitor 15:07:55 sounds good. 15:07:59 fine. 15:08:05 how about mid next week? 15:08:21 fine for me. 15:08:24 maybe before the team meeting? 15:08:49 or wednesday to make it a separate thing? 15:08:55 wednesday is good for me 15:09:01 thursday is my meetings day, i have no extra room 15:09:08 ah! :) 15:09:12 I don't have a preference, either is fine. 15:09:20 let's do it wednesday then. 15:09:26 same time as this meeting? 15:09:34 (daylight ends this weekend) 15:09:46 (or saving of) 15:09:48 finally back to normal ;-) 15:10:04 sounds good 15:10:13 this meeting is defined in terms of UTC? 15:10:22 14:30UTC 15:10:26 yep. 15:10:39 cool 15:11:03 great! 15:11:16 next topic? 15:11:25 yes. 15:11:30 * onionoo release 15:11:39 that would be the hotfix release. 15:11:44 still testing. 15:12:02 #24012 15:12:04 okay. 15:12:22 I can create a pre-release tarball this evening. 15:12:28 trying to find the reason for illegalstateexc. 15:12:32 ! 15:12:49 if you can't find it anymore, that's fine. 15:12:52 when would you need the ok for the branch or patch? 15:12:57 we can always put out another patch release if needed. 15:13:05 true. 15:13:25 3 hours from now? 15:13:25 deployment, when? 15:13:43 tomorrow at 10:00 cest? 15:14:07 ok for both. 15:14:31 great! 15:14:37 there's also a bug in metrics-web. 15:14:45 preventing it from updating. 15:15:00 did you find the reason? 15:15:30 I have a patch. I just don't know why the test does not finish. 15:15:53 so, might take longer than today to fix it. 15:16:13 ok. 15:16:27 ah, speaking of onionoo, 15:16:35 how's your review queue these days? 15:16:53 there are a couple of relatively small onionoo patches in needs_review. 15:16:55 depends 15:17:01 ok. 15:17:03 ah, ok. 15:17:06 not urgent. 15:17:40 I take the onionoo reviews on first then. 15:17:50 cool! 15:18:06 I think we're done. 15:18:19 unless there's more to discuss? 15:18:26 I'm fine. 15:18:29 i think that's all 15:18:37 great. thank you! 15:18:50 bye, bye! 15:18:52 Thanks! And, bye, bye! 15:19:50 #endmeeting