15:59:45 <GeKo> #startmeeting network-health  2024-01-22
15:59:45 <MeetBot> Meeting started Mon Jan 22 15:59:45 2024 UTC.  The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:59:45 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:59:52 <hiro> o/
16:00:07 <GeKo> we have our pad
16:00:22 <GeKo> over at https://pad.riseup.net/p/tor-nethealthteam-2023-keep
16:00:37 <GeKo> please add items to our agenda for today if you have not yet done so
16:01:03 <GeKo> ggus: juga:
16:01:42 <GeKo> mattrighetti[m]: so, hiro and i had some onionoo ticket triage sprint last week
16:01:52 <GeKo> and we just dumped a bunch of tickets over to nsa
16:01:58 <GeKo> hope you don't mind :p
16:02:09 <hiro> some of these will need some work on the parser side tho
16:02:14 <GeKo> yeah
16:02:32 <GeKo> but i guess they give a good overview about how nsa could evolve
16:02:34 <GeKo> over time
16:02:42 <mattrighetti[m]> Yep, I saw you moved a bunch of issues on nsa :) cool! Most of them are new requested features I see
16:02:46 <GeKo> even though it doesn't have to
16:02:51 <GeKo> yes, that's right
16:03:00 <GeKo> it's future-work imo
16:03:29 <juga> HI
16:03:34 <GeKo> HI
16:03:35 <hiro> I was thinking, since @mattrighetti[m] is working on a 0.3 version, that we could tag the ones that can be implemented already and leave  the ones that need parser work out
16:03:57 <GeKo> sure,sure
16:04:33 <mattrighetti[m]> Version 3 is ready to be reviews, it closes 3-4 issues I don't quite remember the exact number
16:04:49 <hiro> ah ok @mattrighetti[m] , I'll see that MR then
16:05:16 <mattrighetti[m]> This week I'm going to work on some others, like the victoria metrics data that is not returning stuff right now :/
16:05:17 <mattrighetti[m]> hiro: Did anything change for victoria metrics?
16:05:18 <GeKo> well, fine for a 0.4 or something else
16:05:35 <hiro> I'll create like a ready-to-code tag or a need parser tag so you can skim through those issues anyways
16:05:46 <hiro> and see what you feel like implementing
16:06:00 <mattrighetti[m]> makes sense, thanks!
16:08:38 <GeKo> mattrighetti[m]: anything else from your side you need help with etc.?
16:08:55 <GeKo> ggus: you around by chance?
16:08:58 <mattrighetti[m]> hiro: Did anything change for victoria metrics?
16:09:13 <hiro> uhm I do not think so @mattrighetti[m]
16:09:21 <hiro> I wonder if it is running properly
16:09:26 <hiro> let me check real quick
16:09:46 <Gus2> Hi!
16:09:53 <Gus2> I’m around now
16:10:00 <mattrighetti[m]> Yeah, I can't seem to make nsa return stuff from it, but I did not test by using curl directly against vm so...
16:10:19 <GeKo> wow a Gus2
16:10:30 <GeKo> probably an imposter :)
16:10:57 <juga> i'm getting stuff from victoria metrics right now, but querying bandwidth files and network status
16:11:12 <juga> (in case it's the same victoria metrics source)
16:11:26 <hiro> @mattrighetti[m] I see some errors in the logs... if you send me the query I can check ift
16:11:34 <hiro> s/ift/it
16:11:36 <Gus2> Very likely an imposter!
16:12:01 <mattrighetti[m]> juga, hiro: alright, then it must be something with the nsapi proxy then
16:12:30 <mattrighetti[m]> new issue popping up eheh
16:13:09 <GeKo> mattrighetti[m]: that's how we roll ;)
16:13:25 <GeKo> Gus2: okay, what first?
16:13:30 <GeKo> the meetup?
16:13:38 <hiro> this year resolution tho is less issues w metrics infra
16:13:54 <mattrighetti[m]> going to open a ticket as soon as I understand what's wrong with it, other than that I'm good!
16:14:01 <GeKo> nice
16:14:01 <hiro> thanks @mattrighetti[m]
16:14:18 <GeKo> Gus2: looking at the pad, your agenda looks good to me
16:14:34 <Gus2> GeKo: yeah, i announced the meetup on tor-relays, forum, Reddit, and i will ask comms to announce on tor socials
16:14:41 <GeKo> +1
16:15:09 <Gus2> GeKo: should we include something about the policies in general?
16:15:26 <GeKo> we could explain this new process (again)
16:15:29 <GeKo> can't hurt imo
16:15:45 <Gus2> Ok!
16:15:56 <GeKo> i think we did not send an explicit mail about that to tor-relays@ yet, right?
16:16:01 <Gus2> Now that we even have a website with all the policies
16:16:02 <GeKo> so, folks might not be aware of that
16:16:06 <GeKo> yeah
16:16:14 <GeKo> good stuff!
16:16:26 <Gus2> GeKo: about how to submit proposals? I think we did. And we also had a meetup talking about it
16:18:01 <GeKo> dunno, for some reason i always feel we missed a final announcement or something
16:18:01 <ggus> bye Gus2
16:18:10 <GeKo> it was a nice fellow!
16:18:22 <ggus> it was a chatpgt bot
16:18:39 <GeKo> good one!
16:18:44 * arma2 starts to wonder what this means for arma2
16:18:45 <ggus> GeKo: ok! we can do another announcement
16:18:46 <GeKo> felt like the real ggus
16:18:58 <juga> :)
16:19:08 <GeKo> ggus: i see your "Process for new policies and proposals for the Tor relay operator community"
16:19:14 <GeKo> from june
16:19:31 <GeKo> might be good enough
16:19:45 <GeKo> but a reminder during the meet-up can't hurt imo
16:20:22 <GeKo> ggus: okay, eol work
16:20:28 <GeKo> it seems it's time again :) :(
16:21:06 <ggus> why you want to remove all our precious bridges :(
16:21:09 <GeKo> i think we can be smarter this time and don't need to kick out all affected relays manually just to leave some of them in at the end once they fixed their stuff
16:21:20 <GeKo> no, i want them to upgrade :)
16:21:37 <GeKo> but otherwise the process will be much the same...
16:22:34 <ggus> GeKo: hm, i didn't understand the difference
16:22:55 <GeKo> ggus: i'll be out week 7, so i would start to collect eol info in the week of feb 19
16:23:10 <GeKo> in the process?
16:23:19 <ggus> yes
16:23:43 <GeKo> this time we might just get the relays rejected at the dirauth level directly
16:23:51 <GeKo> if they have not upgraded
16:24:01 <GeKo> by getting a tor release out with the respective patch
16:24:09 <ggus> ah, i see
16:24:14 <GeKo> which is ready and just sitting around for a point release
16:24:15 <ggus> sounds good
16:25:17 <GeKo> ggus: starting the work officially on 2024-02-19 sounds good for you?
16:25:27 <ggus> https://metrics.torproject.org/rs.html#aggregate/all/version:0.4.7
16:25:32 <GeKo> wanna do some social media upgrade outreach before that?
16:25:46 <GeKo> yeah, it's quite a lot of relays and bridges still on 0.4.7...
16:25:48 <ggus> GeKo: yes, feb 19 works for me
16:25:55 <GeKo> okay
16:25:57 <ggus> we can announce on social before that
16:26:04 <GeKo> thanks, please do
16:26:25 <GeKo> alright
16:26:41 <GeKo> do we have anything else we should talk about today?
16:26:55 * juga is good
16:26:59 * ggus is good
16:27:14 <mattrighetti[m]> * matt is good
16:27:19 <GeKo> hiro: i just saw https://gitlab.torproject.org/tpo/network-health/metrics/descriptorParser/-/issues/72#note_2986617
16:27:27 <hiro> yeah
16:27:45 <GeKo> i wonder whether it would be useful if you tested what we currently have in !49 and see whether the algo you have right now is an improvement
16:27:54 <GeKo> without me having finished the review
16:28:19 <GeKo> because if we see that does not solve the issue we might need to get back to the drawing board
16:28:20 <hiro> uhm
16:28:30 <GeKo> and could save us some review and rebase time
16:28:52 <hiro> you mean like a yolo deploy?
16:28:54 <GeKo> (or some better rebased version of !49, that is)
16:28:56 <GeKo> yeah
16:29:12 <GeKo> and see whether this fixes #72 theoretically
16:29:27 <hiro> uhm
16:29:34 <GeKo> i know, right? :)
16:29:44 <GeKo> i am fine if you say "no"
16:29:47 <hiro> so, I think I can fix what you mentioned for tomorrow
16:29:58 <hiro> and then open an issue for the more open questions you left
16:30:23 * ggus o/
16:30:24 <hiro> I think we need to add a mode in the parser that allow us to process old data
16:30:35 <GeKo> i have not even looked at the family generation code yet, so...
16:30:53 <hiro> ah!
16:31:09 <hiro> ok well I do not think the current family generation stuff we have is working anyways
16:31:22 <GeKo> i just spent some time on the status builder as i wanted to get a fresh picture of the whole system working
16:31:40 <hiro> so I think we can do a merge once the code is "clean-enough"^TM and then open the subsequent issues
16:32:05 <hiro> what do you think?
16:32:34 <GeKo> uhm
16:32:36 <GeKo> :)
16:33:03 <GeKo> fine with me
16:33:39 <GeKo> let's see where we are at the end of tomorrow?
16:34:03 <GeKo> maybe we feel comfortable by then testing something for #72
16:34:17 <hiro> yep
16:34:20 <hiro> sounds good
16:34:25 <GeKo> great
16:34:35 <GeKo> hiro: anything else?
16:34:51 <hiro> well there is some issue with onionoo-backend-02 which I do not understand
16:34:56 <hiro> but besides that all groot
16:35:08 <GeKo> is it just -02?
16:35:26 <GeKo> i thought -01 was behaving weird as well from time to time?
16:36:14 <hiro> uhm I am not sure I understood 01 was sending the correct first-seen time
16:36:18 <hiro> and 02 wasn't
16:36:37 <hiro> I haven't checked the status on disk for the reported relays tho
16:37:35 <GeKo> ah, okay
16:37:48 <GeKo> maybe it was indeed just 02
16:38:25 <GeKo> okay
16:38:39 <GeKo> i think that's it for today
16:38:46 <GeKo> thanks everyone and have a nice week
16:38:49 <GeKo> #endmeeting