Hi,
Here's the summary of the IRC meeting.
---
COMMUNITY MEETING
Place: #openvpn-meeting on libera.chat
Date: Wed 3rd August 2022
Time: 10:30 CEST (9:30 UTC)
Planned meeting topics for this meeting were here:
<https://community.openvpn.net/openvpn/wiki/Topics-2022-08-03>
Your local meeting time is easy to check from services such as
<http://www.timeanddate.com/worldclock>
SUMMARY
cron2, d12fk, dazo, djpig, lev, kp, mattock, MaxF and ordex participated
in this meeting.
---
Talked about buildbot. After latest djpig's changes (including
increasing number of CPU cores on the docker host) gitpoller seems to
have become stable.
---
Noted that djpig needs t_client keys for his MacOS buildbot worker.
Cron2 can grant him access, or mattock can get him the keys.
---
Noted that nothing important has been happening in OpenVPN's release/2.5
branch.
---
Talked about the ifconfig-noexec patch. Noted that because buildbot was
not operating properly the patch could not yet be tested properly.
Agreed that ifconfig-noexec patch will be exposed to the now working
buildbot after the DCO hassle is done.
---
kp will repost the FreeBSD DCO patches once the latest Linux DCO patches
have landed.
---
Agreed to remove the --disable-managent option.
--
Full chatlog attached
(11:30:04) dazo: o/
(11:30:13) cron2__: I am here
(11:30:16) cron2__: and I am not here...
(11:30:20) mattock: hi
(11:30:38) dazo: schrödingers cron2__ .....
(11:30:39) cron2__: I just received a call that I need to leave *now* to pick
up $kid at train station, at 11:15, and it takes me 30+ minutes to get there...
(11:30:59) dazo: no worries
(11:31:03) cron2__: I do not have anything that ordex or djpig couldn't report
on
(11:31:31) djpig: hey, I'm punctual to a community meeting :)
(11:31:32) cron2__: dazo: something for you - this Ka Lok Wu person sent a mail
to security@ that none of us can decrypt. Maybe we need new security@ keys?
(11:31:40) cron2__: djpig: hi and ciao ;-)
(11:31:50) MaxF: hi!
(11:31:57) ***cron2__ waves and runs
(11:32:03) dazo: cron2__: I'll handle that ... I thought I had sent you the
2022 keys for security list
(11:32:18) mattock: hi guys!
(11:32:27) cron2__: dazo: if you have, they haven't made it :-( - please re-send
(11:33:01) ***plaisthos is here
(11:33:29) d12fk: hi
(11:34:13) djpig: first topic seems to be for me to give a buildbot status
update?
(11:34:23) mattock: I'm interested in that also
(11:34:35) mattock: also, thanks to djpig for saving what remained of my
vacation! :)
(11:34:43) djpig: okay, I will get started
(11:35:18) djpig: - buildbot gitpoller works reliable since update to 3.5.0
(11:35:42) djpig: - I added workers for Ubuntu 22 and Fedora 36. If you have
any workers you're missing let me know
(11:36:04) mattock: djpig: did you upgrade the EC2 instance also?
(11:36:11) mattock: and/or allocate more memory for the container?
(11:36:14) mattock: buildmaster container
(11:36:18) ordex: ay
(11:36:23) djpig: - I added a macOS worker yesterday which should be mostly
functional now. Missing t_client setup
(11:36:45) djpig: mattock: yeah, upgraded from 2 vCPUs to 4 vCPUs
(11:36:50) mattock: +1
(11:37:14) djpig: memory is not a problem so far, so I used the m instance type
for now.
(11:37:25) djpig: C builds really don't require a lot of memory
(11:38:00) mattock: current buildbot config uses locking to ensure that, at any
given time, only two docker-based builds are running at the same time
(11:38:21) mattock: this prevents buildbot docker host from choking on trying
to launch <x> containers at once
(11:38:35) mattock: this should ensure that memory consumption remains
reasonable
(11:38:48) djpig: cron2__: mattock said for getting access to the t_client CA
to generate a new client cert for the macOS worker I need your assistance?
(11:39:23) djpig: mattock: actually it is num of CPUs, not 2. But even with
four builds memory is still plenty
(11:40:38) djpig: I think that's it as an update. Let me know if you have
questions. Otherwise we can move on to the next topic, I guess
(11:40:49) mattock: ah ok
(11:42:15) mattock: djpig: I can also generate t_client keys for you, or cron2
could grant you access to the openvpn test/ca server
(11:42:55) mattock: next topic: "Hackathon"
(11:43:04) mattock: any news from MaxF or lev?
(11:43:49) lev__: yeah we're welcomed in Hki, I haven't cancelled it yet
(11:44:27) lev__: apparently in Delft we need first aid guy
(11:45:08) MaxF: One of the people who are helping out had the BHV training.
I'll try to look for one more in case they can't be there the whole time
(11:46:11) ordex: could we start a poll for the dates? or we need more pieces
first?
(11:47:23) MaxF: I'll check today with the first aid person if there are some
dates where they aren't available
(11:47:46) MaxF: then I can exclude those dates from the poll right away
(11:48:37) MaxF: first date September 24, last date November 26?
(11:49:02) becm_ [~Thunderbi@217.110.68.42] è entrato nella stanza.
(11:49:22) ordex: I think it makes sense
(11:50:29) dazo: +1
(11:51:13) mattock: +1
(11:52:11) mattock: sync up on 2.5/2.6?
(11:52:44) mattock: (I have to go to lunch in <20 mins, traveling in car)
(11:54:12) ordex: for 2.5 I am not sure there is much?
(11:54:26) ordex: for 2.6 we are on DCO patch 10 and 11 at the moment
(11:54:39) ordex: 10 is close to be merged - cron2__ was asking some extra
feedback to djpig
(11:54:49) ordex: while 11 has just been subject of modification
(11:55:14) d12fk: I'll have started reviewing more from plaisthos by next week,
so there will be more incoming for 2.6
(11:56:04) kp: I'm planning to re-post the freebsd patches when most/all of the
current dco patches have landed. Does that make sense to everyone?
(11:56:24) ordex: kp: yeah, there is currently quite some activity so reporting
now will only lead to -> report again later
(11:57:04) MaxF: sorry if I'm annoying, but what about the ifconfig-noexec bug?
(11:57:29) kp: I'm not familiar with that issue.
(11:57:59) MaxF: https://patchwork.openvpn.net/patch/2567/
(11:58:12) vpnHelper: Title: [Openvpn-devel,v5] Don't "undo" ifconfig on exit
if it wasn't done - Patchwork (at patchwork.openvpn.net)
(11:58:24) ordex: MaxF: I acked that patch with reserve but it couldn't be
tested further because we were in te middle of a buildbot reshuffling
(11:58:35) ordex: so couldn't test on various platforms like *bsd
(11:58:35) Pippin_ [~Pippin_@openvpn/community/Pippin] è entrato nella stanza.
(11:58:47) ordex: the buildbot is back operation since a few days, but now
cron2__ is still deep into DCO
(11:58:59) ordex: so I guess your patch will be poked again once we're done
with DCO
(11:59:15) ordex: operational*
(11:59:17) mattock: there are still some buildbot build failures, but those
seem genuine issues, not buildbot-related (based on a cursory glance)
(11:59:29) MaxF: I have an OpenBSD machine, would it help if I test it manually
on there?
(11:59:30) ordex: yap, some of those are on cron2__'s agenda to fix
(11:59:53) ordex: MaxF: it definitely would, but we'd still want to have the
patch go through the full buildbot machinery before merging
(12:00:07) ordex: but yeah, testing there is definitely added value (you may
find a bug :p)
(12:00:27) MaxF: ok!
(12:05:16) mattock: I have 10 mins - next topic?
(12:05:28) mattock: <10 mins
(12:06:42) mattock: remove --disable-management?
(12:07:11) dazo: Yes, remove.
(12:08:16) ordex: remove!
(12:08:31) ordex: cron2__ was looking around and saw that it really brings a
lot of code
(12:08:44) ordex: but I agree that it makes more sense to remove the ifdef
craziness and maybe we can simplify the code later on
(12:08:46) plaisthos: I also don't think the difference is size is worth it
(12:09:09) ordex: [1642.53] <@cron2__> --disable-management saves 70 kbytes
(12:09:11) plaisthos: and the maintainance headache for us
(12:09:16) ordex: it's not really negligible
(12:09:20) plaisthos: I know.
(12:09:26) ordex: but yeah, we can survive
(12:09:30) plaisthos: But openvpn in total is not big by today's standards
(12:10:22) mattock: ok, so remove it is
(12:10:26) mattock: I need to split now
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel
