21:01:08 <efried> #startmeeting nova
21:01:09 <openstack> Meeting started Thu Aug 29 21:01:08 2019 UTC and is due to finish in 60 minutes.  The chair is efried. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:01:10 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:01:13 <openstack> The meeting name has been set to 'nova'
21:01:52 <mriedem> o/
21:01:59 <aspiers> o/
21:06:03 <efried> #link agenda https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
21:06:25 <efried> if it's just the three of us, I'm going to skip the agenda and just ask if y'all want to talk about anything.
21:07:15 <mriedem> not really
21:07:31 <efried> These 2100 meetings seem to be pretty sparse of late. Wondering if we should move or drop them. I think the only people who miss the 1400 ones routinely are west-coasters
21:07:33 <aspiers> Nothing really, just to say that stephenfin stuck SEV on the runway this morning and it should all be ready to go
21:07:48 <aspiers> I just cut it over to use his new scheduler/utils.py thing
21:07:53 <efried> cool
21:08:03 <efried> glad to see that merged. It's gonna make some things simpler
21:08:16 <efried> There's this:
21:08:16 <efried> (melwitt): I'm out on PTO today and tomorrow but wanted to seek approval for a specless blueprint https://blueprints.launchpad.net/nova/+spec/policy-rule-for-host-status-unknown
21:08:16 <efried> I have uploaded code to hopefully help with approval: https://review.opendev.org/679181
21:08:31 <aspiers> but the thing with moving vcpus etc. over to requested_resources still needs to be done, right?
21:08:58 <efried> aspiers: Yes
21:09:13 <aspiers> it's all gradually beginning to make a bit more sense to me
21:09:47 <efried> That 'host status UNKNOWN' thing sounds really familiar.
21:09:57 <efried> I thought we already talked about this a couple weeks ago.
21:10:11 <efried> o look, notes in the whiteboard
21:11:54 <efried> So... without digging into this more, I'm not going to be able to render an opinion
21:12:11 <efried> mriedem: can you tell at a glance whether this conforms to your suggestions?
21:12:26 <mriedem> i haven't reviewed the change
21:12:34 <efried> If we get your ack, we can kind of assume gibi's, based on his note there
21:13:01 <efried> would be nice to get lbragstad's nod too
21:13:16 <efried> but... does it really make sense for us to be approving a blueprint two weeks before FF?
21:13:49 <mriedem> i'd rather not
21:13:58 <mriedem> especially when it touches the api
21:14:13 <mriedem> and the code was posted yesterday
21:14:55 <efried> yeah, unless there's some reason this is important enough to preempt cores reviewing other stuff that's been approved & coded for a long time, I don't think it makes sense to add this straw to the camel's back.
21:15:54 <efried> without melwitt here to argue that justification, I think we have to assume
21:16:04 * efried draws red X
21:17:00 <mriedem> :x duh duh duh
21:17:57 <efried> okay, anything else to talk about?
21:18:06 <mriedem> not from me
21:18:26 <efried> allllrightythen
21:18:26 <efried> o/
21:18:26 <efried> #endmeeting