Wednesday, 2025-04-23

ttx#startmeeting large_scale_sig15:00
opendevmeetMeeting started Wed Apr 23 15:00:32 2025 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'large_scale_sig'15:00
amorinhello!15:00
ttxamorin: high!15:00
ttxhi!15:01
dmsimard[m]hello o/15:01
ttxHi dmsimard good to see you!15:01
ttxfelix.huettner: around?15:02
ttxWelcome to the monthly Large Scale SIG meeting...15:02
ttxOur agenda lives at:15:02
ttx#link https://etherpad.opendev.org/p/large-scale-sig-meeting15:02
ttxFeel free to add topics there while we wait for stragglers15:03
ttx#topic Next Large Scale SIG virtual meetup15:03
ttxUnfortunately not much progress to report on that front. We were waiting for Nexgen to confirm (as we wanted an AI infrastructure episode) but they seem too busy buying GPUs right now15:04
ttxI'm now looking at plan C, after our two main targets did not follow up15:05
ttxLet me know if you have suggestions of who we could reach out to!15:06
ttxDefinitely want to do one before summer hits15:06
amorinack, I dont remember the name of the company, but they were doing baremetal with openstack15:07
amorindmsimard[m]: I think we talked about it once15:07
dmsimard[m]CERN is always interesting to hear about but they already talk a lot about what they do :)15:07
amorinyes, cern is a good idea, they do use GPU as per talks I heard about on kubecon15:08
ttxyes and we had them several times already :) Would like to feature a recent/new user ideally15:08
ttxI'll come up with suggestions and probably discuss it over email so that we make progress before next month meeting15:09
dmsimard[m]agreed15:09
ttx#action ttx to suggest plan C solutions in a ML thread ahead of next meeting15:09
ttxbut yes, if we can't convince a recent user to talk about their stuff, we'll reach out to older users, maybe one that's been growing their footprint a lot15:10
ttxAnything else on that topic?15:11
ttx#topic Large scale doc15:12
ttx#link https://docs.openstack.org/large-scale15:12
ttxNothing to review on https://review.opendev.org/q/project:openstack/large-scale+status:open15:12
ttxDoes anyone have new doc changes cooking?15:12
amorinI remember, it was openmetal!15:12
amorinsorry for late answer :(15:13
ttxOK, next topic...15:14
ttx#topic Anything to highlight from the PTG ?15:14
ttxGood question! I haven't been attending that many sessions so I can't tell15:14
ttxAnything relevant in sessions you attended?15:14
dmsimard[m]I added this topic, I also haven't been able to attend but did browse a couple etherpads after the fact15:15
dmsimard[m]I didn't come prepared with a list but was hoping to know if there was noteworthy things to put on our radar to follow15:16
ttxamorin: did you attend anything relevant?15:17
dmsimard[m]I saw in keystone there is an attempt to rewrite it in rust for improved performance, for example15:18
dmsimard[m]https://etherpad.opendev.org/p/apr2025-ptg-keystone line 9915:18
ttxI guess taht's a good question -- would you consider that Keystone performance is such a bottleneck that you would just both feet into a Rust rewrite (and the inevitable regressions it would initially bring?)15:19
amorinI did attend few stuff around GPU, autoscaling15:19
ttxjump*15:19
amorinI attented some very interesting talks about telemetry / monitoring of applications15:19
amorinwhich is something we lack in OpenStack IMHO15:19
ttxI would agree that telemetry is a bit lacking right now15:20
dmsimard[m]@ttx, I don't personally have strong opinions and know what happened to past attempts at rewriting things in golang or rust :)15:20
dmsimard[m]I am curious and interested in claims of 10x to 100x performance improvements, though15:21
amorinwe are trying to implement sentry inside neutron downstream, but this is still wip15:21
dmsimard[m]We have something on the order of 100 million keystone API calls in 24h so even 10x improvement is significant15:23
ttxdmsimard: interesting to know that at least the struggle is real (not sure that rewrite is the solution, but there is a problem to solve)15:24
* dmsimard[m] nod15:24
ttxAny other interesting insight from the PTG week?15:25
ttxif not, moving on15:26
ttx#topic Next meeting(s)15:26
ttxOur next meeting is scheduled for May 28, 15utc, here as usual15:26
dmsimard[m]I noted a challenge in ARM testing from the nova pad since Linaro has stepped away15:26
ttxMy personal goal is to have a guest and a date for our next virtual meetup by then15:27
ttx#topic Open discussion15:28
dmsimard[m]Any plans for operators and this SIG at this upcoming France summit ?15:29
ttxWe'd like to have something yes15:31
ttxeither a ops feedback session, or something Large-Scale-SIG specific15:31
dmsimard[m]That would be great, let us know if we can help :)15:32
ttxWill sure do! We should see clearer in a month15:34
ttxAlright, anything else to discuss?15:34
dmsimard[m]nothing from me15:34
ttxOK then... Thanks for joining. Looks like we really need a new high-profile meetup to promote the monthly meeting and get more attendance :)15:36
ttx#endmeeting15:36
opendevmeetMeeting ended Wed Apr 23 15:36:09 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:36
opendevmeetMinutes:        https://meetings.opendev.org/meetings/large_scale_sig/2025/large_scale_sig.2025-04-23-15.00.html15:36
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/large_scale_sig/2025/large_scale_sig.2025-04-23-15.00.txt15:36
opendevmeetLog:            https://meetings.opendev.org/meetings/large_scale_sig/2025/large_scale_sig.2025-04-23-15.00.log.html15:36
amorinthanks!15:37

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