07:00:27 #startmeeting masakari 07:00:28 Meeting started Tue Nov 10 07:00:27 2020 UTC and is due to finish in 60 minutes. The chair is yoctozepto. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:00:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 07:00:31 The meeting name has been set to 'masakari' 07:00:39 #topic Roll-call 07:00:46 \o/ 07:03:05 #topic Agenda 07:03:21 * Roll-call 07:03:24 * Agenda 07:03:27 * Announcements 07:03:30 ** OpenStack Victoria Release Community Meeting - Thu 2020-11-12 16:00 UTC (yoctozepto presenting Masakari) 07:03:34 ** Teams cleanup http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018542.html 07:03:38 * Review action items from the last meeting 07:03:42 * CI status 07:03:45 * Backports pending reviews 07:03:49 ** Should we release the non-current stable branches? 07:03:53 * Release planning 07:03:56 ** Review action items from the Wallaby vPTG https://etherpad.opendev.org/p/masakari-wallaby-vptg 07:04:01 * Open discussion 07:04:08 #topic Announcements 07:04:22 #topic OpenStack Victoria Release Community Meeting - Thu 2020-11-12 16:00 UTC (yoctozepto presenting Masakari) 07:04:30 #undo 07:04:31 Removing item from minutes: #topic OpenStack Victoria Release Community Meeting - Thu 2020-11-12 16:00 UTC (yoctozepto presenting Masakari) 07:04:47 #topic Announcements 07:04:59 #info OpenStack Victoria Release Community Meeting - Thu 2020-11-12 16:00 UTC (yoctozepto presenting Masakari) 07:05:28 please be informed that this week is the OpenStack Community Meeting for Victoria 07:05:43 I will be presenting Masakari so you might be interested 07:06:00 other projects will present themselves too 07:06:07 feel welcome to join 07:06:37 #info Teams cleanup http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018542.html 07:06:46 I plan to clean the teams up tomorrow 07:07:14 please read the linked message and reply if needed 07:07:56 #topic Review action items from the last meeting 07:08:19 There were no action items assigned during the previous meeting 07:08:39 #topic CI status 07:09:22 Masakari not running periodics so hard to tell; generally green 07:10:54 #action yoctozepto to add periodic jobs to masakari 07:11:19 #topic Backports pending reviews 07:12:37 #link https://bit.ly/2UeoIiN 07:13:01 so there are those 3 pending for the dashboard 07:13:35 I can't access the link https://bit.ly/2UeoIiN 07:13:49 oh 07:14:17 that is a very important feedback, thank you 07:15:12 I (among others) have been shortening the links in places where the long ones are hard to read, but if they are blocked in China, it does not make sense to use them 07:15:24 #undo 07:15:25 Removing item from minutes: #link https://bit.ly/2UeoIiN 07:15:30 #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+-branch:master 07:15:38 ugly but worky :D 07:16:45 thanks 07:17:33 #action yoctozepto to replace bit.ly links with their long forms 07:19:37 well, back to the topic - please review those, I will self-approve tomorrow if nobody does before 07:19:50 though I would like to avoid that 07:20:13 #topic Should we release the non-current stable branches? 07:20:55 the topic is the question but also: Do you know of a change worth of backporting that has not been backported? 07:22:00 No. Mostly backpoered. 07:22:37 please let me know by tomorrow if you find something worthy of backporting (or just backport yourselves) 07:22:48 ok 07:22:55 I will propose stable releases then to let the public benefit from all the accumulated patches 07:23:26 (and to show that the project is alive) 07:24:34 ping 07:24:41 suzhengwei_: pong 07:25:05 #topic Release planning 07:25:19 #topic Review action items from the Wallaby vPTG https://etherpad.opendev.org/p/masakari-wallaby-vptg 07:26:20 has anyone had a chance to do something about the assigned actions? 07:26:45 * yoctozepto did something, yes 07:27:09 well, then, please share, yoctozepto 07:27:49 (suzhengwei) Enable/Disable evacuation segment wise +1+1 -- TODO(yoctozepto): check nova and other projects regarding this 07:27:52 and so I did 07:28:01 the result is on the whiteboard 07:28:15 http://codesearch.openstack.org/?q=disabled.*BooleanField&i=nope&files=&repos= 07:28:20 thanks, I will check it later. 07:28:20 http://codesearch.openstack.org/?q=disabled.*Column&i=nope&files=&repos= 07:28:25 nova and cinder seem to prefer 'disabled' because of the default (disabled=False) making most sense 07:28:28 suzhengwei_: thanks! 07:29:00 so I felt right that we should rather call it 'disabled' as that is the accepted practice 07:30:10 suzhengwei__: unstable connection, huh? 07:30:20 yep 07:30:33 suzhengwei__: worry not, you will be able to read all the logs/summary afterwards 07:31:02 #action suzhengwei to reflect upon yoctozepto's findings about disabled/enabled 07:31:16 the next one I have done is 07:31:26 (nautik) Way to disable instance evacuation if operator defaults to evacuating all instances +1+1 -- TODO(yoctozepto): check how it could be possible in the current state 07:31:37 DONE(yoctozepto): I confirm it is entirely impossible 07:31:58 well, this one was pretty simple; indeed there is no way to have this scenario currently 07:33:27 I left an anonymous TODO if anyone wants to pick up and move this further 07:33:38 and finally 07:33:39 yes, there is no perfect solution. 07:33:53 (yoctozepto/nautik) what do `control_attributes` do? (apparently nothing!) -- TODO(yoctozepto,jopdorp,suzhengwei,nautik): verify in code 07:34:00 DONE(yoctozepto): 07:34:04 monitors do not care at all 07:34:08 engine does not care at all 07:34:14 API requires it present and stores it in the database (no further actions on it) 07:34:26 this is basically the summary (also available in the etherpad) 07:34:59 I doubt others assigned really need to go over this but please feel welcome to do so 07:36:02 me too 07:37:40 I left another anonymous TODO for anyone wishing to proceed further 07:37:55 that is all I have done regarding the PTG actions 07:38:01 anyone else? 07:38:12 (mostly asking suzhengwei__ because all others are silent today) 07:38:35 retry check when host failure. 07:39:06 I have a rough code change. https://review.opendev.org/#/c/761704/ 07:39:44 #link https://review.opendev.org/761499 07:39:46 ^ spec 07:40:48 #link https://review.opendev.org/761704 07:40:54 ^ reference implementation 07:41:05 I have updated the PTG etherpad as well with this information 07:41:07 thanks suzhengwei__ 07:41:34 wait for response from you. 07:41:48 I have added the spec to my queue of reviews 07:41:54 thanks 07:42:19 anyone else? anything else? 07:42:46 no. 07:43:15 #topic Open discussion 07:43:43 please let me know if there is anything to discuss at this moment 07:44:35 #action yoctozepto to switch masakari focus in launchpad from victoria to wallaby 07:45:04 #action yoctozepto to clean teams up 07:45:12 #action yoctozepto to release stable branches 07:45:27 (I have just done a summary of extra actions for me) 07:48:03 We can finish the meeting earlier:) 07:53:58 yeah, I wanted to give others time 07:54:13 thank you suzhengwei__ for attending 07:54:17 #endmeeting