Friday, 2016-08-05

*** tjakobs has joined #openstack-powervm00:01
*** tjakobs has quit IRC00:06
*** thorst has quit IRC00:06
*** thorst has joined #openstack-powervm01:04
*** thorst has quit IRC01:11
*** thorst has joined #openstack-powervm01:15
*** thorst has quit IRC01:16
*** esberglu has quit IRC01:43
*** esberglu has joined #openstack-powervm02:14
*** thorst has joined #openstack-powervm02:17
openstackgerritEric Berglund proposed openstack/nova-powervm: DNM: ci check  https://review.openstack.org/32831502:22
openstackgerritEric Berglund proposed openstack/nova-powervm: DNM: CI Check2  https://review.openstack.org/32831702:22
openstackgerritEric Berglund proposed openstack/nova-powervm: DNM1  https://review.openstack.org/30023102:22
openstackgerritEric Berglund proposed openstack/nova-powervm: DNM: CI Check  https://review.openstack.org/29593502:22
openstackgerritEric Berglund proposed openstack/nova-powervm: DNM: Test Change Set 2  https://review.openstack.org/30023202:22
*** kriskend has quit IRC02:24
*** kriskend_ has quit IRC02:24
*** thorst has quit IRC02:25
*** esberglu has quit IRC02:35
*** thorst has joined #openstack-powervm02:43
*** thorst has quit IRC02:43
*** tjakobs has joined #openstack-powervm02:53
*** esberglu has joined #openstack-powervm02:58
*** esberglu has quit IRC02:59
*** tjakobs has quit IRC03:00
*** Ashana has joined #openstack-powervm03:35
*** Ashana has quit IRC03:39
*** Ashana has joined #openstack-powervm03:41
*** thorst has joined #openstack-powervm03:44
*** Ashana has quit IRC03:45
*** Ashana has joined #openstack-powervm03:46
*** Ashana has quit IRC03:52
*** thorst has quit IRC03:52
*** esberglu has joined #openstack-powervm03:55
*** kotra03 has joined #openstack-powervm03:56
*** esberglu has quit IRC04:02
*** thorst has joined #openstack-powervm04:51
*** thorst has quit IRC04:58
*** jwcroppe has joined #openstack-powervm05:11
*** jwcroppe has quit IRC05:51
*** thorst has joined #openstack-powervm05:56
*** thorst has quit IRC06:03
*** thorst has joined #openstack-powervm07:01
*** thorst has quit IRC07:08
*** Ashana has joined #openstack-powervm07:14
*** Ashana has quit IRC07:18
*** openstackgerrit has quit IRC08:03
*** openstackgerrit has joined #openstack-powervm08:03
*** thorst has joined #openstack-powervm08:08
*** alechevalier has joined #openstack-powervm08:09
*** alechevalier has quit IRC08:11
*** k0da has joined #openstack-powervm08:13
*** thorst has quit IRC08:13
*** thorst has joined #openstack-powervm09:10
*** thorst has quit IRC09:18
*** kotra03 has quit IRC09:25
openstackgerritRavi Kumar Kota proposed openstack/nova-powervm: WIP: PowerVM: Implement get_instance_diagnostics  https://review.openstack.org/35052509:40
*** kotra03 has joined #openstack-powervm10:02
*** thorst has joined #openstack-powervm10:16
*** thorst has quit IRC10:23
*** kotra03 has quit IRC10:25
*** kotra03 has joined #openstack-powervm10:25
*** thorst has joined #openstack-powervm11:20
*** svenkat has joined #openstack-powervm11:26
*** thorst has quit IRC11:28
*** smatzek has joined #openstack-powervm11:29
openstackgerritArun Mani proposed openstack/nova-powervm: Deploy of a VM occasionally fails due to invalid keystone token  https://review.openstack.org/35127011:31
openstackgerritArun Mani proposed openstack/nova-powervm: Deploy of a VM occasionally fails due to invalid keystone token  https://review.openstack.org/35127011:32
*** thorst has joined #openstack-powervm11:48
*** Ashana has joined #openstack-powervm12:04
*** Ashana has quit IRC12:28
*** thorst_ has joined #openstack-powervm12:45
*** thorst has quit IRC12:49
*** catintheroof has quit IRC12:53
*** catintheroof has joined #openstack-powervm13:05
openstackgerritymadhavi@in.ibm.com proposed openstack/nova-powervm: [WIP] Plug updated VIFs  https://review.openstack.org/35076813:10
*** esberglu has joined #openstack-powervm13:12
*** madhaviy has joined #openstack-powervm13:12
*** mdrabe has joined #openstack-powervm13:14
*** lmtaylor has joined #openstack-powervm13:18
thorst_madhaviy: Great update on the WIP.  I think the next step is to update the tests to validate the new code that was put in13:32
thorst_the iteration you did now got it to pass the existing tests, which is important.  Next though is validation of the new bits.13:32
*** jwcroppe has joined #openstack-powervm13:33
madhaviyok, I will add more tests13:34
*** kriskend has joined #openstack-powervm13:38
*** kriskend_ has joined #openstack-powervm13:38
*** seroyer has joined #openstack-powervm13:40
*** tjakobs has joined #openstack-powervm13:46
*** seroyer has quit IRC13:51
*** catintheroof has quit IRC14:00
*** burgerk has joined #openstack-powervm14:01
*** openstackgerrit has quit IRC14:03
*** openstackgerrit has joined #openstack-powervm14:03
*** edmondsw has joined #openstack-powervm14:04
*** catintheroof has joined #openstack-powervm14:07
svenkat@efried: I have a suggestion for redundancy and capacity data in upcoming SR-IOV vif driver14:36
efriedtell me14:36
svenkatif you can make them two separate methods and let them return the required data14:36
efriedNot sure what you're referencing.14:37
thorst_efried: at some point, would like to chat about how to detect when the port labels change from networking-powervm14:44
thorst_I'm wondering if we can use an event model instead of polling?14:44
efriedWell14:44
efriedI put up a patch set last night that kinda does both.14:45
efriedThe rpc_loop re-grabs the data14:45
efriedBut the existing (inherited) event handler posts the changes back to the world.14:45
efriedI'm still trying to get my brain around the order of operations.14:46
efriedthorst_, svenkat: does this vNIC plug/unplug stuff need to be able to work for both LPAR and VIOS types?14:49
thorst_efried: LPARs14:49
thorst_efried: I'll look at the patch set.  I'm worried about getting that data every 2 seconds.14:49
efriedk, makes life a little easier.14:49
thorst_efried: well, to be clear, plug/unplug only works against LPARs because OpenStack manages client VMs14:50
thorst_we should never have a client VM that is a VIOS type14:50
efriedThat's kinda what I figured.14:50
thorst_unless apearson goes crazy14:50
efriedAs far as getting the data every 2s - it's a very quick call, and it's happening per vif plugin (and only for the SR-IOV one at that) - not for like every instance or anything.14:51
thorst_ahhh14:51
thorst_I should review code before I complain about it14:51
efriedI take your point, and could certainly be persuaded that it should be event-driven.  It's just two orders of magnitude more complex that way, so there would have to be a compelling reason.14:52
thorst_well, I do personally hate event only models14:53
thorst_cause an event always slips through the cracks14:53
*** lmtaylor has quit IRC14:53
*** mdrabe has quit IRC14:55
efriedthorst_, agree.  Always seem really brittle.14:57
efriedTrying to think if etag would save us anything.14:58
efriedI can cache the System wrapper and use the refresh() method rather than getting a new one each time.  That's better code - but I'm not sure it's any more efficient.14:58
*** mdrabe has joined #openstack-powervm15:02
*** dwayne has joined #openstack-powervm15:05
*** lmtaylor has joined #openstack-powervm15:07
thorst_efried: not more efficient...but yeah15:07
efriedIt may be a trivial amount more efficient because the REST response has no XML in it.15:07
efried...if nothing has changed.15:07
openstackgerritEric Fried proposed openstack/nova-powervm: WIP: VIF driver implementation for SR-IOV  https://review.openstack.org/34341915:08
efriedthorst_, svenkat ^^ like this, for redundancy/capacity?15:08
openstackgerritEric Fried proposed openstack/networking-powervm: WIP: Mechanism driver for powervm SR-IOV interface  https://review.openstack.org/34342315:09
svenkatefried: neutron port id shold be involved here. there could be more than one SR-IOV adapater attached to vif. extra specs is for entire instance15:11
efriedSo the consumer would have to make the extra_spec entry a dict15:12
efriedI assume that's... possible?15:12
svenkatyes… i am getting that dictionary details… one moment15:12
efried'<physnet>': { 'redundancy': 3, 'capacity': 0.05 }15:12
efried?15:12
*** jwcroppe has quit IRC15:12
*** jwcroppe has joined #openstack-powervm15:13
efriedOr even { '<pport_loc>': { 'capacity': 0.05 }, ..., '<physnet_name>' { 'redundancy': 3, 'capacity': 0.07 }, ... }15:14
svenkat{'powervc-sriov-ports':[{'port_uuid': 'ddc24826-504d-422b-b758-a84bcbe77992', 'capacity' : '50', 'redundancy-level': '4'}]}15:15
efriedWhere did that come from?15:15
efriedWhere does this get created?  By the admin when defining the flavor?  How did they know the port UUID?15:16
svenkatyou need to create the port before you deploy for ‘direct’ types , so you know the port id15:16
efriedI don't think so.15:16
svenkatotherwise, ‘normal’ port is getting created if you specify network id during boot15:17
efriedthorst_, help me out here.  There should be no need to do this in two steps, right?  You just have to select the physnet name.15:17
efriedSay wha?  Wouldn't that be a configuration thing?15:18
thorst_efried: I think that 1) that is a powervm thing (not powervc).  2) you probably want to set capacity and redundancy per VIF.  Not per physical network15:19
thorst_different workloads on the same physical network have different needs...15:19
efriedthorst_, would we generally create only one vif per physnet per instance?15:27
thorst_efried: I think so.  Generally15:32
*** burgerk has quit IRC15:36
*** lmtaylor has left #openstack-powervm15:50
thorst_esberglu: it seems that quota_floating_ips can no longer be set to -1.  I think this may actually be a bug you want to open to nova16:12
thorst_I'm seeing that in new devstacks and I know our undercloud uses it16:12
esbergluthorst: Yeah I hit that too. Do we even need that config option? There are a bunch of other config options that had min=0 added, while others had min=-1 added in this change. Not sure if they were intentionally doing it that way16:18
esbergluhttps://github.com/openstack/nova/commit/2eebb5edc6c236252e2da1ab1a3e0120de160acd16:18
esbergluI don’t know why they would get rid disabling some of the quotas but since its not all of them it seems to be on purpose16:25
*** burgerk has joined #openstack-powervm16:27
thorst_well, it seems like a proper bug16:36
thorst_but we can probably toss that one16:36
*** k0da has quit IRC16:36
esbergluthorst_: Okay I will open a bug for it16:39
thorst_and maybe even a good bug fix opportunity16:39
esbergluYep16:42
*** lmtaylor has joined #openstack-powervm16:55
openstackgerritEric Fried proposed openstack/nova-powervm: WIP: VIF driver implementation for SR-IOV  https://review.openstack.org/34341916:55
*** madhaviy has quit IRC16:59
*** kotra03 has quit IRC17:06
thorst_efried: https://github.com/openstack/networking-powervm/blob/master/doc/source/devref/usage.rst17:52
thorst_I think that is the conf option doc17:52
thorst_we'd need that updated for sr-iov too17:52
*** seroyer has joined #openstack-powervm18:04
efriedthorst_, that guy is pretty sparse.  E.g. it doesn't tell you *how* to set up your SEA, or even provide a pointer to a doc that does.18:32
*** kriskend has quit IRC18:35
*** kriskend_ has quit IRC18:35
efriedFor SR-IOV, I was thinking we would need to document18:36
efried- the pvmctl command to assign port labels18:36
efried- the neutron port-create command syntax (including the redundancy & capacity stuff we discussed)18:36
efried- the conf options: seems like we need to document the new ml2_conf.ini mechanism_drivers value ('pvm_sriov') and the new nova.conf setting ('vnic_required_vfs')18:36
efriedAnything else?18:36
thorst_efried: I think things like how to boot with a SR-IOV based vnic18:52
thorst_but I guess that's in the neutron port-create18:52
efriedWe gotta assume they know how to specify an existing port to nova boot.18:52
*** esberglu has quit IRC18:53
*** catintheroof has quit IRC19:00
efriedthorst_ - "These configuration options go in the AGENT section of the CONF file."19:01
efriedWhich CONF file??19:01
thorst_ml2.conf19:09
*** esberglu has joined #openstack-powervm19:10
efriedthorst_ A section literally called [AGENT] ?19:11
efriedor a section called [pvm_sriov] ?19:12
thorst_I think literally called [AGENT]19:17
thorst_hop on neo3819:17
efriedWell.19:19
efriedIs heal_and_optimize_interval a neutron thing?19:20
thorst_efried: its a me thing19:21
efriedIs it a private/undocumented conf option?19:21
efriedI mean, it's undocumented; is it supposed to be undocumented?19:21
*** thorst__ has joined #openstack-powervm19:23
thorst__no, it was meant to be documented.19:23
efriedthorst__, I'm going to open a bug, since a) I don't want to fold that into my current change set; b) I wouldn't know how to document it anyway; and c) I don't know if there are more opts that need to be documented.19:25
*** burgerk_ has joined #openstack-powervm19:25
efriedthorst__ - I suppose it's too late to rename bridge_mappings to sea_bridge_mappings19:25
thorst__correct.19:26
*** thorst_ has quit IRC19:26
*** thorst__ is now known as thorst_19:26
*** burgerk has quit IRC19:29
efriedsvenkat: I shouldn't need to say --binding:profile type=dict physical_network=whatever19:32
efriedThe physical network name is already in the vif19:32
efriedam I wrong?19:32
svenkati found that only when you do —binding:profile type-dict physical_network=xxx i could to vif.get_physical_network() and get it…19:39
svenkatotherwise i was getting none.19:39
svenkator did you change anything in mechnism driver to get this to work? or actually you can also get physical network from segment (neutron) and put it in vif_details (get_vif_details) in mech driver code19:40
efriedsvenkat, looking at get_physical_network(), it should just work by getting the network name out of ['network']['meta']['physical_network']19:41
efriedI'll try it out.19:41
svenkatok..19:41
svenkatso we can use binding:profile only for redundancy and capacity. ..19:41
efriedright, that was my thought.19:44
*** k0da has joined #openstack-powervm19:44
*** erlarese has quit IRC19:45
efriedthorst_ https://bugs.launchpad.net/networking-powervm/+bug/161040419:56
openstackLaunchpad bug 1610404 in networking-powervm "Update config options table in usage.rst" [Undecided,New]19:56
efriedthanks, openstack bot.  I win.19:56
efriedthorst_, svenkat: Should we put the redundancy setting into ml2_conf.ini instead?19:57
efriedHeck, should we even bother with the conf setting, now that we have a way to specify it in the port-create?19:58
svenkatefreid: yes. it should be in port-create .19:58
efriedum19:59
efriedIt's going to be in port-create for sure.19:59
efriedThe question is whether we should bother having a conf option for it anymore19:59
efriedand if so, whether it should be in the nova.conf (as currently designed) or if it makes more sense for it to be in the ml2_conf.ini19:59
efriedI know it's being *used* in the vif driver, but from the user's perspective, it may make more sense as a ml2 plugin conf option.20:00
thorst_efried: I like your suggestion.20:01
efriedwhich one?20:01
thorst_nova can always assume it comes from one place that way20:01
thorst_put it in ml2.20:01
efriedokay.20:01
efriedShould we put a capacity default in there too?20:01
thorst_yep20:01
thorst_totally dig that20:02
efriedSecond thoughts... not sure we can reasonably do that.20:02
thorst_(until I don't)20:02
efriedCause it has to be a multiple of the min capacity granularity.20:02
thorst_well, we could reasonably set it to 2%20:02
thorst_but...20:02
efriedAnd it may be different for different ports20:02
efriedfor different groups of ports20:02
efriedfor different networks.20:02
thorst_right...if it were ever to go down to 1%20:02
efriedtoo complex to handle.20:03
efriedleave it out.20:03
thorst_well, way to build someone up and then destroy their hopes20:06
openstackgerritDrew Thorstensen proposed openstack/networking-powervm: Simplify host_uuid and gets  https://review.openstack.org/34439920:06
*** thorst__ has joined #openstack-powervm20:16
*** apearson has joined #openstack-powervm20:17
*** thorst_ has quit IRC20:18
*** svenkat has quit IRC20:19
*** apearson has quit IRC20:31
*** thorst__ has quit IRC20:46
*** burgerk_ has quit IRC20:49
*** thorst_ has joined #openstack-powervm20:50
*** smatzek has quit IRC20:54
*** thorst_ has quit IRC20:55
*** lmtaylor has left #openstack-powervm20:56
openstackgerritEric Fried proposed openstack/nova-powervm: WIP: VIF driver implementation for SR-IOV  https://review.openstack.org/34341921:02
openstackgerritEric Fried proposed openstack/nova-powervm: WIP: VIF driver implementation for SR-IOV  https://review.openstack.org/34341921:12
openstackgerritEric Fried proposed openstack/nova-powervm: WIP: VIF driver implementation for SR-IOV  https://review.openstack.org/34341921:18
*** dwayne has quit IRC21:30
*** edmondsw has quit IRC21:42
*** mdrabe has quit IRC22:05
*** tjakobs has quit IRC22:21
openstackgerritEric Fried proposed openstack/networking-powervm: WIP: Mechanism driver for powervm SR-IOV interface  https://review.openstack.org/34342322:25
*** seroyer has quit IRC22:34
*** k0da has quit IRC23:37
*** seroyer has joined #openstack-powervm23:45
*** esberglu has quit IRC23:52

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