Tuesday, 2017-10-17

*** edmondsw has joined #openstack-powervm00:13
*** edmondsw has quit IRC00:18
*** esberglu has joined #openstack-powervm00:30
*** esberglu has quit IRC00:45
*** AlexeyAbashkin has joined #openstack-powervm00:48
*** AlexeyAbashkin has quit IRC00:52
*** edmondsw has joined #openstack-powervm01:00
*** jwcroppe has quit IRC01:08
*** jwcroppe has joined #openstack-powervm01:11
*** AlexeyAbashkin has joined #openstack-powervm01:28
*** AlexeyAbashkin has quit IRC01:32
*** tjakobs_ has joined #openstack-powervm02:19
*** AlexeyAbashkin has joined #openstack-powervm02:27
*** AlexeyAbashkin has quit IRC02:31
*** tonyb has quit IRC02:36
*** tonyb has joined #openstack-powervm02:37
*** tjakobs_ has quit IRC03:02
*** AlexeyAbashkin has joined #openstack-powervm03:26
*** tjakobs_ has joined #openstack-powervm03:28
*** AlexeyAbashkin has quit IRC03:31
*** AlexeyAbashkin has joined #openstack-powervm04:26
*** AlexeyAbashkin has quit IRC04:31
*** jwcroppe has quit IRC04:35
*** esberglu has joined #openstack-powervm05:09
*** esberglu has quit IRC05:09
*** edmondsw has quit IRC05:17
*** tjakobs_ has quit IRC05:29
*** jwcroppe has joined #openstack-powervm05:55
*** jwcroppe has quit IRC05:59
*** edmondsw has joined #openstack-powervm07:01
*** edmondsw has quit IRC07:06
*** AlexeyAbashkin has joined #openstack-powervm07:34
*** edmondsw has joined #openstack-powervm08:50
*** edmondsw has quit IRC08:54
*** esberglu has joined #openstack-powervm09:04
*** esberglu has quit IRC09:09
*** esberglu has joined #openstack-powervm09:59
*** esberglu has quit IRC09:59
*** openstackgerrit has quit IRC10:33
*** edmondsw has joined #openstack-powervm10:38
*** edmondsw has quit IRC10:42
*** esberglu has joined #openstack-powervm10:52
*** esberglu has quit IRC10:57
*** edmondsw has joined #openstack-powervm12:09
*** esberglu has joined #openstack-powervm12:52
esberglu#startmeeting powervm_driver_meeting13:00
openstackMeeting started Tue Oct 17 13:00:45 2017 UTC and is due to finish in 60 minutes.  The chair is esberglu. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: powervm_driver_meeting)"13:00
openstackThe meeting name has been set to 'powervm_driver_meeting'13:00
esberglu#topic In-Tree Driver13:01
*** openstack changes topic to "In-Tree Driver (Meeting topic: powervm_driver_meeting)"13:01
esbergluNot much motion here in the last week13:01
esbergluConfig drive still up for review13:01
esbergluI spent some time at the end of last week trying to get and OVS devstack run to work13:02
esbergluStill working on that13:02
edmondswhow's that going?13:02
esbergluThat's about it for me IT13:02
edmondswstuck, or making progress?13:02
esbergluedmondsw: I got an OOT stack working with OVS, but haven't tried the equivalent IT yet13:02
edmondswk, cool13:03
esbergluFigured I should be able to base most of it on that13:03
edmondswI keep getting distracted when I go to review the config drive patch13:03
edmondswefried once I review that, you think we can start asking for reviews in the community, or.. ?13:04
edmondswshould we have thorst review first?13:04
efriedNah, we should be able to ask sdague13:04
edmondswk, I'll try to look at that today13:05
esbergluedmondsw: sweet13:05
edmondsw#action edmondsw to review IT config drive patch13:05
edmondswthat's probably all for IT then13:05
esberglu#topic Out-of-Tree Driver13:05
*** openstack changes topic to "Out-of-Tree Driver (Meeting topic: powervm_driver_meeting)"13:06
esbergluI spent a little time yesterday afternoon working on porting the host cpu stats to pypowervm13:06
esbergluGot the UT working, but the 1st try is failing sonar13:06
esbergluedmondsw: You said we need that by next week?13:07
edmondswsounds like a good start, though. Can't ever expect sonar to work first time ;)13:07
edmondswlet's try to finish it this week if we can13:07
esbergluedmondsw: Yep I'll finish it this week to leave time for reviews13:08
edmondswmdrabe efried should we talk about the DefaultStandardize change?13:09
efriedmdrabe not here?13:09
edmondswmdrabe you here?13:09
edmondswoh nope...13:09
efriedI can summarize the issue, if you like.13:09
efriedThe way lpar_builder is set up, it can't actually tell if it's creating a new LPAR or updating an existing one.13:10
edmondswI've been following along, just wanted to discuss next steps13:10
efriedSo if you use DefaultStandardize, you'll always blat the values in its init with the defaults.13:10
efriedIncluding max_io_slots13:10
efriedSo this change set is detecting when we have an existing LPAR and overwriting the DefaultStandardize values with the existing values from the wrapper.  Which is stupid.  But is actually the least evil AFAICT.13:11
edmondswwhat I didn't quite follow was why there were two values we have to pick between which to keep...13:11
edmondswone from the wrapper, and another from slot_mgr13:12
edmondswcan you explain that?13:12
edmondswI think you guys agreed to always keep whichever of the 2 was higher13:13
*** thorst has joined #openstack-powervm13:14
efriedIt's possibly because this was a problem before, but we were in such a rush to implement the damned slot manager stuff, we just went with the first solution we came up with.13:14
edmondswhow could the slot_mgr have a value that's more correct about the current state of the VM than the lpar wrapper?13:15
efriedI believe the slot manager figures out the highest slot being used by the source.13:15
efriedOh, because if the original LPAR was created with a non-default slot limit - which would have been possible before I introduced that bug - then you could have wound up using a slot higher than the default max (64).13:16
efriedThen when you went to rebuild, it would rebuild the new LPAR with the default (64) and try to put a mapping on the >64 slot - kaboom.13:16
efriedOh, yeah, so it's not actually a horrible patchup solution.  Because on a RR, we're creating the target LPAR afresh.13:17
edmondswok, so it's all about that issue with 1.1.713:17
efriedSo anyway, on a RR, we want to use whatever the slot manager said (which in fact is probably whatever was on the source LPAR, not just arbitrarily the highest); but on a resize we want to use whatever the original LPAR had.13:18
efriedNo, not entirely.13:18
efriedThe resize issue was still a bug, even before 1.1.713:18
edmondswoh, true13:18
efriedTry to resize an LPAR that started off with a nonstandard max_io_slots (or in fact any of those other fields DefaultStandardize defaults), and you'll end up with the defaults in those fields.13:18
efriedI'm actually not completely sure there'll ever *be* a scenario where we'll have *both* a source LPAR and a slot manager.13:19
efriedSo in fact the "choose the highest" thing might be moot.  For now.  But better to do it and have it be a no-op than to have to track down THAT bug later on.13:20
edmondswit sounded like you said instead of "choose highest" you're now thinking we should choose one or the other based on resize vs. RR13:21
efriedNo, actually.13:21
efriedIf both of those things are in play for some reason, we should choose the highest.13:21
edmondswI think that makes sense13:22
edmondswwill want some nice comments about that in the code13:22
edmondswexplaining why13:22
efriedCause there's some semantic like "cold migrate resize" in play.13:22
efriedor maybe it's "live resize with migration"13:23
efriedSaw a bp go by about that.13:23
edmondswok, probably enough time on that13:23
edmondswtx for the explanation13:23
edmondswthe only other thing I know of going on OOT is the iscsi work13:23
efriedyuh, moving on.13:23
edmondswwe've been making progress there13:23
edmondswtjakobs has been working to address comments13:24
edmondswthat's probably all for OOT13:24
esberglu#topic Device Passthrough13:24
*** openstack changes topic to "Device Passthrough (Meeting topic: powervm_driver_meeting)"13:24
edmondswefried you're up13:25
efriedStill waiting for jwcroppe to come back on requirements.13:25
efriedI started trying to stack that new system, as time has allowed.13:26
efriedHaven't succeeded yet, I don't think.13:26
efriedBut otherwise, nothing to report on the pre-Queens-hackup version.13:26
efriedThe Queens stuff is going fairly well, though.  It's possible we could be able to do everything we need with generic RPs on a Queens base.13:27
edmondswefried I didn't realize you were still waiting for input from jwcroppe. Are you sure he knows that?13:27
efriedYou guys were gonna review my spec on granular resource request syntax, remember?13:27
edmondswthat's good news about queens13:27
edmondswyeah, I remember...13:27
esbergluefried: I will today13:27
edmondsw#action edmondsw and esberglu to review https://review.openstack.org/#/c/510244/13:28
efriedNote that spec freeze is Thursday, so don't -1 me for typos.13:28
efriedjust for substantive stuff.13:28
esbergluYep Queens-1 thursday, forgot to say that during the drivers bit thanks13:29
esbergluefried: Anything else before we move on?13:30
efriedJay is on vacation13:30
edmondswJay is changing companies13:30
efriedAnd I volunteered to babysit his NRP seres while he's gone.13:30
edmondswalright... CI?13:32
esberglu#topic PowerVM CI13:32
*** openstack changes topic to "PowerVM CI (Meeting topic: powervm_driver_meeting)"13:32
esbergluNeed to check with nvcastet today on that bug we've been seeing in CI13:32
edmondswhsien should also be back now13:32
esbergluOther than that mostly just backlog items as able, nothing too exciting13:33
esberglu#topic Open Discussion13:34
*** openstack changes topic to "Open Discussion (Meeting topic: powervm_driver_meeting)"13:34
edmondswnothing more from me13:34
*** openstack changes topic to "This channel is for PowerVM-related development and discussion. For general OpenStack support, please use #openstack."13:35
openstackMeeting ended Tue Oct 17 13:35:55 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2017/powervm_driver_meeting.2017-10-17-13.00.html13:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2017/powervm_driver_meeting.2017-10-17-13.00.txt13:36
openstackLog:            http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2017/powervm_driver_meeting.2017-10-17-13.00.log.html13:36
*** esberglu has quit IRC13:54
*** esberglu has joined #openstack-powervm13:54
*** esberglu has quit IRC13:59
*** jwcroppe has joined #openstack-powervm14:06
*** esberglu has joined #openstack-powervm14:09
*** tjakobs_ has joined #openstack-powervm14:15
*** openstackgerrit has joined #openstack-powervm14:41
openstackgerritEric Berglund proposed openstack/nova-powervm master: DNM: ci check  https://review.openstack.org/32831514:41
*** AlexeyAbashkin has quit IRC15:30
*** AlexeyAbashkin has joined #openstack-powervm15:30
*** AlexeyAbashkin has quit IRC15:41
*** jwcroppe_ has joined #openstack-powervm15:47
*** jwcroppe has quit IRC15:49
*** jwcroppe_ has quit IRC17:13
*** AlexeyAbashkin has joined #openstack-powervm17:22
*** AlexeyAbashkin has quit IRC17:24
*** cjvolzka has joined #openstack-powervm19:06
*** jwcroppe has joined #openstack-powervm19:21
*** AlexeyAbashkin has joined #openstack-powervm19:40
*** AlexeyAbashkin has quit IRC19:44
*** jwcroppe has quit IRC19:45
*** jwcroppe has joined #openstack-powervm20:02
efriedesberglu edmondsw Some jackass is making a breaking change to the spawn method signature.  We'll need to update our OOT driver accordingly.20:07
efriedEither one of y'all want to take that on, or want me to do it?20:08
edmondswefried if you have the time... I'm neck deep20:08
efriedOkay.  I'm pretty familiar with the change, so I guess I can do it.  FYI: https://review.openstack.org/51187920:09
efriedesberglu If we want CI results before ^ merges, we'll have to patch it in somehow.  Depends-On doesn't work for us from OOT, does it?20:10
edmondswI don't think so20:10
esbergluefried: No it doesn't. I can do a manual run20:13
efriedesberglu ight, stand by.20:13
openstackgerritEric Fried proposed openstack/nova-powervm master: Add allocations to spawn signature  https://review.openstack.org/51281420:19
efriedesberglu ^ + https://review.openstack.org/51187920:19
esbergluefried: ack20:19
efriedesberglu Somehow our OOT CI passed at PS5 of the above.  Can't imagine how.20:21
efriedoh, we're not running OOT CI on nova changes??20:21
efriedesberglu wait, I'm confused.20:21
esbergluefried: I know what happened20:21
efriedokay.  FYI, I've also seen this pop up more than once:
*** AlexeyAbashkin has joined #openstack-powervm20:22
efriedesberglu Let me know when I can powervm:recheck the nova change.20:23
efriedesberglu Oh, by the way, if we want to patch in https://review.openstack.org/#/c/493654/ (Glance) and https://review.openstack.org/492651 (devstack) we can start using uwsgi20:24
efriedI tested it locally and it seems to work fine.20:25
esbergluefried: We skip OOT CI on nova changes with powervm in any of the filepaths20:25
efriedesberglu Ahhhhh.  Well, in this case, that's wrong :)20:25
efriedOr... maybe not, actually.  Cause this will in fact break OOT.20:25
efriedOkay, I'll recheck to get the in-tree one validated.20:26
efriedesberglu Unless there's some know permanent issue with that multiple-networks thing20:26
esbergluefried: Nah that's an issue that hits the IT driver very infrequently20:27
*** AlexeyAbashkin has quit IRC20:27
efriedight, rechecking.20:27
esbergluefried: Do you remember why we were skipping OOT CI on IT patches with powervm in them?20:35
*** jwcroppe has quit IRC20:35
esbergluI'm struggling to recall and the commit message wasn't very helpful20:35
efriedProbably because we assumed they were going to be adds to the in-tree driver, and therefore the OOT driver would override them anyway and be redundant, so we probably did it to save CI resources.20:36
efriedesberglu If we're not worried about CI resources, it's probably not a terrible idea to take that condition away.20:37
esbergluefried: It will make the CI jobs SO much more readable to get rid of that condition20:37
esbergluAnd it shouldn't affect overall run numbers really20:38
efriedesberglu Is there some kind of condition going the other way too?  Like, we skip the IT runs for all OOT patches, or something?20:38
esbergluefried: Nope20:38
efriedHm.  Then there was probably a much better reason we were skipping OOT runs on powervm-containing IT patches.20:39
efriedBut I can't remember what it would have been.20:39
openstackgerritMerged openstack/nova-powervm master: Support PPT ratio capable to PPT ratio incapable host rebuild  https://review.openstack.org/50823620:39
*** edmondsw has quit IRC21:16
*** edmondsw_ has joined #openstack-powervm21:18
openstackgerritEric Berglund proposed openstack/nova-powervm master: WIP: Move host cpu stats to pypowervm  https://review.openstack.org/51286421:19
*** edmondsw_ has quit IRC21:22
*** thorst has quit IRC21:25
*** thorst has joined #openstack-powervm21:25
*** thorst has quit IRC21:30
*** thorst has joined #openstack-powervm21:50
*** edmondsw has joined #openstack-powervm21:51
*** thorst has quit IRC21:54
*** edmondsw has quit IRC21:55
*** esberglu has quit IRC21:55
*** esberglu has joined #openstack-powervm21:56
*** esberglu has quit IRC22:00
*** tjakobs_ has quit IRC22:12
*** esberglu has joined #openstack-powervm23:31

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