21:02:50 <mriedem> #startmeeting nova
21:02:51 <openstack> Meeting started Thu Dec  8 21:02:50 2016 UTC and is due to finish in 60 minutes.  The chair is mriedem. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:02:52 <edleafe> ooh, that was sneaky!
21:02:53 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:02:55 <openstack> The meeting name has been set to 'nova'
21:03:03 <mriedem> well we should have some super interesting logs
21:03:03 <melwitt> o/
21:03:05 <takashin> o/
21:03:12 <edleafe> \o
21:03:12 <auggy> :P
21:03:15 <dtp> o/
21:04:02 * Vek waves
21:04:29 <mriedem> ok so let's get started
21:04:31 <mriedem> #link agenda https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
21:04:42 <mriedem> #topic release news
21:04:51 <mriedem> #link Ocata release schedule: https://wiki.openstack.org/wiki/Nova/Ocata_Release_Schedule
21:05:06 <mriedem> #info next thursday 12/15 is the o-2 milestone
21:05:16 <mriedem> #link Ocata blueprints https://blueprints.launchpad.net/nova/ocata
21:05:22 <mriedem> #info 69 total blueprints, 8 implemented, 10 not started, 37 need code review, 10 implemented
21:05:31 <mriedem> oops some stale data in there
21:05:49 <mriedem> so still a few blueprints that haven't started
21:05:53 <mriedem> which is concerning
21:06:02 <mriedem> i tried bugging some people in irc the other day
21:06:16 <mriedem> but honestly we have enough code up for review for other blueprints at this point i'm not going to chase people much
21:06:41 <mriedem> any questions?
21:06:51 <mriedem> #topic bugs
21:07:20 <mriedem> sdague helped out with triage yesterday and took a pretty good chunk out of the new bugs list, so thanks there
21:07:33 <mriedem> one i came across which isn't really new but wasn't being worked is https://launchpad.net/bugs/1633734
21:07:33 <openstack> Launchpad bug 1633734 in OpenStack Compute (nova) "ValueError: Field `instance_uuid' cannot be None" [High,Confirmed]
21:07:41 <mriedem> so ^ is an upgrade issue from mitaka to newton
21:07:50 <mriedem> i've started a repro patch here https://review.openstack.org/#/c/408727/
21:08:09 <mriedem> it's tricksy, and i think we need an invalid data purge migration in newton to handle it
21:08:20 <mriedem> but i'm not sure if it's an offline data migration or online
21:08:26 <mriedem> so need to talk to some people about that later
21:08:49 <mriedem> otherwise we don't have any critical bugs
21:09:04 <mriedem> gate status and 3rd party ci status are relatively uneventful
21:09:10 <mriedem> i've noticed the intel nfv ci went away
21:09:13 <mriedem> wznoinsk: are you around?
21:09:32 <mriedem> i'll follow up on that later
21:09:40 <mriedem> i know they were working through some issues with their multinode job
21:09:46 <mriedem> anyone else for bugs?
21:09:55 <wznoinsk> Yes should be back tomorrow
21:10:01 <mriedem> wznoinsk: cool
21:10:11 <mriedem> #topic reminders
21:10:19 <mriedem> #link Ocata review priorities https://etherpad.openstack.org/p/ocata-nova-priorities-tracking
21:10:30 <mriedem> i haven't been through ^ lately so know how up to date it is
21:10:34 <kristian__> Hi im back
21:10:41 <mriedem> cdent has been sending out priorities for resource provider work in the ML
21:11:02 <mriedem> #topic stable branch status
21:11:16 <mriedem> not much to report here except liberty should be eol soon
21:11:21 <mriedem> tonyb was putting in the request to infra for that last night
21:11:43 <kristian__> Can I propose an idea?
21:11:45 <mriedem> and lyarwood cleaned out a lot of stable/mitaka stuff that wasn't appropriate
21:11:59 <mriedem> kristian__: does it have to do with stable branches?
21:12:09 <mriedem> kristian__: because if not, please save it for open discussion
21:12:28 <kristian__> its about gpu passthrough
21:12:32 <mriedem> yeah so not right now
21:12:39 <mriedem> any questions on stable?
21:12:54 <mriedem> moving on
21:12:58 <mriedem> #topic subteam highlights
21:13:26 <mriedem> for cellsv2, the main review focus right now is on the series starting here https://review.openstack.org/#/c/406380/
21:13:44 <mriedem> melwitt: was there anything else from the cells meeting yesterday you wanted to bring up? like consoleauth or quotas?
21:14:26 <melwitt> sure, I can note that for cells v2 we need to change the deployment assumption from consoleauth service at the top to consoleauth service per cell
21:14:41 <mriedem> #info for cells v2 we need to change the deployment assumption from consoleauth service at the top to consoleauth service per cell
21:15:00 <melwitt> nothing yet on quotas, I'll have something next week
21:15:12 <mriedem> melwitt: do we have changes we need to work for consoleauth for cells v2 right now?
21:15:54 <melwitt> yes, brought up in the meeting was that we need the message queue switching stuff in consoleauth/rpcapi.py like we have in compute/rpcapi.py. dtp volunteered to add that
21:16:23 <mriedem> #info dtp volunteered to work on adding mq switching to consoleauth/rpcapi.py
21:16:29 <mriedem> cool
21:16:39 <mriedem> moving on
21:16:41 <mriedem> edleafe: scheduler?
21:16:45 <edleafe> Discussed whether optional placement DB was going to make it into Ocata. Decision was "meh"
21:16:48 <edleafe> Discussed remotable vs non-remotable, but that was pretty quiet because bauzas wasn't there :)
21:16:51 <edleafe> Agreed to bump the limit on retries for ResourceClass ID generation, with logging added to see if we ever hit it.
21:16:54 <edleafe> Didn't argue the GET vs. POST and/or new resource for querying resource providers - again, no bauzas
21:16:57 <edleafe> done
21:17:06 <mriedem> the non-remotable patch is up from cdent
21:17:11 <bauzas> oh man, missed the meeting
21:17:14 <bauzas> \o
21:17:16 <mriedem> i'm also meh on optional placement db
21:17:28 <edleafe> bauzas: we missed you too :)
21:17:51 <mriedem> and jaypipes has the GET /resource_providers filtering patch up, i just haven't gotten there yet
21:18:04 <mriedem> more info on the GET vs POST thing is in the dev ML
21:18:11 <mriedem> tdurakov: are you around?
21:18:12 <bauzas> mriedem: I squashed the patch
21:18:15 <mriedem> bauzas: yup
21:18:36 <mriedem> i don't have any notes for the live migration meeting
21:18:42 <mriedem> so moving on
21:18:48 <mriedem> sdague: did you make the api meeting this week?
21:19:13 <mriedem> re: api, the last remaining spec we need for ocata is https://review.openstack.org/#/c/393205/
21:19:21 <mriedem> and because i'm a terrible person i haven't gone back to review it yet
21:19:22 <mriedem> but need to
21:19:26 <mriedem> as does everyone else
21:19:44 <mriedem> that's the one about restricting the server list sort/filter parameters
21:20:05 <mriedem> thanks for Kevin_Zheng for continuing to update the spec
21:20:10 <mriedem> s/for/to/
21:20:16 <mriedem> moving on
21:20:23 <mriedem> sriov/pci - lbeliveau?
21:20:29 <mriedem> is that bi-weekly now and this wasn't the week?
21:20:45 <mriedem> i know moshele wants reviews on the pci whitelist regex patch
21:20:59 <mriedem> https://review.openstack.org/#/c/199488/
21:21:04 <mriedem> looks like jay got a review on it today
21:21:19 <jaypipes> mriedem: yeh, still working through that one.
21:21:21 <mriedem> ok moving on again (damn quiet in here today)
21:21:27 <mriedem> jaypipes: thanks
21:21:35 <mriedem> gibi: are you around for notifications highlights?
21:21:43 <jaypipes> mriedem: I'm still chugging through mdbooth's libvirt imagebackend patch series.
21:21:46 <kristian__> mriedem: ping me when I can post my idea
21:21:54 <jaypipes> mriedem: and a few of the flavor notifications series.
21:22:12 <mriedem> yar
21:22:21 <mriedem> so on the notification subteam, they have things ready for review in https://etherpad.openstack.org/p/ocata-nova-priorities-tracking
21:22:23 <mriedem> L177
21:22:36 <mriedem> they are pretty mechanical and easy to review for people looking for something to review
21:23:01 <mriedem> #topic stuck reviews
21:23:16 <mriedem> nothing on the agenda, did anyone have anything they wanted to bring up?
21:23:31 <mriedem> #topic open discussion
21:23:35 <mriedem> kristian__: go
21:23:43 <kristian__> #idea Can there be a metadata option to attach gpu as a main display source?
21:24:03 <mriedem> as in image metadata?
21:24:34 <kristian__> no in a flavor
21:24:44 <mriedem> so a flavor extra spec
21:24:50 <kristian__> yes
21:25:01 <mriedem> which virt drivers support that?
21:25:25 <mriedem> i.e. we generally want things like this to be supportable across the hypervisor drivers
21:26:31 <kristian__> don't know but it should be possible on vanilla qemu/kvm, because I have it running like that in proxmox and before that normally on arch as a "second pc"
21:26:32 <mriedem> kristian__: i don't know the details, it'd probably be something that needs a spec
21:26:51 <mriedem> to detail how this would be handled in the libvirt driver
21:27:05 <mriedem> and then get the other virt driver maintainers to weigh in on if they could support the feature too
21:28:00 <mriedem> kristian__: do you have any other questions about that?
21:28:09 <mriedem> note that we're not accepting new specs for the current ocata release
21:28:11 <kristian__> it should work natively but novnc will not work
21:28:14 <mriedem> so this would have to be proposed for the pike release
21:28:23 <kristian__> ok np
21:28:41 <mriedem> the nova-specs repo has the pike structure now though so you can start working on the spec and propose it for the next release
21:28:51 <mriedem> details about novnc not working would be good to have in there
21:29:16 <mriedem> sahid might be a good person on the libvirt driver team to talk to about this
21:29:31 <mriedem> ok, anyone else for anything else?
21:29:39 <jaypipes> mriedem: not from me.
21:29:50 <mriedem> me neither
21:29:54 <kristian__> mriedem: could you propose that spec? because Im not a python and or openstack dev
21:30:00 <mriedem> kristian__: nope
21:30:13 <mriedem> kristian__: you could write it up as a backlog spec
21:30:28 <mriedem> backlog specs in the nova-specs repo are just basically laying out a high level idea with some details,
21:30:41 <kristian__> mriedem: where?
21:30:42 <mriedem> and then if a developer is interested in working on implementing it, they can take the backlog spec and flesh it out
21:30:54 <mriedem> kristian__: https://specs.openstack.org/openstack/nova-specs/specs/backlog/index.html
21:31:26 <mriedem> the spec template is a guide for what to put in the doc, and where you can stop if you're just doing a backlog spec
21:31:47 <mriedem> backlog specs aren't tied to a given release, they are just a way to put out a feature request / idea
21:31:56 <mriedem> you don't need to know python, just to write up the idea
21:32:20 <mriedem> kristian__: if you have more questions you can ask in the #openstack-nova channel after the meeting
21:32:25 <mriedem> which i'm going to end, now
21:32:27 <kristian__> ok
21:32:28 <mriedem> thanks everyone
21:32:31 <mriedem> #endmeeting