13:03:38 #startmeeting powervm_driver_meeting 13:03:39 Meeting started Tue Mar 14 13:03:38 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:40 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:03:42 The meeting name has been set to 'powervm_driver_meeting' 13:06:09 #topic In Tree Driver 13:06:33 Getting feedback, working through comments. 13:06:45 mriedem is... thorough. 13:07:11 Some stuff is easily addressed. Some stuff may not have a good answer, and may take a nontrivial amount of back and forth before it can be resolved satisfactorily. 13:07:24 But - working on it. 13:08:20 Once I've put up another rev on that first change, I'll need to rebase the whole pile again. At least one comment is going to need to be applied manually to all the change sets. 13:08:52 After all of that, I'm not sure it's terribly productive for me to keep piling change sets on top until we've started to get some serious traction. 13:09:19 Okay. I was just about to say I need to rebase from #2, but sounds like I will hold off 13:09:28 Yeah, I'll take care of that. 13:09:44 That's all I have for in-tree. 13:10:13 #topic OOT driver 13:10:28 efried: is there anything breaking that we can't/wouldn't want to apply from the comments from your perspective? I didn't notice anything breaking, though he's right about the VIOS startup pause 13:10:55 adreznec Breaking how? 13:11:44 efried: Things that would be painfully heavy to maintain differently between IT and OOT, for example 13:11:56 I don't have a problem with the other 80% of his comments. The copyright thing took some churn, but I've got a lengthy response for which the TLDR is that I'm gonna whack the "All Rights Reserved" throughout (which is the thing I need to carry forward into the other change sets). 13:12:03 Or cause major functional changes in how the driver behaves for people switching from OOT to IT down the road 13:12:13 But yeah, the Session timeout is going to be painful to resolve. 13:12:33 But as far as maintaining sync between IT/OOT, nothing's a real big deal. 13:12:44 Mostly worried about maintainability and consistency for eventual end users of the IT driver 13:13:04 Ok 13:13:05 Functionally I don't think there's anything that's going to change 13:13:17 (depending on the outcome of the Session timeout discussion) 13:13:32 But most of the things I'm changing IT, I'm proposing corresponding backports to OOT. 13:13:37 where appropriate. 13:13:42 Especially when they're improvements. 13:14:07 Okay, back to OOT? 13:14:13 esberglu Would changing our setuptools req in networking-powervm's requirements.txt allow us to pass CI in ocata? 13:14:40 We've got a consumer waiting for a fix that's not merging because of that snafu. 13:14:58 Depends. Let me check if the tempest change merged yet one sec 13:15:06 It didn't 13:15:10 at least as of 10 minutes ago. 13:15:51 Then no 13:16:07 bogus. 13:16:10 I believe you need both 13:16:31 How hard would it be for us to pull down that change set from gerrit when we clone tempest? 13:17:30 Not that hard, it would just take a CI redeploy. And then another redeploy once it merges 13:17:43 Or reusing that logic to not apply patches already in the commit chain 13:18:14 I thought these would merge faster... 13:18:24 "CI redeploy" sounds annoying. 13:18:56 Just the management nodes, but yeah it's annoying that's why the initial plan was to just wait it out 13:19:00 svenkat How urgently do you need https://review.openstack.org/443956 ? 13:19:17 efried checking... 13:19:48 it can wait.. not very urgent. 13:20:05 Okay. So esberglu let's just sit on it. 13:20:41 Okay. Apparently they don't want to restrict setuptools to <34.0.0 so we might keep hitting this issue 13:20:46 on new versions of setuptools 13:21:04 Guess we'll burn that bridge when we come to it. 13:21:06 Until setuptools fixes the issue on their end 13:21:15 esberglu: Are other people not impacted by this? Or have they worked around it some other way in other CIs? 13:22:07 Not sure, didn't really look further into it once we had a fix lined up 13:22:25 You would think there would be more chatter if others were affected. 13:22:39 which leads one to wonder whether there's an easy workaround we're missing. 13:22:48 Right 13:22:56 esberglu Maybe ask in #openstack-qa ? 13:23:25 and/or try to find a launchpad bug? 13:24:12 Will do 13:24:16 oh, which reminds me (sorry to be jumping topics) - I think we should backport the VTerm 404 fix to ocata. 13:24:28 I can do that 13:24:39 #action esberglu: Port vterm 404 to ocata 13:24:44 This entails opening a launchpad bug and including it in the Closes-Bug: tag on the cherry-pick. 13:25:03 #action esberglu: Follow through on setuptools issue 13:25:15 Ok 13:25:44 I assume you know how to do all of that; let me know if you need help. 13:25:58 Anything else OOT? I don't have anything 13:26:14 Don't think so. 13:26:22 #topic CI 13:26:29 tjakobs is looking at starting on iSER support, but that's really it 13:26:38 what's iSER? 13:26:47 iSCSI extensions for RDMA 13:26:56 Basically faster/better performing iSCSI 13:27:12 Should be relatively small extensions to the existing rest/pypowervm/nova-powervm iSCSI flow 13:27:12 Wow, that's some serious nested acronymage. 13:30:40 Anything else? 13:30:41 Anyway, that's all I had there. Back to CI, the land of rainbows and unicorns 13:31:03 Merged that glance api tempest change 13:31:14 good 13:31:18 So we should be back to seeing passing master OOT and IT 13:31:57 That's it for me 13:34:54 Any other topics? 13:36:07 Anything Drew would normally be doing that we're missing? 13:37:04 Hah 13:37:22 Drew would be doing like presentations to execs and stuff. 13:37:24 Nope, ok, guess Drew wasn't doing anything 13:37:25 :P 13:37:30 He doesn't do *real* work anymore. 13:38:22 Poor guy 13:38:28 ikr 13:39:15 wedone? 13:39:23 callit 13:39:30 Looks like it 13:39:32 #endmeeting