14:32:48 #startmeeting metrics team 14:32:48 Meeting started Thu Jul 27 14:32:48 2017 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:32:48 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:33:02 (sorry to interrupt, nickm, asn, dgoulet!) 14:33:22 np 14:33:52 https://storm.torproject.org/shared/Ou-1QRctynWbF4yedi-MfDsjImFMFSIEP20fbVGCPRa <- agenda pad 14:35:15 iwakeh: alright, shall we start? 14:35:23 yep. 14:35:32 * Onionoo backend 14:35:38 I hear we have a new host. 14:35:46 I didn't log in yet. 14:36:02 ah, ok. 14:36:09 it's supposed to be a second back-end host that runs the hourly updater. 14:36:36 it should ideally produce the exact same data. but that might not always work out. 14:37:04 still, a good opportunity to remove any inconsistencies between two onionoo instances. 14:37:08 well, we had differences before. 14:37:11 and a big plus in robustness. 14:37:20 yes. 14:37:33 yes, I think there are open tickets for differences. 14:37:51 but, not the end of the world if something's slightly off. 14:38:24 okay, how do we set this up? would you want to give that a try some time next week? 14:38:25 no, another backend is an improvement. 14:38:29 regardless. 14:38:35 agreed. 14:38:52 sure, I can give it a try. 14:39:10 cool! do you already have access to omeiense? 14:39:21 not that I'm aware of. 14:40:00 ah, indeed. 14:40:05 so, we need to fix that first. 14:40:08 I'll create a ticket. 14:40:15 ok. 14:41:05 I think step 1 would then be to log into the new host and set up a new onionoo instance, without any historic data. 14:41:27 and maybe even keep that running for a day to figure out whether there are any issues. 14:41:36 fine, I'll start a list about operation like for CollecTor. 14:41:52 the next step would be to copy over the status/ and out/ directories from the primary instance. 14:41:57 (starting a list sounds good!) 14:42:02 well, it's only updates yet for collector. 14:42:31 shouldn't these be copied first? 14:42:34 in order to copy them, we'll have to stop the hourly updater, create tarballs, restart the hourly updater, copy over tarballs, and get it running on the other side. 14:42:44 the issue is that they age quite fast. 14:42:58 if it takes a few days to figure out any issues, we'll have to copy it once again. 14:43:05 72 hours in collector's recent/. 14:44:30 I mean, we could also schedule the copy for a time after which you have enough time to look into any issues. 14:44:38 which might not be friday afternoon. ;) 14:44:44 hehe 14:44:56 what's your preference? 14:45:14 hmm, hard to tell as I've not done it before ... 14:45:26 better start from scratch and copy later. 14:45:31 okay, I'd suggest to start from scratch. ok! 14:46:16 all else by mail? and trac ticket? 14:46:51 yep. we first need you in the onionoo group anyway. 14:47:00 true. 14:47:11 okay, I put a rough plan on the pad. 14:47:16 next topic? 14:47:21 fine. 14:47:29 * CollecTor 1.3.0 (Webstats) release 14:47:44 my inbox is my enemy. what tickets should I be looking at? 14:47:46 actually, metrics-lib is the basis for this. 14:47:56 ah, so metrics-lib 2.1.0 first? 14:47:57 #22428 14:48:30 its only a few changes here as most is in metrics-lib 2.1.0 14:48:55 #22983 14:49:25 this adds the new descriptor types, but changes very little on existing code. 14:49:49 okay. what's the schedule here? end of july is so close.. 14:49:55 and also features tests for the new descriptors. 14:50:09 true, 14:50:37 though I could probably review two tickets and do a pre-release tomorrow. 14:50:41 would that help? 14:50:51 (for metrics-lib 2.1.0) 14:50:56 fine. 14:51:02 that is most of it. 14:51:15 there are only few changes in collector then. 14:51:26 it builds on the new functionality. 14:51:40 and then we put out collector 1.3.0 on monday? 14:51:52 fine. 14:52:34 that way I 14:53:22 could do some more testing, but it imports fine. 14:53:40 okay. 14:53:48 would be cool to get this done in july. 14:53:51 as planned. :) 14:53:56 yep :-) 14:54:05 could you also 14:54:37 review this #22912 14:54:59 on the list. 14:54:59 I added it to 2.1.0 as it will be needed for 14:55:09 ah, fine :-) 14:55:21 just two tickets for 2.1.0 14:55:28 and one for collector 1.3.0 14:55:34 ok. 14:55:39 but they are big enough. 14:56:08 okay, sounds like we have a plan. 14:56:14 next topic? 14:56:16 yep. 14:56:20 * sanitized bridge descriptor spec 14:56:29 regarding how to proceed. 14:56:29 I noticed your comment. 14:56:40 I though it's easier to discuss that here. 14:56:47 yes, true 14:56:49 not the details about the spec, but where to put it. 14:57:23 we could put it on the third level, as in: Home >> Sources >> Tor Bridge Descriptors. 14:57:30 which would be in parallel to collector. 14:57:45 we don't really have a fourth level. 14:57:54 you mean in section 14:57:56 https://metrics.torproject.org/sources.html#main 14:58:14 as Specifications 14:58:52 to start with, yes. 14:59:05 well, then we have a place. 14:59:18 and the collector page would link to that. 14:59:39 we'd probably take out most of the details about tor bridge descriptors from the collector page, 14:59:51 because we should avoid keeping two copies of those details. 14:59:59 un-clutter is always good. 15:00:15 okay. :) 15:01:24 there, plan added to the pad. 15:01:32 the remaining parts can stay in trac. 15:01:41 ok 15:01:43 ah, one more topic: 15:01:53 * MOSS final report 15:02:03 you raised a good point there regarding deliverable 4. 15:02:13 there's now an edited version that needs approval. 15:02:18 from you and/or isabela. 15:02:25 yes, I have that on my list. 15:02:32 want to take another look and.... perfect! 15:03:14 alright. 15:03:23 nothing in my inbox stands out as super urgent. 15:03:30 fine :-) 15:04:03 okay, cool, we made good plans. let's execute them! :) 15:04:13 thanks and bye! 15:04:14 back to work! 15:04:16 heh 15:04:25 thanks, and bye, bye. 15:04:30 #endmeeting