21:00:53 #startmeeting scientific-sig 21:00:53 Meeting started Tue Apr 12 21:00:53 2022 UTC and is due to finish in 60 minutes. The chair is oneswig. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:53 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:53 The meeting name has been set to 'scientific_sig' 21:01:13 I'm lurking owing to troubleshooting some curious RabbitMQ behaviour... 21:02:31 Anyone about today? 21:04:32 hello Scientific SIG friends :) 21:06:18 Greetings martial, good evening 21:06:29 Hi Stig :) 21:06:40 what's new since last week? 21:07:27 I'm up late working on a curious issue where I can boot VMs attached to some networks, but not others. 21:07:45 Other than that, not too much. 21:08:15 sounds frustrating if anything 21:08:47 One of our team hit a strange problem where a server RTC was not synced on reboot, so it boots up with a system clock 5 minutes out. Why it's not doing the RTC sync, who knows... 21:09:44 I don't mind a bit of grunty troubleshooting, actually :-) 21:10:34 How about you? 21:10:37 awaiting of a couple people to edit the Etherpad or work on their recording before I reach out to the foundation 21:10:54 and testing hyprscale.io in a container 21:11:04 OK, cool. Did you need anything from me on the etherpad? 21:11:41 up to you; I usually share the Etherpad content for them to have "title" "author" and small description (and links) 21:12:09 With hyprscale, does it depend on a broker service run by them? I couldn't figure out how it can traverse NAT from all endpoints without something like that. 21:13:01 according to the way it was presented to me, they reach out to a DHT to announce themselves 21:13:19 and check for connections this way 21:16:17 I am using `--cap-add=NET_ADMIN` but I am not sure that the `peers` see one another 21:17:30 more importantly, so far my `peers` can not ping themselves so something is amiss 21:18:44 Sounds highly secure :-) 21:19:44 well they say it themselves: "Hyprspace is still a very new project. Although we've tested the code locally for security, it hasn't been audited by a third party yet. We probably wouldn't trust it yet in high security environments." 21:21:32 That may also be true. I was following the adage that security is the opposite of functionality... 21:22:57 it's okay, worth testing further 21:23:36 the only thing being that I would more comfortable with it in a container 21:24:55 Do you need to use the host network namespace? I'm guessing so 21:25:23 yes I am pretty sure I am missing this 21:26:43 re-run with the right options, let's see 21:29:01 unable to bootstrap libp2p node 21:29:06 still some stuff to check 21:30:29 Going to commit my current steps and I can look it up later 21:31:30 likely missing passing the tun device or something simple :) 21:32:59 sounds fiddly, for sure 21:34:20 yep that was it 21:34:28 now I can at least ping the localhost 21:35:31 result :-) 21:39:17 Some small progress over here: while looking for the big problem, a small one is fixed... 21:39:26 perfect :) 21:40:02 I think we missed a deadline for registering a Scientific SIG session for Berlin, hopefully we can still slot something in 21:40:41 I did not see any option for it 21:40:51 I still would like to do one 21:40:56 I have my plane ticket 21:41:25 we should ask Ildiko 21:46:46 I think there was a suggestion we do it via the forum channels - deadline iirc 8th april 21:46:49 doh 21:47:01 totally missed it 21:47:41 it is my fault, I did not see it, send me the details, I will follow up 21:49:05 Thanks martial, much appreciated. I'll check 21:51:33 no problem, we are both going to be there, we should host a session for the SIG 21:54:23 Hopefully Blair will be there too. 21:54:42 hopefully, it was unclear last week during the PTG 21:54:43 Also time to think about a dinner out! 22:00:59 OK, time to close. Thanks martial, see you next time 22:01:04 #endmeeting