https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/SFC-160 sfc <p>Honeycomb and VPP have some changes to support plugin infrastructure, so ODL SFC VPP renderer has to adapt to these changes in order that it can work correctly.</p> <p>Honeycomb and VPP were not ready for integration test when SFC VPP renderer was merged.</p> <p>This bug is blocking issue, it can't work if it isn't fixed.</p> <p>Operating System: All<br/> Platform: All</p> SFC-160

SFC VPP Renderer can't work with Honeycomb and VPP

Bug Resolved Done Yi Yang Yi Yang Tue, 6 Sep 2016 10:21:18 +0000 Thu, 19 Oct 2017 16:58:58 +0000 Thu, 8 Sep 2016 02:42:47 +0000 unspecified General 0 2 <p>Once a patch to stable/boron available, please help us analyze the footprint of the patch. To better assess the impact of this bug and fix, could someone from your team please help us identify the following:<br/> Severity: Could you elaborate on the severity of this bug? Is this a BLOCKER such that we cannot release Boron without it? Is there a workaround such that we can write a release note and fix in future Boron SR1?<br/> Testing: Could you also elaborate on the testing of this patch? How extensively has this patch been tested? Is it covered by any unit tests or system tests? <br/> Impact: Does this fix impact any dependent projects?</p> <p><a href="https://git.opendaylight.org/gerrit/45283" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/45283</a> will fix this issue.</p> <p>patch size:</p> <p> java/org/opendaylight/sfc/sfc_vpp_renderer/renderer/VppNodeManager.java | 9<br/> java/org/opendaylight/sfc/sfc_vpp_renderer/renderer/VppRspProcessor.java | 157 +++++-----<br/> yang/v3po.yang | 117 +++++++<br/> yang/vpp-nsh.yang | 48 +--<br/> 4 files changed, 236 insertions<img class="emoticon" src="https://jira.opendaylight.org/images/icons/emoticons/add.png" height="16" width="16" align="absmiddle" alt="" border="0"/>, 95 deletions<img class="emoticon" src="https://jira.opendaylight.org/images/icons/emoticons/forbidden.png" height="16" width="16" align="absmiddle" alt="" border="0"/></p> <p>Fixed with these patches:</p> <p>master<br/> <a href="https://git.opendaylight.org/gerrit/45284" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/45284</a></p> <p>stable/boron<br/> <a href="https://git.opendaylight.org/gerrit/45283" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/45283</a></p> <p>I think it is difficult for jenkins to test SFC VPP Renderer, this needs Honeycomb and VPP. GBP(groupbasedpolicy) also integrate Honeycomb and VPP, maybe Vladimor or Keith can provide help for this.</p> <p>My integration test:</p> <p>1. Start 6 VMs: classifier1, SFF1(VPP1), SF1, SFF2(VPP2), SF2, classifier2.<br/> classifier1 and classifier2 run my ovs-dpdk (<a href="https://github.com/yyang13/ovs_nsh_patches" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/yyang13/ovs_nsh_patches</a>), they will act as classifier to encapsulate and decapsulate VxLAN-gpe+NSH. Here are br-int info.</p> <p>f13fc1c6-0ffd-417f-855b-20ce88bdcb4e<br/> Bridge br-int<br/> Port "vxlangpe0"<br/> Interface "vxlangpe0"<br/> type: vxlan<br/> options: </p> {dst_port="4790", exts=gpe, key=flow, remote_ip=flow} <p> Port br-int<br/> Interface br-int<br/> type: internal<br/> Port "vxlan0"<br/> Interface "vxlan0"<br/> type: vxlan<br/> options: </p> {key=flow, remote_ip=flow} <p> Port "dpdk0"<br/> Interface "dpdk0"<br/> type: dpdk<br/> Port veth-br<br/> Interface veth-br</p> <p>2. SFF1(VPP1) and SFF2(VPP2) will run vpp and honeycomb, nsh_sfc must be installed as plugin.</p> <p>sudo start vpp<br/> sudo sh ./nsh/minimal-distribution/target/minimal-distribution-1.16.12-SNAPSHOT-hc/minimal-distribution-1.16.12-SNAPSHOT/honeycomb</p> <p>3. Run NSH-aware SF in SF1 and SF2<br/> sudo ifconfig eth2 &lt;SFIP&gt; netmask 255.255.255.0 up<br/> sudo python ./vxlan_tool.py -i eth2 --do=forward -v on<br/> <a href="https://git.opendaylight.org/gerrit/gitweb?p=sfc.git;a=blob;f=sfc-test/nsh-tools/vxlan_tool.py;h=d7b75316f0e29c1dc09ec63b17a054c2fcdf20af;hb=HEAD" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/gitweb?p=sfc.git;a=blob;f=sfc-test/nsh-tools/vxlan_tool.py;h=d7b75316f0e29c1dc09ec63b17a054c2fcdf20af;hb=HEAD</a> is vxlan_tool.py from sfc project.</p> <p>4. Run SFC in the host VMs's running and install the below features:<br/> feature:install odl-sfc-vpp-renderer<br/> feature:install odl-sfc-ui</p> <p>5. Add SFs, SFFs, SFC, SFP and RSP</p> <p>PUT <a href="http://10.240.224.185:8181/restconf/config/service-function:service-functions" class="external-link" target="_blank" rel="nofollow noopener">http://10.240.224.185:8181/restconf/config/service-function:service-functions</a></p> <p>{<br/> "service-functions": {<br/> "service-function": [<br/> {<br/> "name": "firewall1-vpp1",<br/> "type": "service-function-type:firewall",<br/> "sf-data-plane-locator": [</p> { "name": "eth0-11", "ip": "192.168.20.10", "port": 4790, "service-function-forwarder": "SFF1-VPP1", "transport": "service-locator:vxlan-gpe" } <p> ],<br/> "nsh-aware": true,<br/> "ip-mgmt-address": "192.168.20.10"<br/> },<br/> {<br/> "name": "dpi2-vpp2",<br/> "type": "service-function-type:dpi",<br/> "sf-data-plane-locator": [</p> { "name": "eth0-12", "ip": "192.168.20.13", "port": 4790, "service-function-forwarder": "SFF2-VPP2", "transport": "service-locator:vxlan-gpe" } <p> ],<br/> "nsh-aware": true,<br/> "ip-mgmt-address": "192.168.20.13"<br/> }<br/> ]<br/> }<br/> }</p> <p>PUT <a href="http://10.240.224.185:8181/restconf/config/service-function-forwarder:service-function-forwarders" class="external-link" target="_blank" rel="nofollow noopener">http://10.240.224.185:8181/restconf/config/service-function-forwarder:service-function-forwarders</a></p> <p>{<br/> "service-function-forwarders": {<br/> "service-function-forwarder": [<br/> {<br/> "name": "SFF1-VPP1",<br/> "ip-mgmt-address": "192.168.10.11",<br/> "service-function-dictionary": [<br/> {<br/> "name": "firewall1-vpp1",<br/> "sff-sf-data-plane-locator": </p> { "sf-dpl-name": "eth0-11", "sff-dpl-name": "vxlangpe-11" } <p> }<br/> ],<br/> "service-function-forwarder-vpp:sff-netconf-node-type": "netconf-node-type-honeycomb",</p> <p> "sff-data-plane-locator": [<br/> {<br/> "name": "vxlangpe-11",<br/> "data-plane-locator": </p> { "transport": "service-locator:vxlan-gpe", "port": 4790, "ip": "192.168.20.11" } <p> }<br/> ]<br/> },<br/> {<br/> "name": "SFF2-VPP2",<br/> "ip-mgmt-address": "192.168.10.12",<br/> "service-function-dictionary": [<br/> {<br/> "name": "dpi2-vpp2",<br/> "sff-sf-data-plane-locator": </p> { "sf-dpl-name": "eth0-12", "sff-dpl-name": "vxlangpe-12" } <p> }<br/> ],<br/> "service-function-forwarder-vpp:sff-netconf-node-type": "netconf-node-type-honeycomb",</p> <p> "sff-data-plane-locator": [<br/> {<br/> "name": "vxlangpe-12",<br/> "data-plane-locator": </p> { "transport": "service-locator:vxlan-gpe", "port": 4790, "ip": "192.168.20.12" } <p> }<br/> ]<br/> }<br/> ]<br/> }<br/> }</p> <p>PUT <a href="http://10.240.224.185:8181/restconf/config/service-function-chain:service-function-chains/" class="external-link" target="_blank" rel="nofollow noopener">http://10.240.224.185:8181/restconf/config/service-function-chain:service-function-chains/</a></p> <p>{<br/> "service-function-chains": {<br/> "service-function-chain": [<br/> {<br/> "name": "SFCVPP",<br/> "symmetric": "true",<br/> "sfc-service-function": [<br/> </p> { "name": "firewall-abstract1", "type": "service-function-type:firewall" } <p>,</p> { "name": "dpi-abstract1", "type": "service-function-type:dpi" } <p> ]<br/> }<br/> ]<br/> }<br/> }</p> <p>PUT <a href="http://10.240.224.185:8181/restconf/config/service-function-path:service-function-paths/" class="external-link" target="_blank" rel="nofollow noopener">http://10.240.224.185:8181/restconf/config/service-function-path:service-function-paths/</a></p> <p>{<br/> "service-function-paths": {<br/> "service-function-path": [</p> { "name": "SFCVPP-Path", "service-chain-name": "SFCVPP", "starting-index": 255, "symmetric": "true" } <p> ]<br/> }<br/> }</p> <p>PUT <a href="http://10.240.224.185:8181/restconf/operations/rendered-service-path:create-rendered-path/" class="external-link" target="_blank" rel="nofollow noopener">http://10.240.224.185:8181/restconf/operations/rendered-service-path:create-rendered-path/</a></p> <p>{<br/> "input": </p> { "name": "SFCVPP-RSP1", "parent-service-function-path": "SFCVPP-Path", "symmetric": "true" } <p>}</p> <p>6. By far, SFC Renderer has successfully created vxlan-gpe ports, nsh entries and nsh maps for SFF1(VPP1) and SFF2(VPP2).</p> <p>vagrant@vpp1:~/honeycomb$ sudo vppctl show vxlan-gpe<br/> <span class="error">&#91;0&#93;</span> local: 192.168.20.11 remote: 192.168.20.10 vxlan VNI 0 next-protocol nsh fibs: (encap 0, decap 0)<br/> <span class="error">&#91;1&#93;</span> local: 192.168.20.11 remote: 192.168.20.12 vxlan VNI 0 next-protocol nsh fibs: (encap 0, decap 0)<br/> <span class="error">&#91;2&#93;</span> local: 192.168.20.11 remote: 192.168.20.9 vxlan VNI 0 next-protocol nsh fibs: (encap 0, decap 0)<br/> vl_client_get_first_plugin_msg_id:266: plugin 'export_eb694f98' not registered<br/> vagrant@vpp1:~/honeycomb$ sudo vppctl show nsh entry<br/> nsh ver 0 len 6 (24 bytes) md_type 1 next_protocol 3<br/> service path 4 service index 255<br/> c1 0 c2 0 c3 0 c4 0<br/> nsh ver 0 len 6 (24 bytes) md_type 1 next_protocol 3<br/> service path 4 service index 254<br/> c1 0 c2 0 c3 0 c4 0<br/> nsh ver 0 len 6 (24 bytes) md_type 1 next_protocol 3<br/> service path 8388612 service index 254<br/> c1 0 c2 0 c3 0 c4 0<br/> nsh ver 0 len 6 (24 bytes) md_type 1 next_protocol 3<br/> service path 8388612 service index 253<br/> c1 0 c2 0 c3 0 c4 0<br/> vl_client_get_first_plugin_msg_id:266: plugin 'export_eb694f98' not registered<br/> vagrant@vpp1:~/honeycomb$ sudo vppctl show nsh map<br/> nsh entry nsp: 4 nsi: 255 maps to nsp: 4 nsi: 255 encapped by VXLAN GPE intf: 3<br/> nsh entry nsp: 4 nsi: 254 maps to nsp: 4 nsi: 254 encapped by VXLAN GPE intf: 4<br/> nsh entry nsp: 8388612 nsi: 254 maps to nsp: 8388612 nsi: 254 encapped by VXLAN GPE intf: 3<br/> nsh entry nsp: 8388612 nsi: 253 maps to nsp: 8388612 nsi: 253 encapped by VXLAN GPE intf: 5<br/> vl_client_get_first_plugin_msg_id:266: plugin 'export_eb694f98' not registered<br/> vagrant@vpp1:~/honeycomb$</p> <p>vagrant@vpp2:~$ sudo vppctl show vxlan-gpe<br/> <span class="error">&#91;0&#93;</span> local: 192.168.20.12 remote: 192.168.20.13 vxlan VNI 0 next-protocol nsh fibs: (encap 0, decap 0)<br/> <span class="error">&#91;1&#93;</span> local: 192.168.20.12 remote: 192.168.20.14 vxlan VNI 0 next-protocol nsh fibs: (encap 0, decap 0)<br/> <span class="error">&#91;2&#93;</span> local: 192.168.20.12 remote: 192.168.20.11 vxlan VNI 0 next-protocol nsh fibs: (encap 0, decap 0)<br/> vl_client_get_first_plugin_msg_id:266: plugin 'export_eb694f98' not registered<br/> vagrant@vpp2:~$ sudo vppctl show nsh entry<br/> nsh ver 0 len 6 (24 bytes) md_type 1 next_protocol 3<br/> service path 4 service index 254<br/> c1 0 c2 0 c3 0 c4 0<br/> nsh ver 0 len 6 (24 bytes) md_type 1 next_protocol 3<br/> service path 4 service index 253<br/> c1 0 c2 0 c3 0 c4 0<br/> nsh ver 0 len 6 (24 bytes) md_type 1 next_protocol 3<br/> service path 8388612 service index 255<br/> c1 0 c2 0 c3 0 c4 0<br/> nsh ver 0 len 6 (24 bytes) md_type 1 next_protocol 3<br/> service path 8388612 service index 254<br/> c1 0 c2 0 c3 0 c4 0<br/> vl_client_get_first_plugin_msg_id:266: plugin 'export_eb694f98' not registered<br/> vagrant@vpp2:~$ sudo vppctl show nsh map<br/> nsh entry nsp: 4 nsi: 254 maps to nsp: 4 nsi: 254 encapped by VXLAN GPE intf: 3<br/> nsh entry nsp: 4 nsi: 253 maps to nsp: 4 nsi: 253 encapped by VXLAN GPE intf: 4<br/> nsh entry nsp: 8388612 nsi: 255 maps to nsp: 8388612 nsi: 255 encapped by VXLAN GPE intf: 3<br/> nsh entry nsp: 8388612 nsi: 254 maps to nsp: 8388612 nsi: 254 encapped by VXLAN GPE intf: 5<br/> vl_client_get_first_plugin_msg_id:266: plugin 'export_eb694f98' not registered<br/> vagrant@vpp2:~$</p> <p>7. Now we can ping and wget namespace in host2.</p> <p>vagrant@host1:~$ sudo ip netns exec app ping 10.0.100.14<br/> PING 10.0.100.14 (10.0.100.14) 56(84) bytes of data.<br/> 64 bytes from 10.0.100.14: icmp_seq=1 ttl=64 time=3.98 ms<br/> 64 bytes from 10.0.100.14: icmp_seq=2 ttl=64 time=4.63 ms<br/> 64 bytes from 10.0.100.14: icmp_seq=3 ttl=64 time=4.12 ms<br/> 64 bytes from 10.0.100.14: icmp_seq=4 ttl=64 time=4.38 ms<br/> 64 bytes from 10.0.100.14: icmp_seq=5 ttl=64 time=4.19 ms<br/> ^C<br/> &#8212; 10.0.100.14 ping statistics &#8212;<br/> 5 packets transmitted, 5 received, 0% packet loss, time 4017ms<br/> rtt min/avg/max/mdev = 3.984/4.264/4.632/0.223 ms<br/> vagrant@host1:~$</p> <p>vagrant@host1:~$ sudo ip netns exec app wget <a href="http://10.0.100.14/" class="external-link" target="_blank" rel="nofollow noopener">http://10.0.100.14/</a><br/> -<del>2016-09-07 02:13:38</del>- <a href="http://10.0.100.14/" class="external-link" target="_blank" rel="nofollow noopener">http://10.0.100.14/</a><br/> Connecting to 10.0.100.14:80... connected.<br/> HTTP request sent, awaiting response... 200 OK<br/> Length: 1677 (1.6K) <span class="error">&#91;text/html&#93;</span><br/> Saving to: ‘index.html’</p> <p>100%<span class="error">&#91;=====================================&gt;&#93;</span> 1,677 --.-K/s in 0.02s</p> <p>2016-09-07 02:13:38 (89.1 KB/s) - ‘index.html’ saved <span class="error">&#91;1677/1677&#93;</span></p> <p>vagrant@host1:~$</p> <p>Test network topology</p> <p>Attachment ScreenHunter_03 Sep. 07 15.41.gif has been added with description: Test network topology</p> <p>(In reply to A H from comment #1)<br/> &gt; Once a patch to stable/boron available, please help us analyze the footprint<br/> &gt; of the patch. To better assess the impact of this bug and fix, could<br/> &gt; someone from your team please help us identify the following:<br/> &gt; Severity: Could you elaborate on the severity of this bug? Is this a<br/> &gt; BLOCKER such that we cannot release Boron without it? Is there a workaround<br/> &gt; such that we can write a release note and fix in future Boron SR1?<br/> &gt; Testing: Could you also elaborate on the testing of this patch? How<br/> &gt; extensively has this patch been tested? Is it covered by any unit tests or<br/> &gt; system tests? <br/> &gt; Impact: Does this fix impact any dependent projects?</p> <p>Severity: Yes it’s a blocker. No known workaround. Cannot delay to SR1. Without this patch, the functionality will NOT work.</p> <p>Testing: Yes we tested the patch and it was verified. Unfortunately, no unit tests/system tests yet. See comment 5 for details about the testing: <a href="https://bugs.opendaylight.org/show_bug.cgi?id=6640#c5" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=6640#c5</a></p> <p>Impact: No impact to any dependent projects.</p> <p>Has this bug been verified as fixed in the latest Boron RC 3.1 Build?</p> <p>(In reply to A H from comment #8)<br/> &gt; Has this bug been verified as fixed in the latest Boron RC 3.1 Build?</p> <p>Where can I get this RC3.1 Build?</p> <p>(In reply to A H from comment #8)<br/> &gt; Has this bug been verified as fixed in the latest Boron RC 3.1 Build?</p> <p>An, I think this one <a href="https://nexus.opendaylight.org/content/repositories/autorelease-1477/org/opendaylight/integration/distribution-karaf/0.5.0-Boron/distribution-karaf-0.5.0-Boron.tar.gz" class="external-link" target="_blank" rel="nofollow noopener">https://nexus.opendaylight.org/content/repositories/autorelease-1477/org/opendaylight/integration/distribution-karaf/0.5.0-Boron/distribution-karaf-0.5.0-Boron.tar.gz</a> should be what I need to verify.</p> <p>I verified it, it worked as expected, so I confirm this bug is fixed in Boron RC 3.1 build.</p> Development External issue ID 6640 External issue URL Issue Type ODL SR Target Milestone Priority Rank 0|i02ffb: