Tuesday, 2018-04-17

*** esberglu has quit IRC01:16
*** prashkre_ has joined #openstack-powervm03:46
*** prashkre has quit IRC03:47
*** prashkre__ has joined #openstack-powervm04:13
*** prashkre_ has quit IRC04:16
*** prashkre__ has quit IRC04:51
*** prashkre has joined #openstack-powervm06:11
*** AlexeyAbashkin has joined #openstack-powervm07:31
*** edmondsw has joined #openstack-powervm08:58
*** edmondsw has quit IRC09:02
openstackgerritprashkre proposed openstack/nova-powervm master: Miscellaneous iSCSI improvements  https://review.openstack.org/56102210:21
*** AlexeyAbashkin has quit IRC11:07
*** AlexeyAbashkin has joined #openstack-powervm11:28
openstackgerritprashkre proposed openstack/nova-powervm master: Handle exceptions properly with iscsi discovery  https://review.openstack.org/56191411:40
openstackgerritprashkre proposed openstack/nova-powervm master: Handle exceptions properly with iscsi discovery  https://review.openstack.org/56191411:47
*** edmondsw has joined #openstack-powervm12:37
*** apearson has joined #openstack-powervm12:40
prashkreedmondsw: efried: Good morning.13:01
efriedHello prashkre13:01
efriedI was looking at your patches (got waylaid, but I'm on it)13:02
edmondswprashkre hi... will look13:02
prashkreFYI.. we have now 3 patches https://review.openstack.org/#/c/561022/, https://review.openstack.org/#/c/557800/, https://review.openstack.org/#/c/561914/13:03
*** tjakobs has joined #openstack-powervm13:30
*** esberglu has joined #openstack-powervm13:36
openstackgerritMerged openstack/nova-powervm master: Handle exceptions properly with iscsi discovery  https://review.openstack.org/56191413:42
openstackgerritEric Berglund proposed openstack/nova-powervm master: DNM: CI Check2  https://review.openstack.org/32831713:45
edmondsw#startmeeting PowerVM Driver Meeting14:02
openstackMeeting started Tue Apr 17 14:02:24 2018 UTC and is due to finish in 60 minutes.  The chair is edmondsw. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: PowerVM Driver Meeting)"14:02
openstackThe meeting name has been set to 'powervm_driver_meeting'14:02
edmondsw#link https://etherpad.openstack.org/p/powervm_driver_meeting_agenda14:02
edmondswefried esberglu ut?14:03
edmondsw#topic In-Tree Driver14:03
*** openstack changes topic to "In-Tree Driver (Meeting topic: PowerVM Driver Meeting)"14:03
edmondsw#link https://etherpad.openstack.org/p/powervm-in-tree-todos14:03
edmondswI understand we're in a runway now14:04
edmondswexcited to see how that goes14:04
esbergluEverything through localdisk is +1 from edmondsw, +2 from efried, and in the runway14:04
edmondswany comments yet?14:04
efried(just checked)14:05
esbergluNope. Target date for that is 4/30 so I'm expecting them to start coming in soon14:05
edmondswanything else to note here then?14:05
efriedWe've been doing runways for all of two weeks, but tbh I haven't really noticed it prompting a significant increase in reviewer focus.14:05
efriedI'm thinking of suggesting a "champion" idea14:05
edmondswefried what would that be?14:06
esbergluI've been prioritizing multinode CI over finishing the cold mig/resize patch, nothing to report there14:06
edmondswesberglu that makes sense... CI is a prereq for that14:06
efriedwhere we assign one reviewer (core or not, I guess, but not the owner of the series) to go pester reviewers to look at the changes, and pester the owner to follow up as needed.14:06
efriedkinda like we champion invention disclosures on IDTs.14:07
edmondswwho pesters folks to be a champion? ;)14:07
efriedPart of the process; add it to runway, assign champion at that time.14:07
efriedjust an idea I'm toying with.14:07
edmondswyep, I think that can work14:08
edmondswcan become a nova meeting agenda item14:08
edmondsw#topic Out-of-Tree Driver14:08
*** openstack changes topic to "Out-of-Tree Driver (Meeting topic: PowerVM Driver Meeting)"14:08
edmondsw#link https://etherpad.openstack.org/p/powervm-oot-todos14:09
edmondswwe've made some progress on the iscsi changes14:09
edmondswI just merged one, which put the others into merge conflict since they're not in a series14:09
edmondswI told prashkre to rebase the other that I +2/+A'd and when he does that I'll fast approve it14:10
edmondswI did give him a comment to go address on the 3rd iscsi commit14:10
edmondswhe's off and running on that14:10
edmondswonce those all merge, I intend to tag 6.0.114:11
openstackgerritprashkre proposed openstack/nova-powervm master: Return iSCSI Initiator for VIOSes  https://review.openstack.org/55780014:11
*** AndyWojo has quit IRC14:11
edmondswI also just setup a meeting with the PowerVC storage guys to talk about community contribution for multiple initiator support, among other things14:11
edmondswanything else to discuss around iscsi?14:12
edmondswthe volume refactor will need to be rebased and updated once these changes merge14:12
edmondswand I still need to dig into the concerns that the PowerVC team raised on that14:13
edmondswso probably more updates there14:13
edmondswtjakobs FYI ^14:13
edmondswanything else for OOT?14:13
edmondswsome other things need to happen, like adding MSP support, but I haven't gotten to anything there14:14
efriedWe could have done the iscsi changes in a series and not had to rebase.14:14
edmondswefried I suggested that a couple times, but nobody did it, so...14:14
efriedNot sure how much more prashkre is going to be doing for us, but might be worth a little tutorial on that.14:14
edmondswefried I'd love to see something written up on that for some wiki somewhere14:15
edmondswand then just link it with things like that14:15
efriedI'm sure there are documents galore.14:15
edmondswI'm sure... question is where, and how good are they14:15
efriedThere's a whole man page for git restack14:15
efriedwhich is what I use *daily*14:15
edmondswif we find a good one, great, just need to keep in our back pocket and start linking14:16
edmondswmaybe just link that then14:16
edmondswI'm familiar with rebase, but not restack14:16
edmondswwhich is probably why I'm confused about managing series myself14:17
efriedesberglu said he tried restack and couldn't get the hang of it.14:18
efriedbut I love it.14:18
edmondswyou play with it enough to figure out the quirks, probably14:18
esbergluefried: I think it's because I didn't check out the latest patch. I would check out the latest in the series, git restack14:18
esbergluThen change anything I want to edit to edit14:18
esbergluAnd go from there?14:18
efriedyes, using git rebase --continue whenever you're ready to move to the next one up.14:19
esbergluOkay I see where I went wrong now, thanks14:19
efriedBut yeah, it's key to check out the top patch in the series.14:19
*** AndyWojo has joined #openstack-powervm14:19
edmondswtop = the first one that should merge?14:20
edmondswor is that bottom?14:20
esbergluTop = last one that should merge14:20
edmondswok, so if I want to change something 3 patches down...14:21
edmondswI check out the top, and then what?14:21
efriedgit restack14:22
efriedit puts you into an editor just like git rebase -i14:22
efriedYou change 'pick' to 'edit' for any patches in the series you want to change.14:22
efriedSave/quit.  You'll be shoved down the chain into the first 'edit' patch.14:22
efriedMake your changes, and run git rebase --continue.  It'll commit your changes and put you into the commit message editor.14:23
efriedSave/quit that guy and you'll be shunted to the next 'edit' patch...14:23
efried...unless there's a merge conflict with one in between14:23
efriedin which case regular merge conflict process14:23
edmondswso you don't need to 'git commit' at all, it does that for you with rebase --continue?14:23
efriedwhen done, git rebase --continue.14:23
efriedyes.  You can do the commit yourself if you like14:23
edmondswjust need to git add after you change something, and then rebase --continue?14:23
efriedeither way.14:23
edmondswcool, got it14:24
edmondswmoving on14:24
efriednote that it doesn't come in the box.14:24
efriedyou have to pip install git-restack14:24
efriedit's something the os infra folks wrote, I think.14:24
edmondswoh, good to now14:24
edmondsw#topic Device Passthrough14:24
*** openstack changes topic to "Device Passthrough (Meeting topic: PowerVM Driver Meeting)"14:24
edmondswefried what's the latest?14:24
efriedJay and I had a knock-down drag-out; now we're asking for an impartial referee to decide who wins.14:24
edmondswyou couldn't take him?14:25
efriedSo many possible responses to that.14:25
edmondswI was trying to set you up easy...14:25
efriedAt this point I would be content either way tbh.  We've wrangled both of our proposals into compromise territory.14:25
efriedI still have a preference for mine, but I won't be seriously mad if it goes the other way.14:26
efriedI made progress on the granular patch.14:26
efriedI've got the bugs worked out to where it has parity with the existing functionality14:27
efriedThat is, if you're not using granular syntax, all the old scenarios still work when they're funneled through the new algorithm.14:27
efriedI'll be in microversion rebase hell until it merges.14:27
efriedNext step will be to write tests; and once the above argument is settled, to fold in that functionality.14:27
efriedBecause it's looking likely that we're going to want to do it in the same microversion.14:28
efriedJay admonished me for not waiting until his NRP stuff was done14:28
efriedand then started working on it again14:28
efriedWhich was kind of the goal.14:28
efriedso goodness there.14:28
efriedSo progress is being made overall.  Otherwise, nothing new to report specifically on device passthrough as it pertains to PowerVM.14:28
efriedexcept I don't remember if I mentioned this14:29
efriedI wrote a couple of patches that use upt in libvirt to solve the age-old problem of sharing providers being double-reported.14:29
efriedI wouldn't have done it, except they took like 15 minutes and basically validated everything I wrote last cycle.14:30
efriedbhagyshris is going to take over the patches to fix up the tests and get everything ready to merge.14:30
edmondswI'm sure the KVM folks thank you14:30
efriedwe'll see :)14:30
efriedI think that's all I have for now.14:31
edmondswI'm more than happy to see things fixed for libvirt, since Power cares about that as well as PowerVM14:31
edmondswone thing I was going to mention14:32
edmondswI think we've said before that we need to consider infiniband and other types of passthrough as well as GPU14:32
edmondswRoCE is another14:33
edmondswand more than just passthrough, virtualization like (or using, I hope) SR-IOV14:33
efriedWe're getting set up for allll of that.14:34
edmondswexcept that I want to do it the right way, not the way we currently do SR-IOV14:34
edmondswso just throwing that out there... stay tuned14:34
edmondswyep yep14:34
edmondsw#topic PowerVM CI14:34
*** openstack changes topic to "PowerVM CI (Meeting topic: PowerVM Driver Meeting)"14:34
edmondsw#link https://etherpad.openstack.org/p/powervm_ci_todos14:34
edmondswesberglu ?14:34
esbergluI've got a change out for the powervm-ci side of multinode. Just adds local.conf files and updates prep_devstack.sh to work with AIO, control, and compute cases14:35
esbergluIt doesn't affect any existing jobs so I'm ready to merge if you guys are okay with it, will make neo-os-ci dev easier to have that in14:35
edmondswesberglu ack14:36
efriedWe gonna get Mujahid in here moving forward?14:36
*** apearson has quit IRC14:36
esbergluOn neo-os-ci I've got to the point where I can have the control node stack, then kick off another job to have the compute stack14:36
edmondswefried yeah, I'll ask him to join, though I expect we'll have more CI discussions in slack going forward14:37
esbergluStill not sure what I have to do to force them to be on the same host, but staging CI only has 1 compute node right now14:37
esbergluI want to bring neo4 back into staging, but I still have that set up for IT work, and might need it again there14:38
esbergluI may just steal a node from production for a little while14:38
edmondswesberglu have you asked the Power KVM CI guys if they've faced this problem?14:38
edmondswdo they do multinode in their CI?14:38
esbergluI don't think so, I can check14:38
*** apearson has joined #openstack-powervm14:39
esbergluThe big blocker for multinode is the jenkins dropping connections on the staging environment14:39
esbergluWhich I'm completely in the dark on, I spent a TON of time trying to figure this out when I was working the queens upgrade14:40
edmondswhave you asked for help from infra?14:40
edmondswit sounds like a possible jenkins issue14:40
esbergluYeah I guess that's the next step14:40
edmondswI know they're not hitting it, but they have experience tracking down these problems, right?14:40
esbergluedmondsw: Problem with that error message is that it could be a billion different things14:41
edmondswand it may very well be a jenkins bug they just haven't hit because of environment differences or something14:41
edmondswesbergly yep exactly14:41
esbergluBut I'll see if they can shed some light14:41
esbergluBut that is 100% blocking multinode CI right now and is my top priority14:41
esbergluNothing else from me14:42
edmondsw#topic Open Discussion14:42
*** openstack changes topic to "Open Discussion (Meeting topic: PowerVM Driver Meeting)"14:43
esbergluefried: You interested in being included in the PowerVM CI education sessions at all?14:43
efriedDoes it increase the probability that I will be called upon to work on the CI?14:43
efriedcause then no14:43
esbergluI'll leave you be :)14:44
edmondswI don't see that happening... but you might still want to be able to plead ignorance anyway :)14:44
edmondswbetter use of your time and all that14:44
edmondswalright, if nothing else...14:45
*** openstack changes topic to "This channel is for PowerVM-related development and discussion. For general OpenStack support, please use #openstack."14:45
openstackMeeting ended Tue Apr 17 14:45:05 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-04-17-14.02.html14:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-04-17-14.02.txt14:45
openstackLog:            http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2018/powervm_driver_meeting.2018-04-17-14.02.log.html14:45
edmondswesberglu how about you go ahead and cancel your meeting invite for this, and I'll send a replacement14:46
edmondsw(including mujahid)14:46
esbergluedmondsw: Done14:46
*** efried has quit IRC15:00
*** efried has joined #openstack-powervm15:01
*** apearson has quit IRC15:02
*** apearson has joined #openstack-powervm15:05
edmondswefried hold off on looking at 6470 just yet... I've got some stuff to discuss with esberglu there that will probably involve changes15:13
edmondswesberglu got some meetings coming up, so it'll be a bit before I can finish looking at that, but comments coming this afternoon15:13
prashkreedmondsw: we have CI +1 on https://review.openstack.org/#/c/557800/, please give your review on it so that for the other patch I can do rebase and do patching on top of them.15:16
edmondswesberglu one question you can maybe go ahead and answer... why is control.local.conf any different from the AIO local.conf besides the MULTI_HOST value?15:17
edmondswprashkre ack15:17
edmondswprashkre done15:18
edmondswesberglu do we even really need a separate conf file?15:19
esbergluedmondsw: Yeah you're right we probably don't15:20
edmondswesberglu ok, I dropped 2 comments for now and will try to look more later15:21
edmondswif you think you'll get a chance to rework that today, I'll wait for that15:22
esbergluedmondsw: Yeah you can hold off15:23
openstackgerritprashkre proposed openstack/nova-powervm stable/queens: Handle exceptions properly with iscsi discovery  https://review.openstack.org/56197615:33
openstackgerritMerged openstack/nova-powervm master: Return iSCSI Initiator for VIOSes  https://review.openstack.org/55780015:34
openstackgerritprashkre proposed openstack/nova-powervm master: Miscellaneous iSCSI improvements  https://review.openstack.org/56102215:49
prashkreedmondsw efried: logging off for a while, please review https://review.openstack.org/#/c/561022/ when you get time.16:03
edmondswprashkre ack16:04
efriedI sent that one already.16:04
*** prashkre has quit IRC16:05
*** prashkre has joined #openstack-powervm16:05
*** prashkre has quit IRC16:11
edmondswefried not 561022 you didn't16:11
efriednow I did16:14
openstackgerritMerged openstack/nova-powervm stable/queens: Handle exceptions properly with iscsi discovery  https://review.openstack.org/56197616:25
openstackgerritMerged openstack/nova-powervm master: Miscellaneous iSCSI improvements  https://review.openstack.org/56102216:46
edmondswesberglu you dropped off slack17:46
edmondswleft you a message about the multinode CI stuff17:47
*** AlexeyAbashkin has quit IRC18:02
openstackgerritEric Berglund proposed openstack/nova-powervm master: DNM: ci check  https://review.openstack.org/32831518:10
*** prashkre has joined #openstack-powervm18:11
edmondswefried I'm gonna tag 6.0.1 for nova-powervm unless you think there's anything more we would want to backport there first18:54
efriededmondsw: Nope, I'm good.18:58
edmondswesberglu openstack/releases only has a ceilometer-powervm deliverable for queens since nova-powervm and networking-powervm weren't under governance yet back then. So should I just use git tag?19:05
edmondswdo you have an example command for what you did to tag things before?19:05
esbergluMight be worth asking if you should create a deliverable for stable branches since we are under governance now? Not sure19:07
esbergluedmondsw: Otherwise it's on a wiki page, I'll send you the link19:08
esbergluedmondsw: Updated 6470 when you ave a chance19:14
openstackgerritEric Berglund proposed openstack/nova-powervm master: DNM: CI Check2  https://review.openstack.org/32831719:16
mdrabeefried: What logging levels would I need to see REST request / response? pypowervm=DEBUG?19:23
efriedmdrabe: TRACE19:24
efriedshit ton of data, that.19:24
efrieduse wisely.19:24
*** AlexeyAbashkin has joined #openstack-powervm19:25
*** AlexeyAbashkin has quit IRC19:34
*** apearson has quit IRC21:15
*** prashkre_ has joined #openstack-powervm21:19
*** prashkre has quit IRC21:19
*** edmondsw has quit IRC21:24
*** tjakobs has quit IRC21:35
*** esberglu has quit IRC21:51

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!