Thursday, 2026-06-11

*** amadaluzia <amadaluzia!2cbc58d702@user/amadaluzia> has quit IRC (Read error: Connection reset by peer)01:30
*** amadaluzia <amadaluzia!2cbc58d702@user/amadaluzia> has joined #cip01:33
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip05:53
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 248 seconds)05:59
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has quit IRC (Read error: Connection reset by peer)07:52
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip09:17
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 248 seconds)09:39
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has joined #cip10:21
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has quit IRC (Ping timeout: 245 seconds)10:33
*** tmerciai2 <tmerciai2!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has joined #cip10:33
*** jki <jki!~jki@46.128.82.95> has joined #cip11:56
jkihi all12:00
iwamatsuhello12:00
ulihello12:00
patersoncHi12:00
jkiok, let's start already12:01
jki#startmeeting CIP IRC weekly meeting12:01
collab-meetbot`Meeting started Thu Jun 11 12:01:27 2026 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.12:01
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:01
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'12:01
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:01
jki#topic AI review12:01
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:01
jkiI had nothing noted12:01
jki512:02
jki412:02
jki312:02
jki212:02
jki112:02
jki#topic Kernel maintenance updates12:02
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:02
ulii pushed 4.412:02
iwamatsuI reviewed 6.12.9012:02
jki"This week reported 63 new CVEs and 7 updated CVEs." - masami12:04
jkianything else to add?12:04
jki512:04
jki412:04
jki312:04
jki212:04
jki112:04
jki#topic Kernel release status12:05
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:05
jkiall on track, 6.1 (both) will be next12:05
jkistill no 6.1-rt-stable, I suppose...12:05
jkianything else to add?12:06
jki512:06
jki412:06
jki312:06
jki212:06
jki112:06
jki#topic Kernel testing12:06
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:06
jkihttps://lava.ciplatform.org/scheduler/worker/lab-cip-siemens-muc is green again12:07
patersoncThanks12:07
patersoncNot testing related, but I'm working with gitlab to get our license renewed12:07
patersoncNo other updates12:08
jkiif there is nothing more on testing, then move on...12:08
jki512:09
jki412:09
jki312:09
jki212:09
jki112:09
jki#topic AOB12:09
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:09
jkithere were 1 or 2 repos without licenses related to the kernel...12:09
jkicip-kernel/lts-commit-list was one12:10
jkistill unsure about just pushing GPL or first asking TSC12:10
jkipatersonc: who should delete cip-kernel/cip-kernel-tests?12:11
iwamatsuI think the original license for this data is GPLv2. Therefore, the license for this repository will also be GPLv2.12:11
jkiif that is true, we cannot deviate anyway12:12
jkiiwamatsu: would you push a license file then so that gitlab is identifying it?12:12
iwamatsuOK12:13
patersonccip-kernel/cip-kernel-tests should be okay now. I pushed a license to it. I'm happy to delete it though if it's not needed12:13
jkiGPLv2 or GPLv2+?12:13
jkipatersonc: it's confusing as the real repo is under cip-testing12:13
jkisame name12:14
patersoncShall I just delete cip-kernel/cip-kernel-tests?12:14
jkiI would say, yes12:14
patersoncDone12:15
jkithanks12:15
jkiiwamatsu: do you also know if we should use GPLv2+ for the other repo?12:15
patersoncSo just  lts-commit-list remaining now. Plus a couple of non-code task-only projects that break the GitLab tooling (working with gitlab on this)12:15
jkisome scripts are v2+ IIRC12:16
iwamatsuI don't know now.12:16
patersoncI can do it if you want?12:17
jkido what?12:17
patersoncAdd the license to lts-commit-list12:18
patersoncGitlab has a template for GPL v2, not v2+. But easy to copy in 2+ if that's what you want12:18
jkithe point is first of all identifying the required license12:19
patersoncok12:19
jkialthough v2+ allows us to pin to v2-only as well12:19
jkiwe would simply push the right text as COPYING file commit, and gitlab should recognize that12:20
iwamatsuI will proceed with that work.12:23
*** pav3l <pav3l!~pavel@jabberwock.ucw.cz> has joined #cip12:23
jkithanks! you were the initial committer anyway, just found out ;)12:23
jkigood12:23
jkithen maybe give pavel a change to catch up - we are already in AOB12:24
pav3lI am late, sorry.12:24
jkianything you want to add from other topics?12:24
pav3lI did reviews. 6.12.92 and .93.12:24
pav3lAnd it looks like this cycle is really a bit different, as we are pretty late12:24
pav3land there are still big series flying around.12:25
pav3lOther than that, not much to report.12:25
jkidid you ping regarding 6.1-rt?12:25
pav3lNot yet, sorry.12:25
jkiwill be due now for us very soon12:25
jkiok12:25
jkithen maybe switch to the AI review topic12:26
jkiuli: thanks again for the write-up12:26
ulinp12:26
jkianyone else has comments / ideas regarding it?12:26
jkipatersonc: I suppose our AWS account would be able to cover some instances with GPUs as well, right?12:27
patersoncProbably12:28
patersoncIf we want to pay lots :P12:28
jkicost-wise, we would obviously be prepared to handle any overrun as CIP12:28
jkiuli: do you have an idea about what would match your needs from the AWS offerings?12:29
ulii haven't looked into aws yet12:29
jkiwe will need some rough math on costs when running this, even when just for some weeks12:29
jki...first12:29
jkiadvantage might be that his should be able to be started and stopped as needed12:30
patersoncMaybe LF has a central service of some kind12:30
patersoncMaybe we need to get Google or someone similar to join the project and get free tokens ;)12:30
jkiregular LF IT will likely be too costly12:31
jkigetting tokens means also buying into specific commercial models12:31
*** tmerciai2 <tmerciai2!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has quit IRC (Ping timeout: 246 seconds)12:32
jkiwe could try that as well, later on, and specifically if there something comming via Glasswing12:32
jkibut the first idea would be replicating uli's setup for shared use12:32
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has joined #cip12:32
uliwhat would be an acceptable budget anyway? like per month?12:32
jkiI would have not problem to ask for, say, 10K first, and we see how far we would get with it12:33
jkidays, weeks, or some month - and then we can check again the value and make a real plan12:34
ulithe only option i have looked at so far (except for pay-as-you-go stuff like vast.ai) is a server from hetzner for 800 something per month (96 GB VRAM)12:34
jkilikely days would be too short, though ;)12:34
uli+2000 or 3000 (don't remember) setup or therabouts12:34
jkiadditional supplier may complicate a quick setup, I guess12:35
uliyeah, i expected that...12:35
jkithat's why I thought of AWS - we have our credit card registered12:35
jkifurther thoughts?12:36
patersoncThank you for the good analysis uli12:37
ulihappy to help12:38
jkihttps://aws.amazon.com/ec2/instance-types/g5/ - this sounds... expensive :)12:38
ulii have difficulties parsing that web site12:40
pav3lYou can click and talk to their "certainly not halucinating" AI assistent :)12:40
jkithere are also special inference instances, but probably with special accelerators12:42
jkiknown to work is something with NVIDIA or AMD, I suppose12:42
jkisooo may different instance types, easily losing overview12:42
uliyou want nvidia. everything else theoretically works but in practice is a pain12:43
uliespecially intel12:43
jkihttps://aws.amazon.com/ec2/instance-types/g7e/ ?12:44
jki"NVIDIA RTX PRO 6000 Blackwell Server Edition"12:44
patersonchttps://instances.vantage.sh/aws/ec2/g5.12xlarge?currency=USD&duration=annually12:44
jki5k/h - hmm, that would be short fun with my 10K12:45
pav3ljki: That's likely $5/h, right?12:47
pav3ljki: It is US, so dot is decimal dot.12:47
jkiyeah, dot-confusions12:47
jkisound much better12:47
ulihttps://www.hetzner.com/dedicated-rootserver/gex131/  1k/month incl vat12:47
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has quit IRC (Ping timeout: 252 seconds)12:48
jkiuli: that can still be an option once we know we want to run that 24/712:48
jki...or have to12:48
jkiI would go for some on-demand first, if possible, also to play with instance sizes12:48
uliin that case vast.ai might be an option. it's not super-reliable, but then i always choose the cheapest, most unreliable option there... :)12:48
jkior with new models12:48
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has joined #cip12:48
jkilooks a bit cheaper, if I chose the right comparison, but not by factors, right?12:50
uliit's actually even a bit more expensive than the hetzner option, but then you can get everything by the hour there12:50
uliand no setup fees12:51
jkimy point is what would be easiest for us to start playing, also from account handling perspective12:51
jkiI don't want anyone to swipe their personal credit cards here12:52
jkiwhat speaks against trying out an EC2 instance first on our existing account? later, we could check what is needed to use other hosters as well12:53
ulifor me that's ok12:55
jkithen I would still ask for a 10K reserve from TSC->Board so that we have some buffer in case we overshoot the AWS grants12:57
jkianything else for today?12:57
jki512:58
jki412:58
jki312:58
jki212:58
jki112:58
jki#endmeeting12:58
collab-meetbot`Meeting ended Thu Jun 11 12:58:30 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:58
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/06/cip.2026-06-11-12.01.html12:58
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/06/cip.2026-06-11-12.01.txt12:58
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/06/cip.2026-06-11-12.01.log.html12:58
*** collab-meetbot` changes topic to "Civil Infrastructure Platform Project. CIP mailing list at https://lists.cip-project.org/g/cip-dev | CIP kernel meeting every Thursday at 13:00 UTC | Find the meeting logs at https://ircbot.wl.linuxfoundation.org/meetings/cip/ and chat logs at https://ircbot.wl.linuxfoundation.org/logs/%23cip/"12:58
jkithanks!12:58
ulithanks12:58
pav3lThank you!12:58
patersoncCheers12:58
*** pav3l <pav3l!~pavel@jabberwock.ucw.cz> has quit IRC (Quit: Leaving)12:59
iwamatsuthank you13:00
*** jki <jki!~jki@46.128.82.95> has quit IRC (Quit: Leaving)13:00
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has quit IRC (Quit: Leaving)13:38
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has joined #cip13:38
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has quit IRC (Ping timeout: 252 seconds)14:28
*** tmerciai1 <tmerciai1!~tmerciai@net-188-217-58-220.cust.vodafonedsl.it> has joined #cip14:28

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!