07:01:01 #startmeeting masakari 07:01:02 Meeting started Tue Sep 1 07:01:01 2020 UTC and is due to finish in 60 minutes. The chair is yoctozepto. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:01:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 07:01:05 The meeting name has been set to 'masakari' 07:01:09 #chair samP 07:01:10 Current chairs: samP yoctozepto 07:01:20 #topic roll-call 07:01:25 \o\ 07:01:57 \o/ 07:02:15 morning devfaz, please put your hands up in the air like you *do* care :D 07:02:32 \o/ :) 07:02:38 that's the spirit 07:02:39 :D 07:03:07 LuisRmz, jopdorp: meeting time :-) 07:03:52 o/ 07:05:29 reusing Tushar's template the next topic is 07:05:34 #topic Critical Bugs and Patches 07:05:55 And there are none but there has not been much triage in the recent time. 07:06:07 If you know about a critical bug, please speak up. 07:08:19 #topic CI health 07:08:47 so the masakari CI is rather healthy; we've been hit by yesterday's setuptools issue that affected all project testing with devstack 07:09:08 #link http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016905.html 07:10:18 otoh, I discovered py38 and lower-constraints jobs were noop except for package installation so I proposed a bunch of fix so please take time to review them: 07:10:20 #link https://review.opendev.org/#/q/owner:radoslaw.piliszek%2540gmail.com+status:open+topic:fix-tox 07:11:39 with gmann we are working on making sure the move to focal is smooth: 07:11:42 #link https://review.opendev.org/#/q/(project:openstack/masakari+OR+project:openstack/masakari-monitors+OR+project:openstack/python-masakariclient+OR+project:openstack/masakari-dashboard)+topic:migrate-to-focal+status:open 07:12:01 there are some issues to be discussed with that still so please do not approve too soon :-) 07:12:26 this one is gtg though: 07:12:28 #link https://review.opendev.org/744343 07:13:21 and there are lots of other smaller fixes that have been proposed, I've approved some trivial ones that I have not authored 07:13:25 others waiting for you 07:13:56 to track everything open against all masakari repos please use: 07:13:58 #link https://review.opendev.org/#/q/(project:openstack/masakari+OR+project:openstack/masakari-monitors+OR+project:openstack/python-masakariclient+OR+project:openstack/masakari-dashboard)+status:open 07:14:26 there is one particular change worth discussing/reviewing and that is by noonedeadpunk: 07:14:34 #link https://review.opendev.org/728629 07:14:48 you can likely ping noonedeadpunk and/or me to discuss it asynchronously 07:15:13 ok 07:15:55 #topic Victoria release planning 07:16:22 it's R-6 for Victoria already: 07:16:24 #link https://releases.openstack.org/victoria/schedule.html 07:16:56 so it's very likely we won't be getting many major features this cycle ;-) 07:17:04 as the feature freeze is next week 07:17:36 the client lib has to be released that week 07:18:26 workitems masakari had for Victoria: 07:18:30 #link https://etherpad.opendev.org/p/masakari-victoria-workitems 07:19:26 it's very unfortunate Sue (suzhengwei) is not here with us because they are the main driver of current changes 07:20:30 there seems to be one goal that looks pretty ready for reviews and should not be overwhelming: 07:20:33 #link https://review.opendev.org/#/q/topic:bp/enable-to-segment+(status:open+OR+status:merged) 07:20:50 please read the blueprint and spec before reviewing so that it's easier to understand 07:23:02 #topic Open discussion 07:23:15 please speak up about anything 07:23:51 I'd like to ask samP to add me and other new cores to https://launchpad.net/~masakari-drivers to be able to coordinate masakari bugs 07:24:47 my other question to samP is: what does the external (NTT) CI tests against masakari? 07:25:03 tbh for the features would be great to have one day protection form split brain... 07:26:07 noonedeadpunk: please expand your thought - masakari depends on corosync so it should protect you from split brain with standard 3-head clusters 07:27:37 So, I wasn't using pacemaker-remote at the first place:) 07:28:05 noonedeadpunk: :-) 07:28:06 So I was deploying pacemaker+corosync on all computes 07:28:18 ah, that could be painful indeed 07:28:19 ah ok, so maybe we should improve the docs ;) 07:28:29 devfaz: ++, my thoughts exactly 07:28:36 they are probably lacking in some places 07:28:47 we are attacking similar problems with kolla 07:28:55 but, when I had connectivity issues (ie one node didn't see all others but all of them see masakari-api), just all nodes were marked in maintenance 07:28:56 telling ppl "how to think about it" 07:29:44 noonedeadpunk: hmm, that's worrying; I think I saw a bug being fixed that might be affecting you 07:29:50 lemme dive in gerrit 07:30:41 noonedeadpunk: https://review.opendev.org/729206 07:30:44 but yeah. for sure I need to look into reconfiguring pacemaker+corosync 07:30:52 #link https://review.opendev.org/729206 07:31:23 noonedeadpunk: true that as well, I've linked you to kolla efforts already but will relink for posterity (and others interested): 07:31:33 oh, it's pretty recent and looks exactly as my cvase I think 07:31:41 #link https://review.opendev.org/670104 07:32:28 noonedeadpunk: it talks about remotes so I'm not 100% sure but otherwise sounds similar to the issue you are describing 07:32:53 noonedeadpunk: please review anyhow; any and all comments help 07:33:20 I will try to implement such deployment for OSA I think 07:33:33 hopefully during this cycle, but no promises) 07:34:19 noonedeadpunk: ++, I like to see openstack deployment projects get better even if I work on the competing ones ;p 07:34:45 (btw, migrate to kolla; let us harvest your soul :-) ) 07:34:56 no, thanks, docker, uh 07:35:00 :p 07:35:09 haha, it works better than you think 07:35:18 I was afraid only at first 07:35:33 turned out to be smoother this way, but it's not the meeting for that discussion :D 07:35:50 we use lxc for that :p 07:35:50 anything else? anyone? 07:39:24 guess not 07:39:29 thank you for today 07:39:35 #endmeeting