Monday, 2026-04-13

alanbachHello everyone o/06:53
alanbachAre we going to have a meeting today?07:00
say3no_hi07:02
alanbachHello!07:02
say3no_yes,07:03
say3no_It starts at 16:00 today. Sorry for the slight delay.07:03
say3no_sorry, 16:00 means JST 16:0007:03
say3no_#startmeeting masakari07:04
opendevmeetMeeting started Mon Apr 13 07:04:26 2026 UTC and is due to finish in 60 minutes.  The chair is say3no_. Information about MeetBot at http://wiki.debian.org/MeetBot.07:04
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:04
opendevmeetThe meeting name has been set to 'masakari'07:04
masahitoo/07:06
alanbachHello o/07:06
say3no_https://etherpad.opendev.org/p/masakari-meeting-2026.107:06
say3no_#topic [alanbach] (Please feel free to move this if there are more important topics) Kindly requesting a review on https://review.opendev.org/c/openstack/masakari/+/97834307:07
alanbachI was here to kindly ask for another set of eyes on that review07:07
alanbachThe concurrent database insertion in Masakari HA has been becoming more problematic for our clients, that's why I proposed a small change in the create_notification_function function07:09
say3no_I sincerely apologize for the delay. I'm aware you've been following up on this since Mar 24, and I haven't been able to get to it until now.07:09
alanbachhttps://review.opendev.org/c/openstack/masakari/+/978343/3/masakari/ha/api.py#35007:09
alanbachNo worries at all! 07:09
alanbachThank you so much for looking into it 07:10
say3no_"Understood. Indeed, depending on the race condition, the current design can result in multiple notifications being created.07:12
alanbachCorrect, introducing the random pause allows the current duplicate detection function to catch them and it has been working reliably in my lab 07:13
alanbachI have a reproducer script added here: https://bugs.launchpad.net/masakari/+bug/2028450/+attachment/5949483/+files/lp2028450-reproducer.bash07:13
alanbachUsing it to reproduce as well as test the fix07:14
say3no_I'd like to discuss this a bit further, if you don't mind. My honest impression is that this PR is more of a workaround than a fundamental fix. I genuinely don't have a settled view on how we should handle PRs like this as a project — I'd value your perspective. From your point of view, what would be the right way to address this issue at its root?07:16
say3no_Honestly, part of me feels we could just merge this as-is. On the other hand, for a workaround of this size, I'm not fully convinced it needs to live upstream — it might be just as well maintained as a local patch on alanbach's side. I'd love to hear your thoughts.07:18
alanbachI believe having the coordination engine should prevent this (please correct me if I am wrong), however the issue is not all deployments have this configured. For example Charmed OpenStack to this day does not support the coordination engine07:19
alanbachOn top of that we still support older versions of Masakari which do not have support for coordination engine07:20
alanbachThe goal is to apply a similar patch to at least remedy the issue for the time being 07:20
alanbachI am considering this change more of a safety fallback system where the coordinator is not configured07:23
say3no_Thanks for the discussion. I've added a few comments on the proposal for your consideration.07:26
say3no_https://review.opendev.org/c/openstack/masakari/+/978343/comments/798712ba_41451fcf07:26
say3no_Once these four points are addressed, I'm happy to give it a +2 and proceed with the merge. Thank you for working on this07:27
alanbachGreat idea! Thank you so much - I'll implement this and will sent a fresh patchset for review 07:28
alanbachThank you again for the discussions and the review07:28
alanbachHave a great rest of the day o/ I am dropping now it is 00:30am here :-D07:29
say3no_Not at all — thank you for joining the discussion. Hearing from people who actually use Masakari in production is genuinely encouraging for us. Please come back anytime!07:29
say3no_oyasumi nasai07:29
alanbachThank you07:30
say3no_Next topic07:30
say3no_#topic PTG Topics and slot https://etherpad.opendev.org/p/masakari-ptg-2026.207:31
say3no_I've added some details to the PTG discussion topics on the etherpad.07:36
say3no_I'm currently looking for the page to register PTG time slots...07:40
say3no_#link https://ptg.opendev.org/ptg.html07:41
say3no_I'm thinking of booking the following slots for Masakari. If any of these are inconvenient for you, please speak up!  Mon/Tue 07:00 UTC (16:00 JST, 09:00 CEST) Mon/Tue 08:00 UTC (17:00 JST, 10:00 CEST)07:57
say3no_I'll proceed with the booking via PTGbot after this. Thank you all for joining today's discussion!07:58
say3no_#endmeeting07:58
opendevmeetMeeting ended Mon Apr 13 07:58:37 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)07:58
opendevmeetMinutes:        https://meetings.opendev.org/meetings/masakari/2026/masakari.2026-04-13-07.04.html07:58
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/masakari/2026/masakari.2026-04-13-07.04.txt07:58
opendevmeetLog:            https://meetings.opendev.org/meetings/masakari/2026/masakari.2026-04-13-07.04.log.html07:58
opendevreviewAlan Baghumian proposed openstack/masakari master: ha/api : create_notification  https://review.opendev.org/c/openstack/masakari/+/97834320:49
opendevreviewAlan Baghumian proposed openstack/masakari master: ha/api : create_notification  https://review.opendev.org/c/openstack/masakari/+/97834320:54

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