Monday, 2026-01-19

say3nohi06:59
say3noanyone there?07:00
say3noI brought an agenda, but if no one’s here, I guess we’ll skip again...07:02
say3noMaybe we should announce the recurring meeting in advance to openstack-dev?07:03
say3nohttps://etherpad.opendev.org/p/masakari-meeting-2026.107:06
say3noI’ll be on IRC until ~16:30. Ping me if anyone comes.07:07
masahito_hi07:07
say3nohi!!!07:08
masahito_we can start the meeting.07:09
masahito_btw, happy new year :)07:10
say3no#startmeeting masakari07:11
opendevmeetMeeting started Mon Jan 19 07:11:14 2026 UTC and is due to finish in 60 minutes.  The chair is say3no. Information about MeetBot at http://wiki.debian.org/MeetBot.07:11
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.07:11
opendevmeetThe meeting name has been set to 'masakari'07:11
say3nohappy new year :)07:11
say3no#info https://etherpad.opendev.org/p/masakari-meeting-2026.107:11
say3noAlright, let’s start with topic 1.07:14
say3no#topic Change Masakari Team Meeting Agenda URL : https://meetings.opendev.org/#Masakari_Team_Meeting07:14
say3noNow: https://wiki.openstack.org/wiki/Meetings/Masakari . The wiki is a bit heavy to update, so for the time being, I’d like to host the agenda on an Etherpad.07:16
say3noI considered just changing it and reporting afterward, but I’d rather notify everyone first. Unless there are any objections, I’d like to go ahead and make the change after this.07:17
masahito_+107:17
say3nothank you, masahitio_07:17
say3no#topic How should we review documentation changes?07:18
masahito_the zuul doc job has the link to the build result, doesn't it?07:21
say3noI see ...?07:22
masahito_https://review.opendev.org/c/openstack/masakari/+/973013 this is the link in the etherpad.07:23
masahito_Open the zuul's +1 comment details, and click "openstack-tox-docs" job result link. It opens the zuul job result.07:23
masahito_In the zuul job result, click "Artifacts" and "Docs preview site".07:24
say3noThanks, I didn’t know I could view the generated artifacts from there.07:24
say3nobut, if the documentation builds successfully, does that mean the content itself is considered OK as long as it looks fine at a glance?07:24
masahito_The build success means "the sphinx syntax is fine in the change.", not "contents of the change is fine."07:26
say3noyep.07:27
say3nohttps://review.opendev.org/c/openstack/masakari-monitors/+/489095 07:27
say3noThis operator guide has been around for a long time and it’s quite large. Would it be reasonable to put a full correctness review of this document on hold for now?07:29
say3noSome contrivuotr has been making small fixes here and there for a long time, so I’d like to support him, but the scope is just too large07:30
masahito_Needs guts for the review.07:31
say3noright07:32
say3nosorry, denwa ga kita07:32
masahito_From my quick glance of the file change list it's mainly to add the new file. So I'm ok to merge it. Let me review it.07:33
say3noI back07:34
say3noThanks. Once you’ve given it a +1, I’ll add a +2 and merge it.07:35
say3no#topic Topic 3: corosync/pacemaker version support in Masakari — how should we handle it at the project/code level? 07:35
say3noTopic 3 is about the Hostmonitor Pacemaker driver implementation in masakari-monitor. I wrote various notes as of January 5, and since then I’ve done some additional investigation on my own and drafted a proposal dated January 19.07:37
masahito_or for the easy fix, new config to check the crmd or not is also fine.07:43
masahito_IIRC, the OpenStack has the basic rule for the supported middleware version. IMO, the easier way is to follow the rule.07:44
masahito_another is to add extra backward compatibility for the old middleware.07:44
say3noi see07:45
masahito_the rule is to follow the package version an official Ubuntu LTS supports.07:45
masahito_let me check the official doument....07:45
say3noOK, so the next action item is to cross-check this against the official documentation.07:46
say3noOK, so the next #action item is to cross-check this against the official documentation.07:47
say3nocan we move on to the next topic?07:48
masahito_i can't fine the doc link.07:48
masahito_sure07:48
say3no#topic 4: Rename corosync/pacemaker driver: `host_handler` to `pacemaker_check` or `corosync_check` 07:49
say3noProbably for historical reasons, what is effectively the Pacemaker driver implementation is currently maintained under the name host_handle. I think this naming is not very user-friendly for people who don’t already know the context.07:52
say3nookay, since we’re close to the end of the scheduled time, would it be okay to carry over topic 4 to the next meeting?07:58
masahito_yup07:59
say3noThank you all for joining today. 08:00
say3no#endmeeting08:00
opendevmeetMeeting ended Mon Jan 19 08:00:46 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:00
opendevmeetMinutes:        https://meetings.opendev.org/meetings/masakari/2026/masakari.2026-01-19-07.11.html08:00
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/masakari/2026/masakari.2026-01-19-07.11.txt08:00
opendevmeetLog:            https://meetings.opendev.org/meetings/masakari/2026/masakari.2026-01-19-07.11.log.html08:00
masahito_say3no: i found a link for the nova's libvirt and qemu supported version matrix. https://docs.openstack.org/nova/latest/reference/libvirt-distro-support-matrix.html08:05
masahito_it's for the supported min version coming of libvirt and qemu installed in the Ubuntu LTS. masakari doens't need to follow the nova's rule, but it's a sample for the min version.08:06
*** b_laci1 is now known as b_laci11:09

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