Friday, 2017-09-01

*** edmondsw has quit IRC00:03
*** edmondsw has joined #openstack-powervm00:05
*** edmondsw has quit IRC00:08
*** edmondsw has joined #openstack-powervm00:09
*** edmondsw has quit IRC00:13
*** thorst_afk has joined #openstack-powervm00:39
*** thorst_afk has quit IRC00:44
*** thorst_afk has joined #openstack-powervm00:47
*** thorst_afk has quit IRC00:47
*** thorst_afk has joined #openstack-powervm00:49
*** thorst_afk has quit IRC00:49
*** thorst_afk has joined #openstack-powervm01:54
*** thorst_afk has quit IRC01:59
*** thorst_afk has joined #openstack-powervm02:05
*** thorst_afk has quit IRC02:05
*** esberglu has joined #openstack-powervm02:20
*** esberglu has quit IRC02:20
*** thorst_afk has joined #openstack-powervm02:36
*** thorst_afk has quit IRC02:41
*** esberglu has joined #openstack-powervm03:14
*** esberglu has quit IRC03:18
*** thorst_afk has joined #openstack-powervm03:38
*** thorst_afk has quit IRC03:42
*** chhavi has joined #openstack-powervm04:11
*** thorst_afk has joined #openstack-powervm04:38
*** thorst_afk has quit IRC04:43
*** thorst_afk has joined #openstack-powervm05:39
*** thorst_afk has quit IRC05:44
*** esberglu has joined #openstack-powervm05:59
*** edmondsw has joined #openstack-powervm06:02
*** esberglu has quit IRC06:03
*** edmondsw has quit IRC06:06
*** thorst_afk has joined #openstack-powervm06:40
*** thorst_afk has quit IRC06:45
*** esberglu has joined #openstack-powervm06:52
*** esberglu has quit IRC06:53
*** esberglu has joined #openstack-powervm06:53
*** esberglu has quit IRC06:53
*** esberglu has joined #openstack-powervm06:54
*** esberglu has quit IRC06:58
*** k0da has joined #openstack-powervm07:36
*** thorst_afk has joined #openstack-powervm07:41
*** thorst_afk has quit IRC07:45
*** k0da has quit IRC08:09
*** thorst_afk has joined #openstack-powervm08:42
*** thorst_afk has quit IRC08:46
*** thorst_afk has joined #openstack-powervm09:42
*** thorst_afk has quit IRC09:47
*** chhavi has quit IRC10:14
*** k0da has joined #openstack-powervm10:31
*** thorst_afk has joined #openstack-powervm10:43
*** thorst_afk has quit IRC10:48
*** thorst_afk has joined #openstack-powervm11:09
*** thorst_afk has quit IRC11:11
*** esberglu has joined #openstack-powervm11:26
*** esberglu has quit IRC11:26
*** thorst_afk has joined #openstack-powervm12:04
*** esberglu has joined #openstack-powervm12:19
*** smatzek has joined #openstack-powervm12:22
*** esberglu has quit IRC12:23
*** apearson has joined #openstack-powervm12:44
*** esberglu has joined #openstack-powervm13:07
*** esberglu has quit IRC13:07
*** efried is now known as fried_rice13:20
*** esberglu has joined #openstack-powervm13:36
*** esberglu has quit IRC13:37
*** esberglu has joined #openstack-powervm13:39
fried_riceesberglu We still running with that tempest patch to ignore connection timeouts?13:52
esberglufried_rice: Yeah13:52
fried_ricemmkay.13:52
esbergluIt only ever seems to hit it once at a time, haven't had a chance to look further13:53
fried_riceDoesn't seem like something that should be our problem.13:53
fried_riceI don't really have a problem running with that patch more or less permanently.13:53
*** miltonm has joined #openstack-powervm14:05
esberglufried_rice: Yeah that was my thinking as well. No hurry to fix it anyways14:06
*** k0da has quit IRC14:08
*** edmondsw has joined #openstack-powervm14:17
esbergluhttps://blueprints.launchpad.net/nova/+spec/powervm-nova-it-compute-driver14:35
esberglufried_rice: edmondsw: ^14:36
edmondswesberglu awesome... I was going to do that this week14:36
edmondswyou guys keep beating me to things :)14:36
esbergluedmondsw: Now we just have to push a spec to nova-specs right?14:37
fried_riceesberglu Yes14:37
edmondswyep14:37
fried_riceYou can start off by copying the one from pike14:37
fried_ricehttps://github.com/openstack/nova-specs/blob/master/specs/pike/approved/powervm-nova-compute-driver.rst14:37
fried_riceHowever, it may be worth correlating with the latest queens template14:38
edmondswyep, and then we'll need to modify it a bit14:38
edmondsw++14:38
fried_ricehttps://github.com/openstack/nova-specs/blob/master/specs/queens-template.rst14:38
edmondswI think they'll require that14:38
fried_riceAlso note that there's a pending update to that template which you should also incorporate.14:38
fried_ricehttps://review.openstack.org/#/c/456756/14:39
fried_riceNot that I think we should have any upgrade impacts.14:39
fried_riceBut include the section anyway.14:39
edmondswesberglu I can do the spec unless you want to14:39
esberglufried_rice: edmondsw: Have we determined what functionality we are targeting for queens?14:40
esbergluI know we have talked about it, not sure if we had a hard list yet though14:41
esbergluedmondsw: I would like to do it14:41
fried_riceAt least config drive and OVS.  thorst_afk should chime in on that.14:41
edmondswyes... PCI passthrough, network (at least SEA, though I'd like OVS as well), config drive, vSCSI14:41
fried_ricePCI passthrough?  In tree?14:41
thorst_afkwe need enough to deploy a real VM that someone can put workload on14:41
thorst_afknetwork (just do both), config drive -> must do's14:42
thorst_afkvscsi would be great for a cinder story14:42
edmondswfried_rice we could do pci just out of tree, but I thought it would be nice to do in both unless there's a reason not to14:42
fried_riceYeah, I guess there's no reason not to.14:42
thorst_afkPCI passthru would be nice in tree, needed out of tree?14:42
thorst_afkfried_rice edmondsw: reviewer bandwidth14:42
thorst_afkif there is enough bandwidth for all...14:42
edmondswright, I view the reviewer bandwidth as a reason to do pci IT... we want them involved in that14:43
fried_riceAs I dig further into the generic resource provider stuff, it's becoming less probable that we'll be able to do our PCI passthrough that way in q - so we'll need our hacked version probably until r.14:43
edmondswdo you think we'll get objections to that hacked implementation going into q IT?14:44
fried_riceRight, that was my concern.14:44
fried_riceNot necessarily so much objections as no reviewer's gonna want to touch it with a ten-foot pole.14:44
edmondswwell, we can always pull it out later... but easier to put it in the plan for now, and then see how that goes?14:44
edmondswat least see how the PTG conversations go... could be pulled quickly :)14:45
fried_ricee.g. see Jay's comments on https://review.openstack.org/#/c/496434/14:45
fried_riceI'm not going to get any traction talking about PowerVM's hacked PCI passthrough implementation at the PTG.14:45
fried_riceCause it has nothing to do with nova.14:45
edmondswfried_rice I thought we'd be talking about that hacked up way of doing things as a way to elucidate the issues driving the work that will go into r14:46
fried_riceedmondsw Meh, that's sorta done.14:47
edmondswcool14:47
edmondswI did see Jay's comments but haven't had a chance to read them yet... I need to do that today14:47
fried_riceI mean, yeah, it's something I'll talk about, but I don't think it's necessary to have a change set to put in front of everyone.14:47
edmondswk14:48
edmondswso you think leave that OOT?14:48
edmondswI don't think there's a reason we have to have it IT... it was more to help us get things done14:49
edmondswif it doesn't do that...14:49
fried_riceedmondsw I don't mind porting it in tree, but we should finish it up OOT first.  And it has served its purpose as a driver of the in-tree device management revolution.14:50
edmondswsure14:50
edmondswesberglu so for the moment anyway don't list PCI passthrough in the spec14:50
esbergluedmondsw: k14:51
openstackgerritEric Fried proposed openstack/nova-powervm master: snapshot capability in DiskAdapter (local: False)  https://review.openstack.org/46642515:04
openstackgerritEric Fried proposed openstack/nova-powervm master: SSP supports nonstandard image caching  https://review.openstack.org/50009915:19
*** tjakobs has joined #openstack-powervm15:23
fried_ricethorst_afk Is snapshot supported in the localdisk driver?  According to the capability bits, it ain't; but according to tjakobs, it works.15:23
thorst_afkI think tjakobs is looking at it with the lens of SDE15:24
thorst_afkand not necessarily with the lens of traditional VIOS?15:24
fried_riceAh, so supported with SDE but not traditional.15:24
fried_ricethorst_afk Looking at https://bugs.launchpad.net/nova-powervm/+bug/1661395 and https://review.openstack.org/#/c/466425/ btw15:25
openstackLaunchpad bug 1661395 in nova-powervm "Snapshot with localdisk not supported" [Low,In progress] - Assigned to Eric Fried (efried)15:25
thorst_afkwe should bounce that off seroyer.15:25
tjakobsabout a year ago, i put up a fix for supporting SDE, but i had also verified i didn't break anything with an traditional setup https://review.openstack.org/#/c/36815715:25
fried_riceIf that's the case, we may want to detect SDEness and make that capability bit dynamic accordingly.15:25
thorst_afkI think the challenge was that our 'SDE' check was just 'is_mgmt_partition'15:25
thorst_afkrather than something in the VIOS bits itself.15:25
thorst_afkwe want to get to capabilities15:26
thorst_afkwhat is the 'VIOS' capable of.  Not, do I happen to be the mgmt partition, so I know its different.15:26
thorst_afkI think that's my main gripe.15:27
thorst_afkwe can do it...sure.  I just would prefer we do the capabilities approach.15:27
fried_riceSo this change https://review.openstack.org/#/c/466425/ will actually regress SDE.15:28
fried_riceSo we shouldn't do it.15:28
fried_riceuntil we have a better answer for that capability bit.15:28
thorst_afkmaybe something to ask Hsien about?15:29
thorst_afktjakobs change looks pretty reasonable IMO, unless we can get a capability bit.15:29
thorst_afkor I wonder if we could hide capability bits in pypowervm until we get it in the REST API.  That seems kinda silly tho15:30
fried_ricethorst_afk tjakobs change makes it look like it may be possible to have a nvl-as-vios and *also* traditional VIOSes.15:31
fried_riceAnd a given VM's disk might be mapped from either one.15:31
fried_riceSo we can't say at the outset whether snapshot is supported or not.15:31
fried_ricecause it might be different for different VMs.15:31
thorst_afkbut line 246 forces it to just be mgmt15:32
thorst_afkin storage.py15:32
thorst_afkI don't think it says that for a given host, you can have from either15:32
fried_riceonly if we happen to find it on the mgmt15:32
thorst_afkits just saying if your host is configured to host local disks through mgmt, you can15:32
thorst_afkand if you're configured for traditional you can't15:32
fried_riceIf L250 doesn't pass, we move on to trying to find it on the VIOS.15:32
thorst_afkalbeit the code is in the mainline execution path...but I think that's the realization15:33
fried_ricemm, actually, localdisk driver only has one VIOS, nah?15:33
fried_riceyup.15:33
thorst_afklocaldisk can only be hosted by one VIOS15:33
fried_riceOkay, so that's solid.15:33
thorst_afkeven if there are many VIOSes on the system15:33
fried_riceI can fix that up.15:33
thorst_afkyeah, I think his change (without diving into it deeply) looks like a reasonable path until capability bits15:33
thorst_afkbut tjakobs we should instead be pushing on Hsien to get these capabilities expressed in the API15:34
fried_ricetjakobs Under what circumstances does L250 fail, but the rest still succeeds?15:34
thorst_afk(this fix looks nice though because if you are hosting through the mgmt, it looks like it stops trying to map to the mgmt...its a bug fix from that point of view)15:34
fried_riceIs there, like, a disk type where we wouldn't find it via boot_disk_path_for_instance, but we would find it and be able to attach it via connect_instance_disk_to_mgmt??15:35
fried_ricethorst_afk We're not debating tjakobs change set - it merged almost a year ago :)15:35
thorst_afklol15:36
thorst_afkwhoops15:36
tjakobsefried I don't think so... Trying to remember15:36
tjakobsyeah, thorst_afk you already +2'd it15:36
fried_ricethorst_afk we're trying to figure out what to do about https://review.openstack.org/#/c/466425/15:36
fried_riceI think I have a fix that we'll be happy with.  Sec...15:36
thorst_afkheh15:43
thorst_afkI'm so up to date15:43
*** k0da has joined #openstack-powervm15:44
openstackgerritEric Fried proposed openstack/nova-powervm master: SSP supports nonstandard image caching  https://review.openstack.org/50009915:52
openstackgerritEric Fried proposed openstack/nova-powervm master: Add snapshot capability in DiskAdapter  https://review.openstack.org/46642515:52
fried_ricetjakobs thorst_afk ^^15:52
fried_ricethorst_afk Second pair of eyes on 5828 please?15:55
fried_ricewait what the actual f just happened?  Merge conflict??15:56
*** apearson has quit IRC15:58
openstackgerritEric Fried proposed openstack/nova-powervm master: Add snapshot capability in DiskAdapter  https://review.openstack.org/46642516:01
fried_ricethat was effin bizarre.16:01
openstackgerritEric Fried proposed openstack/nova-powervm master: SSP supports nonstandard image caching  https://review.openstack.org/50009916:02
*** miltonm has quit IRC16:07
*** miltonm has joined #openstack-powervm16:08
*** esberglu has quit IRC16:24
*** apearson has joined #openstack-powervm16:43
*** esberglu has joined #openstack-powervm16:47
*** edmondsw has quit IRC16:50
*** esberglu has quit IRC16:51
*** edmondsw has joined #openstack-powervm16:51
*** esberglu has joined #openstack-powervm17:20
fried_riceesberglu Any idea what's going on here https://review.openstack.org/#/c/466425/ https://review.openstack.org/#/c/500099/ ?18:05
esberglufried_rice: I updated pvm-novalink and there are Internal Server Error 500s all over the place18:05
fried_ricelogs are getting cut off18:05
fried_riceso I can't see what's actually happening.18:06
esbergluhttp://184.172.12.213/18/499718/2/check/nova-out-of-tree-pvm/14c00f7/logs/n-cpu.txt.gz18:07
esberglufried_rice: Looks like this is the error18:11
esbergluError 500: javax.servlet.ServletException: java.lang.NoSuchMethodError: com.ibm.hmcl.data.HmclHypervisorInfo.setAixCapable.(Z)V (hmcljni/hmcljni_common.cpp:489)18:11
fried_ricewhoah18:11
fried_riceThat's a sev-1 to changh18:12
fried_riceedmondsw 9/25 is way too far after the PTG for me to remember anything that happened there.18:48
edmondswfried_rice a whole week later?18:48
fried_riceIt'd be hard enough for me to do after the weekend.18:48
fried_riceI'm mostly joshing you.  But I wouldn't be offended if it was closer to the event.18:49
edmondswlol... well, I guess you'll be stretched :)18:49
edmondswfried_rice the first part of the week immediately after doesn't work with everyone slammed closing out a PowerVC sprint on Wednesday, Thursday is already booked, and of course Friday doesn't work for the team in ISTL, so 9/25 was earliest I think we can do18:51
*** apearson has quit IRC18:59
*** esberglu has quit IRC19:04
*** esberglu has joined #openstack-powervm19:05
*** apearson has joined #openstack-powervm19:06
*** k0da has quit IRC19:09
*** apearson has quit IRC19:18
*** apearson has joined #openstack-powervm19:18
*** k0da has joined #openstack-powervm19:26
*** smatzek has quit IRC20:16
fried_riceesberglu You could propose a change to move the pike powervm in-tree blueprint from approved to implemented.20:27
fried_riceor I could.  Call it.20:27
*** tjakobs has quit IRC20:38
*** thorst_afk has quit IRC20:46
esberglufried_rice: Just saw this. I'm about to head. I can do it later this evening when I check on CI20:48
fried_riceesberglu It's cool, I should probably be the one to do it, since (I think) I owned it.20:49
esberglufried_rice: Okay. I'm out for the day have a good weekend20:49
*** esberglu has quit IRC20:49
*** esberglu has joined #openstack-powervm20:50
*** esberglu has quit IRC20:54
*** thorst_afk has joined #openstack-powervm21:32
*** thorst_afk has quit IRC21:36
*** thorst_afk has joined #openstack-powervm21:48
*** thorst_afk has quit IRC21:50
*** apearson has quit IRC22:06
*** thorst_afk has joined #openstack-powervm22:29
*** thorst_afk has quit IRC22:32
*** miltonm has quit IRC23:18
*** k0da has quit IRC23:47

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