14:00:03 <edmondsw> #startmeeting PowerVM Driver Meeting
14:00:04 <openstack> Meeting started Tue Jul 10 14:00:03 2018 UTC and is due to finish in 60 minutes.  The chair is edmondsw. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:07 <openstack> The meeting name has been set to 'powervm_driver_meeting'
14:00:24 <edmondsw> ping efried gman-tx mdrabe mujahidali chhagarw
14:00:31 <efried> ō/
14:00:41 <edmondsw> #link https://etherpad.openstack.org/p/powervm_driver_meeting_agenda
14:00:48 <edmondsw> #topic In-Tree Driver
14:00:57 <edmondsw> #link https://etherpad.openstack.org/p/powervm-in-tree-todos
14:01:25 <edmondsw> other than https://review.openstack.org/#/c/578840/ I'm not sure we've done much in-tree since the last meeting
14:01:52 <chhagarw> for the vscsi changes do we need to open a separate bug and incorporate changes ?
14:02:19 <edmondsw> chhagarw you mean in nova-powervm?
14:02:47 <edmondsw> I guess anything we change for vSCSI OOT should probably be changed IT as well now that we've ported that IT
14:03:06 <edmondsw> chhagarw what change are you talking about?
14:03:25 <chhagarw> yes, I am talking about the LPM changes to save the BDM connection info issue
14:03:57 <edmondsw> yes, that should be a separate bug/commit
14:04:24 <edmondsw> I would start in nova-powervm and then once we've agreed there we can use the same bug but a different commit in nova
14:04:57 <chhagarw> sure
14:05:00 <edmondsw> to port the change into the IT driver
14:05:16 <edmondsw> #topic Out-of-Tree Driver
14:05:24 <edmondsw> https://etherpad.openstack.org/p/powervm-oot-todos
14:05:27 <edmondsw> #link https://etherpad.openstack.org/p/powervm-oot-todos
14:06:06 <edmondsw> chhagarw has addressed my comments on https://review.openstack.org/#/c/576034/ and gman-tx +2ed as well, so that is close to merging
14:06:32 <edmondsw> except the CI is broken, so we are waiting for that to get fixed and make sure this passes CI
14:06:45 <edmondsw> chhagarw you have tested these changes in devstack, correct?
14:07:08 <edmondsw> including the most recent edits?
14:08:02 <edmondsw> chhagarw please add a comment to the commit when you've finished testing with devstack
14:08:12 <edmondsw> I'll wait to remove -W for that as well as for CI
14:08:15 <chhagarw> the last change of removing the discover needs to tested on devstack i can check that and update
14:08:21 <edmondsw> tx
14:08:56 <edmondsw> in other news, I have moved nova-powervm to stestr like nova: https://review.openstack.org/#/c/579292/
14:09:23 <edmondsw> and we bumped pypowervm requirement to 1.1.16 and merged the support for rbd user
14:09:56 <edmondsw> also fixed some requirements and constraints issues: https://review.openstack.org/#/c/579701/
14:10:53 <edmondsw> I haven't proposed stestr changes for networking-powervm or ceilometer-powervm yet
14:10:58 <edmondsw> will get to that eventually
14:11:16 <edmondsw> have done a few other cleanups in networking-powervm
14:11:43 <edmondsw> mdrabe any update on the MSP support?
14:13:03 <edmondsw> oh, we also merged the changes esberglu had proposed porting IT changes back to OOT
14:13:15 <edmondsw> which closes out what he was on the hook for
14:14:40 <edmondsw> efried chhagarw gman-tx I happened to notice that extend_disk has not been implemented for the ssp disk driver, and I think that is going to blow up if you try to extend disk during resize
14:15:01 <efried> IT or OOT?
14:15:15 <edmondsw> probably both, but I noticed OOT I believe
14:15:25 <edmondsw> we need to confirm and get a bug opened
14:15:40 <edmondsw> I threw it on the TODO list so I didn't forget, but I don't have a devstack env setup atm to confirm it
14:16:09 <edmondsw> if one of you starts working on that, let me know, else I'll try to get to it
14:16:40 <efried> I thought we implemented extend
14:16:45 <efried> or at least looked into it.
14:17:01 <edmondsw> efried you're probably thinking about our volume drivers
14:17:01 <efried> IIRC, if you try to resize the disk, it actually replaces it with a new one (so your data goes away)
14:17:20 <efried> As a result of which I believe we blocked it and/or left it to blow up if you tried to extend it.
14:17:24 <efried> I.e. the current behavior is correct.
14:17:31 <edmondsw> we implement extend_disk for the localdisk driver
14:17:33 <efried> Unless we want to blow it up earlier or more gracefully or something.
14:17:43 <efried> Yeah, cause you can extend an LV.  But you can't extend an LU.
14:17:55 <efried> again, if memory serves.
14:18:26 <edmondsw> could be right... maybe thorst will remember?
14:18:40 <edmondsw> I'll check with him
14:18:57 <edmondsw> tx, this is why I brought it up
14:19:09 <edmondsw> I don't have anything else for OOT, so...
14:19:15 <edmondsw> #topic Device Passthrough
14:19:17 <edmondsw> efried ^
14:19:50 <efried> #link Spec up for review: https://review.openstack.org/579359
14:20:12 <efried> #link Initial change set with yaml schema & parsing: https://review.openstack.org/579289
14:20:41 <efried> In Nova-land, the nrp microversion finally merged last week \o/
14:21:11 <efried> Folks are starting to work on functional tests to demonstrate how/whether things are broken on the resource tracker side.
14:21:32 <efried> We will need to follow those and work through them before we'll be able to get our stuff working in nova-powervm.
14:21:44 <efried> I don't have a sense yet of how big that will be.
14:21:59 <efried> but definitely not zero.
14:22:07 <efried> Any questions?
14:22:25 <edmondsw> not atm... still need to review those things you linked
14:22:55 <efried> Would like mdrabe to look as well, please.
14:23:28 <efried> edmondsw: Who else do we have to help review/shepherd the nova-powervm code for this effort?
14:23:28 <edmondsw> #topic PowerVM CI
14:23:52 <edmondsw> efried sorry, thought you were done... not sure there is anyone else atm
14:24:04 <edmondsw> other than of course jwcroppe
14:24:21 <efried> okay, then we definitely need to make sure mdrabe is on the hook.
14:24:28 <edmondsw> agreed
14:24:32 <edmondsw> #link https://etherpad.openstack.org/p/powervm_ci_todos
14:24:48 <edmondsw> mujahidali any more luck getting the CI working?
14:24:59 <mujahidali> I have redeployed the CI, it should be back within 2 hour if there are no hurdles.
14:25:10 <edmondsw> ok thanks
14:25:24 <mujahidali> The vscsi for stable/oacata still not stacking.
14:25:24 <mujahidali> I have tried the absolute path as well, suggested by edmondsw: It's failing on the same error "opt/stack/devstack/lib/neutron:420 neutron-api did not start "
14:25:28 <edmondsw> if you're still around when it's back, please ping us and let us know
14:25:36 <mujahidali> sure
14:26:13 <edmondsw> new logs with the abs path?
14:26:38 <mujahidali> logs are gone now
14:26:46 <edmondsw> k
14:27:01 <edmondsw> let's just put ocata on hold for now
14:27:09 <edmondsw> we have pike and queens working, right?
14:27:15 <mujahidali> yes
14:27:27 <edmondsw> so remove ocata from the commit so we can merge pike/queens support
14:27:40 <edmondsw> and create a new commit for ocata with your ocata changes
14:27:43 <edmondsw> so we don't lose them
14:27:51 <mujahidali> okay, will do it.
14:28:05 <edmondsw> but then table the ocata commit for now... we have more important things to work on
14:28:20 <edmondsw> table = put on hold
14:28:36 <edmondsw> how is the multinode CI work going?
14:28:48 <edmondsw> probably on hold while you figure out how to get the CI working at all?
14:28:52 <edmondsw> :)
14:29:10 <mujahidali> yeah, it's on hold for now.
14:30:31 <edmondsw> alright, I assume that's it for CI then
14:30:37 <edmondsw> #topic Open Discussion
14:30:44 <edmondsw> anyone?
14:32:18 <edmondsw> #endmeeting