Thursday, 2018-03-15

*** janki has joined #networking-sfc03:34
*** mohankumar has joined #networking-sfc05:38
*** mangelm has joined #networking-sfc08:02
*** janki has quit IRC09:28
mangelmHi everyone, when creating a port chain I am  using correlation=None but I'm getting an error in logs. Is it possible to avoid MPLS correlation somehow?11:41
mangelmthis is the error I get in case someone wants to have a look: https://hastebin.com/reloniqari.sql11:43
mangelmand this is the request:11:44
mangelmopenstack sfc port chain create --port-pair-group pgClientM --port-pair-group pg_${VM_ID} --port-pair-group pgServerM --flow-classifier fc1_${VM_ID} --flow-classifier fc2_${VM_ID} --flow-classifier fc3_${VM_ID} --chain-parameters symmetric=True --chain-parameters correlation=None pc_${VM_ID}11:44
mangelmIt does not matter if I put correlation="" or correlation=whatever, the error is still the same11:44
bcafarelmangelm: I have no setup around at the moment, but maybe check the python-neutronclient version (there were some sfc fixes a few months ago)11:57
bcafarelthough they should all be in pike release11:57
mangelmbcafarel I'm using OPNFV XCI deployment, https://wiki.opnfv.org/display/sfc/Deploy+OPNFV+SFC+scenarios12:03
mangelmbcafarel, I am sure they manage to create chains but the difference is they normally use tacker, not networking-sfc cli12:03
mangelmbcafarel, interestingly I'm checking out ovs flows and I see "pop_nsh" actions, but no "push_nsh" in any of the rules12:04
mangelmbcafarel, I guess that is a sign that the rules have not been populated correctly12:05
bcafarelmangelm: yes tacker goes through the api itself, this is probably specific to the osc client12:06
bcafarelmangelm: workaround may be to try with neutron CLI12:06
mangelmbcafarel, ok I can try that and also let's see if using tacker helps. In any case I should see push_nsh actions in openflow, shouldn't I?12:09
bcafarelmangelm: tacker sets nsh correlation? (opnfv does if I remember correctly) so yep you should12:12
mangelmbcafarel, I am not fully sure but I remember some OPNFV colleagues saying that NSH headers can be seen by the SF12:17
bcafarelit depends on the correlation value for the port pair (which will create or not a proxy to strip them)12:21
mangelmbcafarel, hmmm I think I can have a clue for the problem. When the port pair is created with no arguments, correlation is set to "None". But when port chain is created with no parameters correlation is set to "MPLS". Do you think this could be causing problems?12:24
bcafarelwith "None" correlation on port pair, you will not see NSH headers in the SF yes (they will be stripped before/restored after)12:29
bcafarelmangelm: https://docs.openstack.org/networking-sfc/latest/contributor/ietf_sfc_encapsulation.html has some details on these12:30
mangelmbcafarel, it seems like it is not possible to use correlation on port pair creation anyway:13:17
mangelmroot@opnfv:~# openstack sfc --insecure port pair create --ingress=${pClientMid} --egress=${pClientMid} ppClientM --service-function-parameters correlation=nsh13:17
mangelmInvalid input for service_function_parameters. Reason: '[{u'correlation': u'nsh'}]' is not a dictionary.13:17
mangelmNeutron server returns request_ids: ['req-e10cee9b-35dc-443b-b594-2cd4127dbeef']13:17
mangelmroot@opnfv:~#13:17
bcafarelmangelm: hmm ok that one I am pretty sure is fixed in python-neutronclient (current or queens)13:36
*** janki has joined #networking-sfc13:52
-openstackstatus- NOTICE: POST_FAILURE results on Tempest-based jobs since the most recent Zuul security fixes are being investigated; rechecking those won't help for now but we'll keep you posted once a solution is identified14:06
*** ChanServ changes topic to "POST_FAILURE results on Tempest-based jobs since the most recent Zuul security fixes are being investigated; rechecking those won't help for now but we'll keep you posted once a solution is identified"14:07
*** phuoc_ has joined #networking-sfc14:47
*** phuoc has quit IRC14:51
*** phuoc has joined #networking-sfc14:52
*** phuoc_ has quit IRC14:52
*** janki has quit IRC16:46
*** mangelm has quit IRC18:22
*** ChanServ changes topic to "Neutron Service Function Chaining (SFC) Extension discussions"19:22
-openstackstatus- NOTICE: The regression stemming from one of yesterday's Zuul security fixes has been rectified, and Devstack/Tempest jobs which encountered POST_FAILURE results over the past 24 hours can safely be rechecked now19:22

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