13:00:56 #startmeeting PCI passthrough 13:00:57 Meeting started Tue Oct 28 13:00:56 2014 UTC and is due to finish in 60 minutes. The chair is baoli. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:58 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:01:00 The meeting name has been set to 'pci_passthrough' 13:01:04 Hi there 13:01:15 hi 13:01:59 updated the meeting wiki https://wiki.openstack.org/wiki/Meetings/Passthrough#Agenda_on_Oct._28th.2C_2014 13:03:48 Hi 13:04:04 hi 13:04:09 baoli: Thanks! 13:04:35 reposting https://wiki.openstack.org/wiki/Meetings/Passthrough#Agenda_on_Oct._28th.2C_2014 13:05:30 I started tagging sr-iov/pci-passthrough related bugs with pci-passthrough 13:06:08 baoli++ 13:06:29 baoli: started looking at your patches but didn't get through them 13:06:57 Please tag bugs with pci-passthrough as you see fit. 13:07:11 baoli: I'll use the same on neutron side as well 13:07:31 is there a Nova session on current pci-passthrough changes at the summit? 13:07:49 there are two links: one for nova, one for neutron, to find bugs with that tag 13:08:07 sadasu, I just checked but didn't see one 13:09:27 I do not think there is 13:10:10 I think we can meet at pod to discuss 13:11:02 summit sessions ae more for talks to reach consensus and not update on progress 13:13:19 there are a bunch of Cross-project workshop, but they are not finalized yet 13:13:54 sorry, my connection flapped 13:13:59 did I miss anything? 13:14:53 test 13:14:58 sadasu, not really. no talk scheduled for pci-passthrough at the summit. We're saying if we want to meet at pod 13:15:21 ok. +1 for meeting at the pod 13:15:51 sometime on Monday? 13:16:11 works for me 13:16:55 need to see if there is some schedule for pod time sharing 13:18:00 Monday morning or afternoon? 13:18:34 Let's send proposal over emails, once finalize the schedule 13:18:54 that works. 13:19:04 irenab: ok. when are you getthing there? 13:20:21 I am joing the upsteam training, so will be there over weekend 13:21:33 sadasu: when do you arrive? 13:22:24 Sunday morning 13:23:17 sadasu: cool, we can meet at Sunday evening 13:23:38 baoli: there is recent ml thread regarding pci whitelist format, do we want to discuss it here? 13:24:01 irenab, sure 13:24:22 but I'm not clear what it is breaking now 13:24:51 irenab, you are referring to sdague's comments? 13:25:08 beagles: yes 13:26:09 He suggests quite reasonable solution with additional file, but I remember when we proposed it initially it has some objections 13:26:46 yeah... I was always under the impression that the current pci whitelist was a sort of interim solution - with some folks wanting a more centrally manageble configuration. 13:27:05 beagles: I agree 13:27:31 so maybe we should be looking in that direction instead. As an admin and deployment thing, I would expect the NFV crowd having some thoughts on this. 13:28:56 beagles: do you have any idea how they want it to be managed? 13:29:24 API, auto-discovery, other.... 13:29:29 irenab, no idea. 13:30:08 irenab, I'm trying to recall who mentioned it in Atlanta .. Adrian maybe? 13:30:34 yeah, from the emails, i am only able to gather what is not preferred... 13:30:56 I'll fire a reply to the ML about that whitelist being an interim solution if that's okay with everyone 13:31:06 beagles: +1 13:31:52 Initially I had the impression that Sean doesn't like how it's configured through devstack. But it seems he intended to change how it's configured in nova. Right? 13:32:23 baoli: I think so 13:32:29 seems that way 13:32:49 baoli: from the emails..it does seem that way 13:34:03 is there any specific topic we want to discuss at the summit? maybe worth to advertise once we set a time and location for others to join 13:34:06 But, I am not sure if having another file for the pci passthrough config and giving a pointer to that in nova config would be a widely accepted solution either 13:34:27 Regarding whether or not it's an interim solution, keep in mind that's how it was from the very beginning of PCI passthrough. 13:34:33 I think beagles is right, we need to provide other tool ro set it 13:34:45 baoli: agreed 13:35:11 but there might be better way to facilitate the user to configure it. 13:35:30 irenab: this would be aperfect topic to nail down at the summit 13:36:35 sadsu7: agree, I think we need to have some proposals to discuss it. Hopefuly beagles' mail will raise ideas 13:37:10 ok 13:37:11 look forward to it. 13:38:28 should we involve any oslo folks in the discussion for ideas? 13:38:58 baoli: do you want to go over new bugs? 13:39:27 irenab, we can look at the first bug on the list 13:41:03 any thoughts? It's actually already found long back and there are existing patches. 13:42:11 It's kind of critical for restart 13:42:39 baoli: seems there is afix lready submitted 13:42:56 https://review.openstack.org/#/c/131321/ 13:44:14 missed that earlier. 13:45:17 I'll try to verify the fix 13:45:31 well, that won't fix the fundamental issue. 13:45:48 baoli: can you please summarize the initial issue 13:46:37 fix seems simple..but there is no explation of the root cause of the problem 13:46:57 irenab, during restart, the compute node needs to reconcile with the DB in terms of the PCI device records. 13:47:23 That's not done properly. 13:48:17 https://review.openstack.org/#/c/82206/ https://review.openstack.org/#/c/102298/ attempted to fix that. 13:48:55 baoli: do you mean DB should be in sync with node current PCI devices? 13:49:44 irenab, nova-compute needs to sync up with the DB during its restart 13:51:04 baoli: to reflect current compute devices and update device availability state? 13:51:24 irenab, that's right. 13:51:44 in restart case, all the VMs keep running on the node (unless the node itself gets restarted) 13:52:03 baoli: but this is not the case of this bug, right? 13:52:20 irenab, it is. 13:52:21 if node restarts, devices may be changed 13:53:05 by the way, what happens in case the white list is changed and then nova is restarted 13:53:15 irenab, I wouldn't think admin would remove, but may add new. Most use case would be to upgrade 13:53:35 sorry, wouldn't remove any existing 13:54:41 so actually the case to fix, is nova restart with same or extended white list settings while there are running VMs with allocated PCI devices 13:54:49 irenab: the new whitelist should be used for VMs that are freshly brought up after the whitelist change 13:55:01 existing VMs should continue as is 13:55:23 irenab, currently even without any change, it's not working as designed, or the code has never worked for the restart case. 13:55:33 without any change of WL 13:55:35 sadsu: yes, I was afraid of the case, where white list maybe changed in the way that it won't contain allocated devices 13:55:36 baoli: the 2 review links you posted are changing the same files 13:55:48 are they 2 diff fixes that you are proposing? 13:56:36 baoli: do you know if Heyongli fixing this issue? 13:56:37 irenab: agreed..I knew that you were referring to that case...but too bad we can't change what is already allocated correct? 13:56:51 sadasu, kind of. 13:57:22 irenab, I need to take a close look at it. 13:57:58 But my first impression is that it doesn't address the issue completely 13:58:09 baoli: it is really good idea to track this issues at group wiki page 13:58:45 irenab, agreed. 13:59:19 it's listed as the top bug. 13:59:31 I'll try to take a look at this issue as well 13:59:57 irenab, great 14:00:15 I think that the time is up, we can continue at the summit 14:00:22 See you guys at the summit. 14:00:30 guys and girls, see you in Paris 14:00:59 #endmeeting