Monday, 2016-08-01

*** thorst has joined #openstack-powervm00:50
*** thorst has quit IRC00:59
*** esberglu has joined #openstack-powervm01:02
*** esberglu has quit IRC01:06
*** thorst has joined #openstack-powervm02:04
*** thorst has quit IRC02:18
openstackgerritSridhar Venkat proposed openstack/networking-powervm: WIP: Mechanism driver for powervm SR-IOV interface  https://review.openstack.org/34342302:30
*** jwcroppe has joined #openstack-powervm02:48
*** thorst has joined #openstack-powervm03:19
*** thorst has quit IRC03:27
*** thorst has joined #openstack-powervm04:27
*** thorst has quit IRC04:33
*** seroyer has joined #openstack-powervm05:28
*** thorst has joined #openstack-powervm05:29
*** kotra03 has joined #openstack-powervm05:32
*** seroyer has quit IRC05:33
*** jwcroppe has quit IRC05:33
*** jwcroppe has joined #openstack-powervm05:34
*** thorst has quit IRC05:37
*** thorst has joined #openstack-powervm07:20
*** thorst has quit IRC07:29
*** k0da has joined #openstack-powervm08:09
*** thorst has joined #openstack-powervm08:26
*** thorst has quit IRC08:33
*** thorst has joined #openstack-powervm09:31
*** thorst has quit IRC09:38
*** thorst has joined #openstack-powervm10:36
*** thorst has quit IRC10:44
*** Ashana has joined #openstack-powervm11:38
*** edmondsw has joined #openstack-powervm11:40
*** erlarese has joined #openstack-powervm11:44
*** smatzek has joined #openstack-powervm11:58
*** thorst has joined #openstack-powervm12:05
*** k0da has quit IRC12:33
*** k0da has joined #openstack-powervm13:04
*** tblakeslee has joined #openstack-powervm13:07
*** mdrabe has joined #openstack-powervm13:09
*** jwcroppe_ has joined #openstack-powervm13:11
*** jwcroppe has quit IRC13:13
*** jwcropp__ has joined #openstack-powervm13:13
*** kotra03 has quit IRC13:15
*** jwcroppe_ has quit IRC13:16
*** seroyer has joined #openstack-powervm13:32
openstackgerritSridhar Venkat proposed openstack/networking-powervm: Checkin blueprint for networking-powervm for SR-IOV VIFs support  https://review.openstack.org/32221013:34
*** efried has quit IRC13:36
*** efried has joined #openstack-powervm13:36
*** tblakeslee has quit IRC14:01
*** k0da has quit IRC14:02
*** tpeoples has quit IRC14:04
*** tsjakobs has joined #openstack-powervm14:11
*** k0da has joined #openstack-powervm14:14
*** burgerk has joined #openstack-powervm14:15
*** tpeoples has joined #openstack-powervm14:18
*** tblakeslee has joined #openstack-powervm14:23
*** erlarese_ has joined #openstack-powervm14:25
*** erlarese has quit IRC14:28
*** erlarese_ is now known as erlarese14:28
*** mdrabe has quit IRC14:36
*** lmtaylor has joined #openstack-powervm14:41
*** mdrabe has joined #openstack-powervm14:42
*** seroyer has quit IRC14:51
*** esberglu has joined #openstack-powervm14:58
*** kriskend has joined #openstack-powervm15:02
*** svenkat has joined #openstack-powervm15:02
*** kriskend_ has joined #openstack-powervm15:03
svenkatefried, thorst : this is about pci_device_id related monkey patches in sriov vif patchset : https://review.openstack.org/#/c/343419/5/nova_powervm/virt/powervm/vif.py15:04
efriedYuh.15:05
efriedsvenkat, can you explain how this came about in the first place?15:05
efriedHelp me with the background.15:05
*** kotra03 has joined #openstack-powervm15:05
svenkatsure, if i create a neutron port of vnic type direct and use it to deploy a VM15:05
svenkatthere are three areas in compute code that it does not let spawn and allocate_network_instance to go through15:05
*** seroyer has joined #openstack-powervm15:06
svenkatall those three are mentioned in the patchset and monkey patched15:06
svenkatthey are all related to pci_device_id not being present15:06
svenkatcouple of them are in nova.network.neutronv2.api.API and one in nova.compute.claims.Claim15:07
efriedLet's start with monkey_populate_neutron_extension_values15:07
efriedI don't see a difference between your patched code and the original code.15:07
efriedCan you point it out?15:07
svenkatsure.. one moment15:08
svenkatline 76, pci_request_id is set to None15:08
svenkatthis is the difference15:08
efriedI see.15:08
efriedSo the original code makes _populate_neutron_binding_profile a no-op; but you've activated it.15:10
efriedsorry, vice versa.15:10
svenkatok…15:10
svenkatyes.15:10
efriedokay, this one should be simple enough.15:11
svenkatok…15:11
svenkatthe code is in network api in nova… is there anything in nova-powervm to overwrite it?15:12
thorstsvenkat: or how to we change the PowerVM code to make it work with the existing behavior of nova.15:13
thorstthats been my stance all along15:13
svenkatok…15:13
svenkatso how do we do it in this particular case15:14
svenkatnext one is similar to this one.15:14
efriedWe may need to massage the pci whitelist to make that method no-op.15:14
svenkatok…15:15
svenkatso far i could not figure out how this required value flows within nova compute code, (that has entry or exit points in nova-powervm code).15:17
efriedYup, looking.15:17
svenkatthanks15:18
efriedthorst, svenkat: we may need to inject a dummy value into the pci whitelist to make this work.15:18
efriedwould that be a reasonable approach?15:18
svenkat ok…15:18
thorstefried: yes.15:19
thorstI was assuming our dummy values would be some form of our physical network names15:19
efriedLet me look at the others and see if they would be resolved by similar means.15:19
*** k0da has quit IRC15:20
efriedsvenkat, this is weird, I can't find _populate_pci_mac_address at all.15:22
svenkatthis is a new method added15:22
svenkatare you looking in mitaka  or newton15:22
svenkati had the same issue… my devstack environment has it15:23
efriedI'm on the master branch of nova.15:24
svenkatok…15:24
*** apearson has joined #openstack-powervm15:26
*** lmtaylor has quit IRC15:28
*** lmtaylor1 has joined #openstack-powervm15:29
*** mdrabe has quit IRC15:32
*** mdrabe has joined #openstack-powervm15:33
thorstsvenkat: I've put back several review comments15:33
svenkatok…15:33
svenkatin nova-powervm or networking-powervm or both?15:33
thorstnetworking-powervm.  Should show up in your request view.15:34
svenkatsure.. looking15:34
efriedthorst, how do I go from somebody's name to their IRC handle?15:36
thorstefried: good q...who are you looking for?15:36
efriedNikola Dipanov15:36
thorstnot sure...15:38
thorsthttps://www.google.com/search?q=Nikola+Dipanov&ie=utf-8&oe=utf-815:38
thorstprobably djipko15:39
efriedYeah, that's what I was seeing.15:39
efriedCan't see him in IRC - at least not the channels I'm searchin.g15:39
thorstworks for Facebook...still a little early for west coast.15:40
efriedWell, svenkat, it appears to me as though the _populate_pci_mac_address method was removed at some point in the last three weeks.15:44
efriedSo that issue may be moot.15:44
svenkatoh ok…15:44
thorstefried FTW15:44
thorst:-)15:45
efriedIt would be tough to figure out when that happened; but I can do that if it's necessary.15:45
svenkatthats good. if it is gone, we can ignore it15:45
efriedBut, in case you needed any further encouragement, this is a dramatic case-in-point why we don't monkey patch - especially private methods.15:45
openstackgerritSridhar Venkat proposed openstack/networking-powervm: Checkin blueprint for networking-powervm for SR-IOV VIFs support  https://review.openstack.org/32221015:45
svenkatok…15:46
thorstefried: I'd like a +1 from you on this before I W+1 it:  https://review.openstack.org/#/c/322210/615:50
efriedthorst, time frame?15:56
thorstefried: dept lunch15:56
efriedThat doesn't help me.15:56
*** thorst is now known as thorst_afk15:56
*** efried has quit IRC16:08
*** kotra03 has quit IRC16:55
*** thorst_afk is now known as thorst17:19
thorstesberglu: I remapped all the volumes to neo617:19
thorstcan you re-add to ssp?  do you know those steps?17:19
esbergluthorst: You just go on the vios and do cluster addnode right?17:40
esbergluWhich vios owns the cluster though?17:42
esbergluthorst: nvm. found it17:45
*** mdrabe has quit IRC18:46
*** mdrabe has joined #openstack-powervm19:09
adreznecthorst: You good on https://review.openstack.org/#/c/348544/ merging then?19:13
*** efried has joined #openstack-powervm19:19
thorstadreznec: looking...19:33
thorstadreznec: yeah, definitely19:35
thorstmerge away19:35
*** k0da has joined #openstack-powervm19:57
*** jwcropp__ has quit IRC20:47
*** jwcroppe has joined #openstack-powervm20:48
*** jwcroppe has quit IRC20:48
*** jwcroppe has joined #openstack-powervm20:48
openstackgerritMerged openstack/nova-powervm: Fix package setup configuration  https://review.openstack.org/34854420:53
efriedthorst, mdrabe: brainstorming solutions for the stale mappings bug again.20:54
thorstk...I need to head out in 15-2020:54
thorstso lets brainstorm quick20:54
efriedWhat I'm thinking now is simply to add a mapping scrub at the end of the destroy flow to clean up any leftovers.20:54
mdrabeyou'd still hit that warning20:55
efriedDon't care.20:55
efriedDo I?20:55
thorstis a warning a bad thing?20:55
thorstWe could change the message.20:55
thorstto be a little friendlier20:55
mdrabeThe warning is saying: we're not gonna clean up this mapping or hdisk20:55
mdrabebut then you're gonna end up cleaning it up20:55
thorstew20:56
efriedYeah; we would need to change that.20:56
efried"Disconnect Volume: The backing hdisk for volume "20:56
efried"%(volume_id)s on Virtual I/O Server %(vios)s is "20:56
efried"not in a valid state.  No disconnect "20:56
efried"actions to be taken as volume is not healthy."),20:56
efriedJust whack that last sentence and I think we're okay.20:57
thorstefried: What other flows could perhaps be impacted by that?20:58
thorstcold migration?20:58
thorst(or does that call down to destroy...I think it does?)20:58
efriedSure, any flow that's using destroy would be impacted, but I believe that's what we want.20:59
efriedIn destroy, we always want all VSCSI mappings for the instance to go away.20:59
*** svenkat has quit IRC21:00
mdrabeIf you're gonna change that warning message it might be nice to add something like "...is not in a valid state. This could be the result of evacuation"21:01
mdrabeThose stale mappings could be tackled from there too though21:02
thorstefried: what about disconnect volume...where you remove a volume but don't destroy the server?21:02
efried"server"?21:03
efriedoh, the instance.21:03
efriedYeah, the plan would be to put the scrub into destroy, not into disconnect_volume.21:03
thorstefried: yep, sorry21:04
thorstI'm just wondering if it could leave a volume around that way that we'd clean up otherwise21:04
thorstnonetheless, its not like we're taking anything away from what we have today21:04
thorstrather, just doing additional clean up....21:04
efriedRight.  Theoretically, disconnect_volume should be destroying any disk that we can actually find.21:04
thorstso I'm leaning towards liking it21:04
efriedThe problem we're having today is that, when the disk has been ripped out, we can't even get a name/UDID to use to identify the mapping.21:05
thorstefried: well, it'll destory a disk on the vscsi disconnect I think21:05
thorstyeah...21:05
thorstso I think that's fine21:05
efriedSo if you try to disconnect_volume in a non-destroy flow, and that disk has been ripped out, you'll still leave that stale mapping around.21:05
efriedthat's still a hole21:05
thorstbut would be cleaned up on a destroy21:06
efriedyes.21:06
thorstso not a significant hole IMO21:06
efriedAnd I don't think we want to go removing storage-less mappings - because if the disk gets restored at some point, we want it to reappear to the VM.21:06
thorstfair enuf21:06
efriedI.e. handle flaky storage backend.21:06
efriedOkay, so now the only question is whether I can use VSCSIBus.delete() or have to do a second VIOS feed GET with VSCSI mapping xags.21:07
mdrabeshouldn't the Feed already be there?21:07
mdrabeWith xags galore21:07
thorsteveryone gets a xag21:08
thorstgotta run, but I'm currently with mdrabe...I'd be thinking that the feed is already there21:08
*** thorst has quit IRC21:08
*** thorst has joined #openstack-powervm21:09
*** thorst has quit IRC21:13
efriedargh, sorry kids.  mdrabe, we *may* be able to use the same feed.  I'll have to look into that.21:15
*** thorst has joined #openstack-powervm21:34
*** lmtaylor1 has quit IRC21:35
*** thorst has quit IRC21:38
*** burgerk has quit IRC21:46
*** smatzek has quit IRC22:03
*** jwcroppe_ has joined #openstack-powervm22:04
*** esberglu has quit IRC22:04
*** jwcroppe has quit IRC22:06
*** mdrabe has quit IRC22:08
*** mdrabe has joined #openstack-powervm22:09
*** mdrabe has quit IRC22:17
*** k0da has quit IRC22:19
*** Ashana has quit IRC22:24
*** esberglu has joined #openstack-powervm22:25
*** tblakeslee has quit IRC22:26
*** efried has quit IRC22:28
*** seroyer has quit IRC22:30
*** Ashana has joined #openstack-powervm22:31
*** Ashana has quit IRC22:35
*** kriskend_ has quit IRC22:40
*** kriskend has quit IRC22:40
*** Ashana has joined #openstack-powervm22:41
*** Ashana has quit IRC22:45
*** esberglu has quit IRC22:45
*** esberglu has joined #openstack-powervm22:49
*** thorst has joined #openstack-powervm22:51
*** Ashana has joined #openstack-powervm22:52
*** Ashana has quit IRC22:56
*** tsjakobs has quit IRC22:57
*** thorst_ has joined #openstack-powervm23:00
*** thorst has quit IRC23:02
*** Ashana has joined #openstack-powervm23:04
*** Ashana has quit IRC23:08
*** Ashana has joined #openstack-powervm23:12
*** thorst_ has quit IRC23:13
*** thorst has joined #openstack-powervm23:14
*** Ashana has quit IRC23:17
*** esberglu has quit IRC23:17
*** Ashana has joined #openstack-powervm23:18
*** thorst has quit IRC23:22
*** Ashana has quit IRC23:22
*** esberglu has joined #openstack-powervm23:25
*** tblakeslee has joined #openstack-powervm23:26
*** Ashana has joined #openstack-powervm23:30
*** Ashana has quit IRC23:34
*** tsjakobs has joined #openstack-powervm23:35
*** Ashana has joined #openstack-powervm23:35
*** edmondsw has quit IRC23:40
*** Ashana has quit IRC23:40
*** tsjakobs has quit IRC23:40
*** Ashana has joined #openstack-powervm23:41
*** Ashana has quit IRC23:46
*** Ashana has joined #openstack-powervm23:47
*** Ashana has quit IRC23:51
*** Ashana has joined #openstack-powervm23:53
*** thorst has joined #openstack-powervm23:54
*** jwcroppe has joined #openstack-powervm23:56
*** Ashana has quit IRC23:57
*** jwcroppe_ has quit IRC23:57

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