14:00:14 #startmeeting nova 14:00:15 Meeting started Thu Apr 18 14:00:14 2019 UTC and is due to finish in 60 minutes. The chair is efried. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:16 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:19 The meeting name has been set to 'nova' 14:00:22 o/ 14:00:28 o/ 14:00:29 \o 14:00:47 o/ 14:00:48 o/ 14:00:51 o/ 14:01:04 #link agenda https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting 14:01:54 #link Minutes from last meeting: http://eavesdrop.openstack.org/meetings/nova/2019/nova.2019-04-11-21.00.html 14:02:03 #topic Release News 14:02:15 o/ 14:02:19 Pike final release to be discussed under stable branch status 14:02:24 anything else for release news? 14:02:46 #topic Bugs (stuck/critical) 14:02:47 No Critical bugs 14:02:47 #link 76 new untriaged bugs (up 2 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 14:02:47 #link 11 untagged untriaged bugs (up 1 since the last meeting): https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW 14:03:00 any bugs to highlight? 14:03:39 yeah 14:03:49 but i guess that's in stable section 14:03:59 http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005242.html 14:04:06 mm 14:04:31 we have a few upgrade impacting stein regressions, 14:04:42 since we just GA'ed stein, it'd be good to get those fixed and released before people upgrade 14:05:03 if this was pre-GA these would have probably been RC candidates 14:05:05 so like within the next three years? 14:05:15 too soon 14:06:06 anywho, an easy start is the func recreate regression test patches: https://review.openstack.org/#/c/653098/ 14:06:28 https://review.openstack.org/#/c/653268/ 14:07:30 * efried opens tabs 14:08:03 that it for now? 14:08:22 for release news 14:08:23 sure 14:08:27 i guess 14:08:31 Gate status 14:08:31 #link check queue gate status http://status.openstack.org/elastic-recheck/index.html 14:08:31 mdbooth: any update on https://bugs.launchpad.net/nova/+bug/1823251 ? 14:08:32 Launchpad bug 1823251 in OpenStack Compute (nova) "Spike in TestNovaMigrationsMySQL.test_walk_versions/test_innodb_tables failures since April 1 2019 on limestone-regionone" [High,Confirmed] 14:09:07 mdbooth isn't here I guess 14:09:09 3rd party CI 14:09:09 #link 3rd party CI status http://ciwatch.mmedvede.net/project?project=nova&time=7+days 14:09:28 This ^ has seemed a tad wonky to me lately, got a question out to mmedvede about it. 14:09:40 #link sean-k-mooney is working on getting the NFV job in tree https://review.openstack.org/#/c/652197/ 14:09:44 sean-k-mooney: your mic 14:10:17 ok so there are a number of related ci topics but to start with 14:10:43 that job is intended to replace teh testing done by the intel nfv ci 14:11:05 currently it is running a small subset of test which i hope to expand 14:11:19 it has more feature enabeld the the intel nfv ci (like realtime) 14:11:28 but cannot test multi numa guest 14:11:47 to do that we would need a multi numa host vm form nodepool 14:12:00 o/ 14:12:06 i intend to create a seperate job to test ovs-dpdk integretion 14:12:33 again bare multi numa testing thos two jobs will provide parity with the intel nfv ci 14:13:12 the main enabler of this is the qemu MTTCG backend and that will also be the main delta between how the intel nfv ci ran the test and upstream 14:13:28 they used nested virt this will use the multi thread tcg backend 14:14:05 to do this we need libvirt 5.2 and a new qemu so that forces use to use fedora 29 and the virt preview repo 14:14:35 as a result the stablity may be quetionable so i would like to keep them non voting until we have evidence that it is stable 14:14:55 throw it in the experimental queu 14:14:56 *queue 14:15:01 rather than check queue non-voting 14:15:05 then you can run it on-demand 14:15:31 i could do that i woudl like it to run on all changes to the libvirt driver 14:15:45 would you object if i did both but limited the check queue to that? 14:16:07 we should talk about it later elsewhere 14:16:19 ok well that was the main update 14:16:29 Thanks sean-k-mooney 14:16:35 we have a ptg session to discuss testing in general too 14:16:35 definitely thanks for working on this 14:16:53 #topic Reminders 14:16:56 any? 14:17:15 #topic Stable branch status 14:17:15 #link Stein regressions: http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005242.html 14:17:15 ...as discussed above 14:17:24 #help Need to flush the stable branch reviews so we can put pike into extended maintenance mode: 14:17:24 #link pike-em potential etherpad https://etherpad.openstack.org/p/nova-stable-pike-em 14:17:24 #link final nova release for pike https://review.openstack.org/#/c/652868/ 14:18:02 i'll spend this morning populating that etherpad and bugging stable cores 14:18:10 though i've got charts to work on... 14:18:17 Thanks mriedem 14:18:26 yay charts :$ 14:18:35 is that a mustache? 14:18:45 some kind of grimace maybe 14:19:28 #link stable/stein: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/stein 14:19:28 1 patch needing second +2/+W 14:19:28 2 patches needing review 14:19:35 #link stable/rocky: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/rocky 14:19:35 2 patches need second +2/+W 14:19:35 2 patches needing review 14:19:42 #link stable/queens: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/queens 14:19:42 1 patch needs second +2/+W 14:19:42 7 needing core reviews 14:19:48 #link stable/pike: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/pike 14:19:48 5 patches needing core reviews 14:19:48 See above 14:20:03 #topic Sub/related team Highlights 14:20:03 Placement (cdent) 14:20:42 we talked about the emails and how there will be more emails (and there were) 14:20:44 EOM 14:21:20 API (gmann) 14:21:20 No separate updates. Spec reviews are in progress. 14:21:26 anything else gmann? 14:21:40 yeah, spec review going on. lock detail spec is merged and other under review 14:21:54 that's all for today 14:21:57 thanks gmann 14:21:59 #topic Stuck Reviews 14:22:00 any? 14:22:27 #topic Forum Planning 14:22:27 See meeting agenda for a list of nova-ish forum sessions. Feel free to add any I missed. 14:22:51 #topic PTG Planning 14:22:51 #link PTG: Nova etherpad https://etherpad.openstack.org/p/nova-ptg-train 14:22:51 links from ^ to various other etherpads 14:23:02 I'll be trying to put together some kind of schedule over the next week 14:23:26 so please get your topics into the etherpads so they're stable-ish for when I'm cutting and pasting stuff around. 14:24:01 efried: do we need to have cross project sessions with keystone for 'Nova API policy updates' L214 ? 14:24:18 there was question on that and it is good idea 14:24:18 cmurphy, lbragstad: thoughts ^ ? 14:24:20 there is a forum session on that right? 14:24:45 * lbragstad reads 14:24:50 forum is more giving general updates ? but not sure we can specifically discuss nova cases 14:25:24 https://www.openstack.org/summit/denver-2019/summit-schedule/events/23642/increasing-api-accessibility-with-granular-policy-and-default-roles 14:25:25 #link https://www.openstack.org/summit/denver-2019/summit-schedule/events/23642/increasing-api-accessibility-with-granular-policy-and-default-roles 14:25:29 i win 14:25:30 I was wondering about unified limits, in a similar vain 14:25:35 * lbragstad shakes fist 14:25:40 johnthetubaguy: https://www.openstack.org/summit/denver-2019/summit-schedule/events/23641/unified-limits-update-and-migration 14:26:10 thanks, I should read more of that schedule 14:26:45 gmann: my question is what would be new at this ptg from previous ptgs if we have a xp session on this? 14:26:45 we have a slot in our agenda for following up on forum discussions to see if we want further ptg discussion, we can go ahead and plan for a cross project session ahead of time if you guys want 14:27:01 #link https://etherpad.openstack.org/p/DEN-granular-policy-and-default-roles 14:27:11 #link https://etherpad.openstack.org/p/DEN-unified-limits 14:27:28 mriedem: we have spec ready now about what all steps and updates. 14:28:01 i am ok if we can get keystone review/suggestion in forum and then discuss nova specific plan in nova ptg only 14:28:03 ^ those etherpads are for the forum, but there are sections for the ptg bits that cmurphy talked about 14:28:31 we're hoping to keep the content in the forum applicable to operators - and push dev-specific discussions to the ptg 14:28:53 (in an effort to make the most of the time we have with ops and users at the forum) 14:29:09 I'll get with y'all later to schedule a slot on Friday. Meanwhile, can someone please chop the relevant bits out of the main etherpad and create a nova-keystone xproj etherpad for them? 14:29:47 efried feel free to reuse the ptg sections in the etherpads we have already if you'd like 14:30:29 our ptg agenda fwiw https://etherpad.openstack.org/p/keystone-train-ptg 14:30:57 okay, thanks, I'll catch up with you later to work out the details. 14:31:11 thanks efried 14:31:15 thanks 14:32:17 Generally about the PTG: I'm pretty concerned about timing. We basically have one day for general nova topics. Because Friday is xproj and Saturday is going to be pretty weak, what with some key people already gone and others promising to be grumpy. 14:32:17 So I'm basically going to front-load the stuff I think is important, and try as much as possible to time-box the topics. 14:32:17 What this means is, once I've drafted the agenda, you should look at it and yell at me if something seems pushed too far back or given too little time. 14:32:48 i agree with that plan 14:32:55 ditto 14:32:57 and sympathize with trying to organize 14:33:02 +1 14:33:04 did i just rap? 14:33:13 thanks. Here's my grimace again :$ 14:33:39 #topic Open discussion 14:33:45 anything? 14:33:50 i have two topics 14:33:56 (belated o/) 14:34:07 hit it sean-k-mooney 14:34:19 speclesss blurint for extending libvirt video device models 14:34:20 #link https://blueprints.launchpad.net/nova/+spec/libvirt-video-device-models 14:34:22 this is basically extending an enum with some minor verion check in the driver 14:34:24 i have implemented it already here 14:34:26 https://review.openstack.org/#/q/topic:bp/libvirt-video-device-models 14:34:44 so basically im asking for approval of the specless blueprint 14:35:11 i also have an update on bug 1822884 14:35:13 bug 1822884 in OpenStack Compute (nova) "live migration fails due to port binding duplicate key entry in post_live_migrate" [Undecided,In progress] https://launchpad.net/bugs/1822884 - Assigned to sean mooney (sean-k-mooney) 14:35:13 #link https://bugs.launchpad.net/nova/+bug/1822884 14:35:50 NewBruce applied https://review.openstack.org/#/c/653609/ and i appears to fix the issue. 14:36:14 it still needs work but i think we have a path forward 14:36:34 those are the too topics 14:36:56 anyone object to approving the video model bp? 14:37:17 seems pretty straight-forward, add support for gop and none based on libvirt version and feature support capabilities yeah? 14:37:24 the latter maybe depending on kashyap's blueprint? 14:37:27 for those new libvirt apis? 14:37:30 mriedem: yep 14:37:41 * kashyap blinks 14:37:57 mriedem: it also ties into my image metadata prefiltering spec 14:37:58 mriedem: What is "gop"? 14:38:06 https://libvirt.org/formatdomain.html#elementsVideo 14:38:14 uefi grapichs output 14:38:19 protocol 14:38:41 (Nod) 14:38:46 we also had partil supprot for vitio before 14:38:53 now you will be able to request it 14:39:01 before it was enabled by default on arm 14:39:01 so i think i'm a +1 on the specless bp 14:39:06 but you could not request it 14:39:53 kashyap: you good with this, since you're a) libvirt savvy, b) here? 14:40:06 (Yes, I'm here.) 14:40:15 and c) involved apparently, owning a dep 14:40:17 efried: I need to look at it properly; don't want to hurry it in this meeting. 14:40:35 oops my bad 14:40:36 efried: there isnt really a dep on kashyap's work 14:40:36 i'm not sure there is a hard dependency really, sean already has code up 14:40:52 sean-k-mooney: Yeah, it is not dep on any work I'm doing, actually. 14:41:14 Okay, so strike c). 14:41:14 If nobody has objections, I'll catch up with kashyap later and approve the bp if he's on board, cool? 14:41:32 ++ 14:41:39 Nod 14:41:50 efried: Got two more mins so I can "plug" something here? 14:41:52 works for me :) 14:42:05 kashyap: Open discussion, go for it 14:42:42 I'd appreciate some more eyes on the spec: Secure Boot for KVM/QEMU guests — https://review.openstack.org/#/c/506720/ 14:42:53 It already had some feedback from folks here. 14:43:25 (And I'm working with Debian and Ubuntu folks to also get the relevant low-level virtual firmware deps in place.) 14:44:32 (Might want to wait for PS-12, will push out 'soon'. I've simplified some more bits in the spec.) 14:44:34 kashyap: have the windriver people been looking at that? 14:44:39 b/c they care about uefi 14:45:10 I was looking for ChrisF the other day 14:45:14 Will ping him today 14:45:29 ala https://review.openstack.org/#/c/621646/ 14:45:32 you mean cfriesen 14:45:39 mriedem: I've left periodic updates in the spec over the year. It needed a lot of work in EDK2/OVMF (the virtual firmware), QEMU, libvirt et al 14:46:33 mriedem: Ah, thanks for that pointer. I saw that in passing 14:46:37 mriedem: But Jack Ding seems to be AWOL? 14:47:02 idk 14:47:03 jack ding i think got pulled off nova work form talking to cfriesen 14:47:16 i dont know if that was tempory or permenent 14:47:30 that is why cfriesen took over some of his pathces 14:47:50 Okay, that's a separate one. I'll ping cfriesen to take a look at the SB stuff 14:48:18 mriedem: BTW, this is the general Secure Boot support for KVM/QEMU guests -- similar to the one you help landed for the Hyper-V 14:48:30 (I think you'll recall; as I saw your name when I was doing code audit.) 14:48:36 * mriedem doesn't remember 14:48:38 efried: That's it. Don't want to elaborate further here. 14:48:44 Can talk on the -nova channel 14:48:56 Okay, any other opens before close? 14:49:22 Thanks all. 14:49:22 o/ 14:49:22 #endmeeting