13:03:09 #startmeeting powervm_driver_meeting 13:03:10 Meeting started Tue Jul 18 13:03:09 2017 UTC and is due to finish in 60 minutes. The chair is esberglu. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:03:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:03:13 The meeting name has been set to 'powervm_driver_meeting' 13:03:16 o/ 13:03:38 \o 13:03:59 #topic In-tree Driver 13:04:24 Any new developments here? 13:04:47 nope 13:04:49 o/ 13:05:08 o/ 13:05:12 should be quiet on the IT driver for a bit with that blueprint done for pike 13:05:55 Yep. Just a reminder that next week is the pike 3 milestone (feature freeze) 13:06:09 Well, except for testing 13:06:34 #topic OOT driver 13:07:57 Anyone have discussion items OOT? 13:08:27 Couple g-r bumps proposed by the bot. 13:08:37 Been keeping an eye on our CI for those, haven't looked yet this morning. 13:08:38 Still waiting on an env to patch for the NVRAM event stuff 13:09:17 The g-r patches were getting blocked by those subnetpool tests. Just merged that 13:09:21 I'll kick off rechecks 13:09:24 k 13:11:13 esberglu Can you post the link to the agenda pls? 13:11:20 https://etherpad.openstack.org/p/powervm_driver_meeting_agenda 13:12:03 If people could start using that it would be really helpful. So I don't have to ask if there are any other topics every few minutes 13:12:18 :-) 13:12:26 #topic PowerVM CI 13:12:37 Still working on the devstack generated tempest.conf 13:12:59 Gonna update the local.conf files first and make sure they don't break stacking or anything else 13:13:08 Then propose any needed devstack/tempest changes 13:13:23 Then make the switch to the generated tempest.conf files 13:13:38 Otherwise just working through https://etherpad.openstack.org/p/powervm_ci_todos 13:14:17 #topic Driver Testing 13:14:29 Need discussion on PCI PassThru Investigation? 13:14:41 esberglu That's the next topic. 13:14:43 I would have done that under other business 13:14:58 What's the status of iSCSI, jay1_ chhavi ? 13:15:33 Yeah.. testing is inprogress 13:15:45 will update tonight 13:16:08 jay1_ nothing blocking you at the moment, though? 13:16:18 Yes edmondsw 13:16:22 I see the etherpad is still showing an issue on neo34... is that just old data? 13:16:34 https://etherpad.openstack.org/p/powervm-driver-test-status 13:16:49 Yeah.. in the evening only issue got resolved.. I will wipe out that issue info 13:16:53 tx 13:17:11 have you seen any evidence that the phyp guys are looking at neo32? 13:18:43 no, it is still in open state 13:19:03 At this point I've forgotten what the other thing was that we were wanting a pypowervm release for. Was it power-off? 13:19:18 jay1_ please prompt them... remind them you're holding the system for them and can't do that forever 13:19:37 Yeah, just added comment 13:19:39 efried I think so? been too long 13:19:49 back in a sec... 13:19:56 jay1_ might want to email the owner directly 13:20:02 jay1_: who are the PHYP guys? Not the NL guys, but actual PHYP? 13:20:10 yeah, phyp 13:20:12 wow 13:20:13 thorst^ 13:20:25 can I get subscribed to that defect? 13:20:36 thorst apparently we hit a bug they've never been able to track down, and it clears up when you restart the system, so we're leaving it for them to look at 13:20:56 did seroyer ask us to hold it for them? 13:21:15 thorst yes 13:21:24 jay1_ what was the phyp defect number again? 13:21:26 alright. Please subscribe me and I'll be a...jerk 13:21:34 just slack it to me 13:21:43 SW395662 13:21:53 thorst^ 13:22:27 on to PCI? 13:23:30 #topic PCI PassThru Investigation 13:23:57 efried I started looking at the reviews you added me to 13:24:09 that's just barely getting our feet wet, of course 13:24:43 tied up with some PowerVC stuff atm, trying to get through that so I can get to the PCI stuff in earnest, but probably won't be before next week 13:25:45 efried I think it's pretty much the same for you? 13:26:14 oh, he had to step away 13:26:45 I'm back - yeah, same. 13:26:46 I wasn't aware of those reviews, but I'll be looking through them shortly 13:27:08 as long as we can iterate what devices are there and attach them to a VM...I'm happy 13:27:11 My plan also includes trying to familiarize myself with the current code. 13:27:21 basic use case to start, then complexity later :-D 13:27:53 And then maybe try to get some time on jaypipes's calendar to talk through the vision as it relates to resource groups et al. 13:28:39 Because I think that whole architecture may be in flux 13:28:55 and we want to make sure that when it stabilizes, it does so in a way that's actually useful for us. 13:30:08 Just spitballin here, but... 13:30:58 agree with all of that 13:31:12 efried: probability of something for queens is low, medium or? 13:33:00 eh, doesn't need an answer 13:33:06 lets just do the reviews and do our best :) 13:33:17 yeah, too early to answer that I think 13:34:49 next topic/ 13:34:51 ? 13:35:10 #topic Open Discussion 13:35:11 #topic Open Discussion 13:35:24 thorst: You want to abandon 4707? 13:35:45 I'm gonna come back to that at some point, but I don't think that will be the final solution 13:36:16 esberglu is there anything on the TODO list for that? 13:36:21 s/list/etherpad/ 13:36:31 esberglu: done 13:36:44 edmondsw: I'll add it if not 13:36:51 tx 13:37:00 just a FYI that I'm still planning to do a VIF overhaul 13:37:03 probably there, just didn't ring a bell for me 13:37:43 thorst can you add that to https://etherpad.openstack.org/p/powervm-in-tree-todos 13:37:51 yep yep 13:39:17 Anything else before I call it? 13:40:18 call it 13:40:34 #endmeeting