| opendevreview | Merged openstack/masakari master: Detect missing [taskflow] connection https://review.opendev.org/c/openstack/masakari/+/973001 | 03:22 |
|---|---|---|
| opendevreview | Merged openstack/masakari master: docs: update information about cinder endpoint in verify https://review.opendev.org/c/openstack/masakari/+/974656 | 04:14 |
| opendevreview | Merged openstack/masakari-monitors master: Migrate setup configuration to pyproject.toml https://review.opendev.org/c/openstack/masakari-monitors/+/973335 | 04:34 |
| say3no_ | hi | 07:00 |
| masahito | hi | 07:01 |
| say3no_ | thank you masahito 3, let's start meeting | 07:01 |
| say3no_ | #startmeeting masakari | 07:01 |
| opendevmeet | Meeting started Mon Feb 16 07:01:54 2026 UTC and is due to finish in 60 minutes. The chair is say3no_. Information about MeetBot at http://wiki.debian.org/MeetBot. | 07:01 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 07:01 |
| opendevmeet | The meeting name has been set to 'masakari' | 07:01 |
| say3no_ | #info https://etherpad.opendev.org/p/masakari-meeting-2026.1 | 07:02 |
| say3no_ | #topic Elections | 07:03 |
| say3no_ | As I was going through the upcoming schedule, I noticed the election was coming up, so I thought I'd raise it as a topic. | 07:04 |
| noonedeadpunk | o/ | 07:04 |
| noonedeadpunk | sorry for being late and not keeping in line with meetings | 07:04 |
| say3no_ | hi! | 07:05 |
| noonedeadpunk | nomination period is coming to it;s end actually | 07:05 |
| say3no_ | I was hoping to hear from the current PTL if they had any thoughts, but I'm wondering — what happens if no one ends up nominating? | 07:05 |
| noonedeadpunk | so it;s high time to get some candidate out for the project | 07:05 |
| noonedeadpunk | I can elaborate on this :) | 07:06 |
| say3no_ | +1 | 07:07 |
| noonedeadpunk | so if project has no nominations, it appears on a TC table, where TC gives a call to gein community attention and a couple of weeks for potential volunteer to step in | 07:07 |
| noonedeadpunk | thought it's really better not to get to this point, and have a nomination right away | 07:07 |
| noonedeadpunk | and better to have an election, rather then a project without any | 07:07 |
| noonedeadpunk | and if nobody steps in within these couple of weeks, project goes to inactive state and then getting retired for the next cycle | 07:08 |
| say3no_ | I see, thanks for the explanation. | 07:09 |
| masahito | right. we need slot in the next ptg. someone should raise their hand. | 07:10 |
| say3no_ | Just to confirm — PTLs are elected every six months, right? | 07:12 |
| noonedeadpunk | yes, correct | 07:12 |
| noonedeadpunk | and also there\s a possibility to move project to DPL model | 07:13 |
| noonedeadpunk | to spread an administrative workload between different people | 07:13 |
| noonedeadpunk | though, I guess for moving PTL->DPL it either should be a current PTL initiative, or project should be grapped by community without active nominations for elections | 07:14 |
| noonedeadpunk | and I'd really discourage to get to the point of no nominations, as then things can be really unpredictable | 07:15 |
| say3no_ | I see. I do have some interest in taking on the Masakari PTL role, but I'd like to get a bit more experience with how the community works before stepping up. I haven't even been through a full cycle yet. | 07:16 |
| noonedeadpunk | well, then DPL can be smth to consider... | 07:17 |
| noonedeadpunk | #link https://governance.openstack.org/tc/reference/distributed-project-leadership.html | 07:17 |
| noonedeadpunk | or, we can do PTL with liasons instead | 07:17 |
| noonedeadpunk | #link https://docs.openstack.org/project-team-guide/ptl.html | 07:17 |
| say3no_ | reading now ... | 07:19 |
| noonedeadpunk | I likely can help out with things like releasing, if needed | 07:19 |
| say3no_ | thank you | 07:20 |
| noonedeadpunk | and likely some other things as well | 07:21 |
| noonedeadpunk | I just having troubes to follow the bi-weekly meeting schedule, but I just need to be more organized I guess :D | 07:22 |
| noonedeadpunk | as if I have to skip one week - then I'm completely lost | 07:22 |
| say3no_ | Given the risk that Masakari could be retired if no one nominates, let me take a little time to think about the Masakari PTL role — though I know time is short. I also need to consider some internal matters at my company. | 07:25 |
| noonedeadpunk | but I\d guess I\d encourage to take part in elections, given that youre eligible candidate (have some patches merged), and then sorting out liason part | 07:26 |
| noonedeadpunk | yeah, internal matters are important to consider, shure | 07:26 |
| noonedeadpunk | *sure | 07:26 |
| say3no_ | okay | 07:26 |
| say3no_ | #topic [FYI] Change Masakari Team meeting Agenda URL | 07:27 |
| say3no_ | Next is just an announcement/FYI. Thanks in advance. | 07:28 |
| say3no_ | #topic Need review open MRs for masaki-monitors 937674 and 902139 | 07:29 |
| say3no_ | This topic was probably added by Ivan Anfimov. It's about a review request for the introspectiveinstancemonitor in masakari-monitor. | 07:31 |
| say3no_ | Does anyone here have experience with or knowledge about the introspective monitor? | 07:33 |
| say3no_ | In preparation for this review, I've been looking into the current state of Masakari's test implementation and DevStack integration, and I'm setting up an environment in my homelab. | 07:33 |
| say3no_ | This might be slightly off-topic from the review itself, but... | 07:34 |
| noonedeadpunk | I have never used introspective monitor tbh | 07:34 |
| masahito | me neither. | 07:35 |
| say3no_ | Currently, I feel frustrated that Masakari lacks tempest tests and functional tests for masakari-monitor, which makes it difficult to do proper code-level reviews. I believe contributing these functional tests and improving the DevStack integration would benefit the community. What do you all think? | 07:36 |
| noonedeadpunk | 937674 does make sense to me at least | 07:37 |
| masahito | there was less activity in the last few cycles, so let's improve everything one by one, imo. | 07:37 |
| masahito | yes sure. | 07:37 |
| noonedeadpunk | well, I'd say it's hard to test this in current devstack implementation | 07:37 |
| noonedeadpunk | as that would kinda require multi-node setup | 07:38 |
| noonedeadpunk | so we could shut it down and see if things are get executed as expected | 07:38 |
| noonedeadpunk | as how would you really test anything on single node devstack... | 07:38 |
| noonedeadpunk | and unit tests is smth we can base review on... | 07:39 |
| say3no_ | Maybe the real issue is that the unit test coverage for introspective monitor seems insufficient? As for testing on DevStack, it should be possible if you prepare an image with qemu-ga and craft the userdata, but it's still not easy either way. | 07:41 |
| noonedeadpunk | oh, yes | 07:42 |
| noonedeadpunk | and that is smth which should be possible to fix with not-so-high effort with AI... | 07:42 |
| noonedeadpunk | but again, somebody need to understand code paths for the monitor beforehands... | 07:43 |
| say3no_ | As a core reviewer, I'd like to give it a +2 since the code looks fine, but I also want to make sure it actually works without issues — since I'd be taking responsibility for the merge. That said, verifying it in my homelab rather than in the community DevStack would probably be sufficient. | 07:44 |
| noonedeadpunk | ++ | 07:44 |
| masahito | agree and understood your feelings | 07:45 |
| say3no_ | :) | 07:45 |
| say3no_ | And it's tough for an individual to bear that cost alone, so in the future I'd like to shift that burden toward DevStack and functional tests. | 07:45 |
| noonedeadpunk | as for 902139 - I\d request a unit test coverage for the method | 07:46 |
| noonedeadpunk | I kinda still not getting how you plan to test things like hostmonitor or instance monitor with single node devstack, but yeah... | 07:47 |
| say3no_ | thank you Dmitriy-san | 07:47 |
| say3no_ | For the host monitor, I think we'd have no choice but to set up a three-node multi-node environment. | 07:48 |
| noonedeadpunk | I\d say 2 node should work? | 07:49 |
| noonedeadpunk | but then the same setup should work for retrospective monitor as well | 07:49 |
| noonedeadpunk | so probably it does not make much sense to do smth unique for retrospective instance monitor which won't work for other monitors | 07:50 |
| noonedeadpunk | dunno though | 07:50 |
| say3no_ | Well, if we don't worry about tricky stuff like split brain, 2 nodes should be fine. | 07:50 |
| say3no_ | Well, I think I'll keep tinkering with my homelab a bit more. | 07:51 |
| noonedeadpunk | hm, is there anything in masakari actually dealing with split brains? As I was under impressions this is offloaded to clustering software, like consul or pacemaker | 07:51 |
| say3no_ | That's a good point. I was unnecessarily expanding the scope there. | 07:53 |
| noonedeadpunk | I was thinking of optimizing utilization of CI resources :D | 07:54 |
| say3no_ | Right, our resources are limited after all. | 07:56 |
| say3no_ | Regarding this topic, I'll look into adding unit tests for 937674, and I'll re-review 902139 today and give it a +2 if everything looks good. | 07:56 |
| say3no_ | I'd like to wrap up the meeting. Does anyone have anything else they'd like to bring up? | 07:57 |
| masahito | one thing ptg entry | 07:58 |
| masahito | we need ptg slot request until 1st May. https://openinfrafoundation.formstack.com/forms/apr2026_ptg_survey | 07:59 |
| masahito | s/May/March | 07:59 |
| say3no_ | Is this something the PTL is supposed to submit? Or can we as a team go ahead and do it ourselves? | 08:00 |
| masahito | PTL is supposed to submit it usually. | 08:01 |
| noonedeadpunk | ideally - this is a PTL responsibility | 08:01 |
| say3no_ | okay | 08:01 |
| noonedeadpunk | but Id say we can ask for exception in registering the team after 1st of March | 08:02 |
| noonedeadpunk | given that somebody more active step in as a ptl :) | 08:02 |
| say3no_ | Understood. As an action item, I'll check with the current PTL about their intentions. | 08:04 |
| masahito | thanks | 08:05 |
| say3no_ | any questions? | 08:05 |
| say3no_ | okay, I close this masakari meeting 2026-02-16. thank you for comingOkay, I'm closing the Masakari meeting for 2026-02-16. Thank you all for joining. | 08:07 |
| say3no_ | #endmeeting | 08:07 |
| opendevmeet | Meeting ended Mon Feb 16 08:07:23 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 08:07 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/masakari/2026/masakari.2026-02-16-07.01.html | 08:07 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/masakari/2026/masakari.2026-02-16-07.01.txt | 08:07 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/masakari/2026/masakari.2026-02-16-07.01.log.html | 08:07 |
| masahito | thank, bye | 08:07 |
| opendevreview | Sei Sano proposed openstack/masakari-monitors master: Handle exception from guest agent correctly https://review.opendev.org/c/openstack/masakari-monitors/+/902139 | 22:56 |
| opendevreview | Sei Sano proposed openstack/masakari-monitors master: Handle exception from guest agent correctly https://review.opendev.org/c/openstack/masakari-monitors/+/902139 | 23:09 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!