mir/ovs
2
0
Fork 0
mirror of https://github.com/openvswitch/ovs synced 2025-08-31 14:25:26 +00:00
Code Issues Releases Wiki Activity
Files
fb9aefa3c48a52c3799df5cb903e5b966b7ec5b3
ovs/utilities/automake.mk

127 lines
3.4 KiB
Makefile
Raw Normal View History

Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.
2009-07-08 13:19:16 -07:00
bin_PROGRAMS += \
utilities/ovs-appctl \
utilities/ovs-dpctl \
utilities/ovs-ofctl \
Build ovs-wdt or nlmon utilities only on Linux. These utilities are Linux-specific.
2010-05-26 10:25:19 -07:00
utilities/ovs-vsctl
leak-checker: Remove because it cannot be made thread-safe. The underlying glibc interface is deprecated because the interface itself is not thread-safe. That means that there's no way for a layer on top of it to be thread-safe. Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Ethan Jackson <ethan@nicira.com>
2013-04-23 14:52:41 -07:00
bin_SCRIPTS += utilities/ovs-pki
ofproto: Add "ofproto/trace" command to help debugging flow tables. With an appropriate flow table, output from a command like this: ovs-appctl ofproto/trace system@dp0 0 0 ffffffffffff000c29f49d5c080600010 80006040001000c29f49d5cac10008a000000000000ac1004df00000000000000000000000000000 0000000 resembles the following: Packet: -8:00:00.000000 00:0c:29:f4:9d:5c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x 0806), length 60: arp who-has 172.16.4.223 tell 172.16.0.138 Flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff type080 6 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 Rule: cookie=0 in_port=65534 OpenFlow actions=resubmit:1,mod_vlan_vid:5,resubmit:2,mod_vlan_pcp:6,strip_vlan Resubmitted flow: unchanged Rule: cookie=0 in_port=1 OpenFlow actions=resubmit:3,resubmit:4 Resubmitted flow: unchanged No match Resubmitted flow: unchanged No match Resubmitted flow: tunnel0:in_port0000:tci(vlan5,pcp0) mac00:0c:29:f4:9d: 5c->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 No match Final flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff t ype0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 Datapath actions: set_tci(vid=5,pcp=0),set_tci(vid=5,pcp=6),strip_vlan
2010-12-09 15:00:36 -08:00
if HAVE_PYTHON
utilities: Implement ovs-vlan-test script This patch implements a script which may be used to check for connectivity issues caused by bugs in Linux drivers relating to VLAN traffic.
2010-12-07 18:49:28 -08:00
bin_SCRIPTS += \
utilities: a top like tool for ovs-dpctl dump-flows. This python script summarizes ovs-dpctl dump-flows content by aggregating the number of packets, total bytes and occurrence of the following fields: - Datapath in_port - Ethernet type - Source and destination MAC addresses - IP protocol - Source and destination IPv4 addresses - Source and destination IPv6 addresses - UDP and TCP destination port - Tunnel source and destination addresses Testing included confirming both mega-flows and non-megaflows are properly parsed. Bit masks are applied in the case of mega-flows prior to aggregation. Test --script parameter which runs in non-interactive mode. Tested syntax against python 2.4.3, 2.6 and 2.7. Confirmed script passes pep8 and pylint run as: pylint --disable=I0011 --include-id=y --reports=n This tool has been added to these distribution: - add ovs-dpctl-top to debian distribution - add ovs-dpctl-top to rpm distribution. - add ovs-dpctl-top to XenServer RPM. Signed-off-by: Mark Hamilton <mhamilton@nicira.com> Signed-off-by: Gurucharan Shetty <gshetty@nicira.com>
2013-09-13 15:50:48 -07:00
utilities/ovs-dpctl-top \
ovs-l3ping: A new test utility that allows to detect L3 tunneling issues ovs-l3ping is similar to ovs-test, but the main difference is that it does not require administrator to open firewall holes for the XML/RPC control connection. This is achieved by encapsulating the Control Connection over the L3 tunnel itself. This tool is not intended as a replacement for ovs-test, because ovs-test covers much broader set of test cases. Sample usage: Node1: ovs-l3ping -s 192.168.122.236,10.1.1.1 -t gre Node2: ovs-l3ping -c 192.168.122.220,10.1.1.2,10.1.1.1 -t gre Issue#11791 Signed-off-by: Ansis Atteka <aatteka@nicira.com>
2012-06-28 15:52:40 -07:00
utilities/ovs-l3ping \
utilities: New helper ovs-parse-backtrace. The new ovs-parse-backtrace utility makes the output of ovs-appctl backtrace more human readable by removing duplicate traces and converting addresses to function names. Signed-off-by: Ethan Jackson <ethan@nicira.com>
2012-10-15 12:42:48 -07:00
utilities/ovs-parse-backtrace \
utilities: Implement ovs-vlan-test script This patch implements a script which may be used to check for connectivity issues caused by bugs in Linux drivers relating to VLAN traffic.
2010-12-07 18:49:28 -08:00
utilities/ovs-pcap \
utilities/ovs-tcpundump \
ovs-test: A new tool that allows to diagnose connectivity and performance issues This tool will be a replacement for the current ovs-vlan-test utility. Besides from connectivity issues it will also be able to detect performance related issues in Open vSwitch setups. Currently it uses UDP and TCP protocols for stressing. Issue #6976
2011-10-31 14:56:08 -07:00
utilities/ovs-test \
utilities: Implement ovs-vlan-test script This patch implements a script which may be used to check for connectivity issues caused by bugs in Linux drivers relating to VLAN traffic.
2010-12-07 18:49:28 -08:00
utilities/ovs-vlan-test
ofproto: Add "ofproto/trace" command to help debugging flow tables. With an appropriate flow table, output from a command like this: ovs-appctl ofproto/trace system@dp0 0 0 ffffffffffff000c29f49d5c080600010 80006040001000c29f49d5cac10008a000000000000ac1004df00000000000000000000000000000 0000000 resembles the following: Packet: -8:00:00.000000 00:0c:29:f4:9d:5c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x 0806), length 60: arp who-has 172.16.4.223 tell 172.16.0.138 Flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff type080 6 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 Rule: cookie=0 in_port=65534 OpenFlow actions=resubmit:1,mod_vlan_vid:5,resubmit:2,mod_vlan_pcp:6,strip_vlan Resubmitted flow: unchanged Rule: cookie=0 in_port=1 OpenFlow actions=resubmit:3,resubmit:4 Resubmitted flow: unchanged No match Resubmitted flow: unchanged No match Resubmitted flow: tunnel0:in_port0000:tci(vlan5,pcp0) mac00:0c:29:f4:9d: 5c->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 No match Final flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff t ype0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 Datapath actions: set_tci(vid=5,pcp=0),set_tci(vid=5,pcp=6),strip_vlan
2010-12-09 15:00:36 -08:00
endif
ovs-ctl: Make "force-reload-kmod" warn when DHCP clients must be restarted. This should make it more obvious when the admin needs to restart a DHCP client (or other daemon). Without this, unless the admin carefully reads the documentation, the first notice he gets about a need to restart the DHCP client can easily be when the lease expires and the machine drops off the network. Bug #5391. Tested-by: Gurucharan Shetty <gshetty@nicira.com> Suggested-by: Duffie Cooley <dcooley@nicira.com> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-05-01 15:36:44 -07:00
scripts_SCRIPTS += \
utilities/ovs-check-dead-ifs \
utilities/ovs-ctl \
utilities/ovs-save
utilites: rename ovs-lib.sh to ovs-lib Rename this helper script to simply ovs-lib, since it's primarily a library of helper functions. Signed-off-by: Chris Wright <chrisw@sous-sol.org> Signed-off-by: Ben Pfaff <blp@nicira.com>
2011-12-08 23:36:05 -08:00
scripts_DATA += utilities/ovs-lib
Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.
2009-07-08 13:19:16 -07:00
EXTRA_DIST += \
ovs-ctl: Make "force-reload-kmod" warn when DHCP clients must be restarted. This should make it more obvious when the admin needs to restart a DHCP client (or other daemon). Without this, unless the admin carefully reads the documentation, the first notice he gets about a need to restart the DHCP client can easily be when the lease expires and the machine drops off the network. Bug #5391. Tested-by: Gurucharan Shetty <gshetty@nicira.com> Suggested-by: Duffie Cooley <dcooley@nicira.com> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-05-01 15:36:44 -07:00
utilities/ovs-check-dead-ifs.in \
Implement automatic dependency generation for manpages. This ensures that manpages actually get rebuilt if any of the lib/*.man fragments that they depend upon are modified.
2011-10-26 16:06:37 -07:00
utilities/ovs-ctl.in \
utilities: New helper script ovs-dev.py. ovs-dev.py is a script I've written to help perform common tasks necessary for developing Open vSwitch. It allows a developer to configure, build, and run the switch with a minimum of effort or knowledge of the various idiosyncrasies involved. Signed-off-by: Ethan Jackson <ethan@nicira.com>
2013-07-06 18:55:45 -07:00
utilities/ovs-dev.py \
utilities: a top like tool for ovs-dpctl dump-flows. This python script summarizes ovs-dpctl dump-flows content by aggregating the number of packets, total bytes and occurrence of the following fields: - Datapath in_port - Ethernet type - Source and destination MAC addresses - IP protocol - Source and destination IPv4 addresses - Source and destination IPv6 addresses - UDP and TCP destination port - Tunnel source and destination addresses Testing included confirming both mega-flows and non-megaflows are properly parsed. Bit masks are applied in the case of mega-flows prior to aggregation. Test --script parameter which runs in non-interactive mode. Tested syntax against python 2.4.3, 2.6 and 2.7. Confirmed script passes pep8 and pylint run as: pylint --disable=I0011 --include-id=y --reports=n This tool has been added to these distribution: - add ovs-dpctl-top to debian distribution - add ovs-dpctl-top to rpm distribution. - add ovs-dpctl-top to XenServer RPM. Signed-off-by: Mark Hamilton <mhamilton@nicira.com> Signed-off-by: Gurucharan Shetty <gshetty@nicira.com>
2013-09-13 15:50:48 -07:00
utilities/ovs-dpctl-top.in \
ovs-l3ping: A new test utility that allows to detect L3 tunneling issues ovs-l3ping is similar to ovs-test, but the main difference is that it does not require administrator to open firewall holes for the XML/RPC control connection. This is achieved by encapsulating the Control Connection over the L3 tunnel itself. This tool is not intended as a replacement for ovs-test, because ovs-test covers much broader set of test cases. Sample usage: Node1: ovs-l3ping -s 192.168.122.236,10.1.1.1 -t gre Node2: ovs-l3ping -c 192.168.122.220,10.1.1.2,10.1.1.1 -t gre Issue#11791 Signed-off-by: Ansis Atteka <aatteka@nicira.com>
2012-06-28 15:52:40 -07:00
utilities/ovs-l3ping.in \
utilites: rename ovs-lib.sh to ovs-lib Rename this helper script to simply ovs-lib, since it's primarily a library of helper functions. Signed-off-by: Chris Wright <chrisw@sous-sol.org> Signed-off-by: Ben Pfaff <blp@nicira.com>
2011-12-08 23:36:05 -08:00
utilities/ovs-lib.in \
utilities: New helper ovs-parse-backtrace. The new ovs-parse-backtrace utility makes the output of ovs-appctl backtrace more human readable by removing duplicate traces and converting addresses to function names. Signed-off-by: Ethan Jackson <ethan@nicira.com>
2012-10-15 12:42:48 -07:00
utilities/ovs-parse-backtrace.in \
Implement automatic dependency generation for manpages. This ensures that manpages actually get rebuilt if any of the lib/*.man fragments that they depend upon are modified.
2011-10-26 16:06:37 -07:00
utilities/ovs-pcap.in \
utilities/ovs-pki.in \
utilities/ovs-save \
utilities/ovs-tcpundump.in \
ovs-test: A new tool that allows to diagnose connectivity and performance issues This tool will be a replacement for the current ovs-vlan-test utility. Besides from connectivity issues it will also be able to detect performance related issues in Open vSwitch setups. Currently it uses UDP and TCP protocols for stressing. Issue #6976
2011-10-31 14:56:08 -07:00
utilities/ovs-test.in \
Implement automatic dependency generation for manpages. This ensures that manpages actually get rebuilt if any of the lib/*.man fragments that they depend upon are modified.
2011-10-26 16:06:37 -07:00
utilities/ovs-vlan-test.in
MAN_ROOTS += \
Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.
2009-07-08 13:19:16 -07:00
utilities/ovs-appctl.8.in \
ovs-benchmark: New utility.
2011-07-27 16:23:06 -07:00
utilities/ovs-benchmark.1.in \
Implement automatic dependency generation for manpages. This ensures that manpages actually get rebuilt if any of the lib/*.man fragments that they depend upon are modified.
2011-10-26 16:06:37 -07:00
utilities/ovs-ctl.8 \
Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.
2009-07-08 13:19:16 -07:00
utilities/ovs-dpctl.8.in \
utilities: a top like tool for ovs-dpctl dump-flows. This python script summarizes ovs-dpctl dump-flows content by aggregating the number of packets, total bytes and occurrence of the following fields: - Datapath in_port - Ethernet type - Source and destination MAC addresses - IP protocol - Source and destination IPv4 addresses - Source and destination IPv6 addresses - UDP and TCP destination port - Tunnel source and destination addresses Testing included confirming both mega-flows and non-megaflows are properly parsed. Bit masks are applied in the case of mega-flows prior to aggregation. Test --script parameter which runs in non-interactive mode. Tested syntax against python 2.4.3, 2.6 and 2.7. Confirmed script passes pep8 and pylint run as: pylint --disable=I0011 --include-id=y --reports=n This tool has been added to these distribution: - add ovs-dpctl-top to debian distribution - add ovs-dpctl-top to rpm distribution. - add ovs-dpctl-top to XenServer RPM. Signed-off-by: Mark Hamilton <mhamilton@nicira.com> Signed-off-by: Gurucharan Shetty <gshetty@nicira.com>
2013-09-13 15:50:48 -07:00
utilities/ovs-dpctl-top.8.in \
ovs-l3ping: A new test utility that allows to detect L3 tunneling issues ovs-l3ping is similar to ovs-test, but the main difference is that it does not require administrator to open firewall holes for the XML/RPC control connection. This is achieved by encapsulating the Control Connection over the L3 tunnel itself. This tool is not intended as a replacement for ovs-test, because ovs-test covers much broader set of test cases. Sample usage: Node1: ovs-l3ping -s 192.168.122.236,10.1.1.1 -t gre Node2: ovs-l3ping -c 192.168.122.220,10.1.1.2,10.1.1.1 -t gre Issue#11791 Signed-off-by: Ansis Atteka <aatteka@nicira.com>
2012-06-28 15:52:40 -07:00
utilities/ovs-l3ping.8.in \
Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.
2009-07-08 13:19:16 -07:00
utilities/ovs-ofctl.8.in \
utilities: New helper ovs-parse-backtrace. The new ovs-parse-backtrace utility makes the output of ovs-appctl backtrace more human readable by removing duplicate traces and converting addresses to function names. Signed-off-by: Ethan Jackson <ethan@nicira.com>
2012-10-15 12:42:48 -07:00
utilities/ovs-parse-backtrace.8 \
ofproto: Add "ofproto/trace" command to help debugging flow tables. With an appropriate flow table, output from a command like this: ovs-appctl ofproto/trace system@dp0 0 0 ffffffffffff000c29f49d5c080600010 80006040001000c29f49d5cac10008a000000000000ac1004df00000000000000000000000000000 0000000 resembles the following: Packet: -8:00:00.000000 00:0c:29:f4:9d:5c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x 0806), length 60: arp who-has 172.16.4.223 tell 172.16.0.138 Flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff type080 6 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 Rule: cookie=0 in_port=65534 OpenFlow actions=resubmit:1,mod_vlan_vid:5,resubmit:2,mod_vlan_pcp:6,strip_vlan Resubmitted flow: unchanged Rule: cookie=0 in_port=1 OpenFlow actions=resubmit:3,resubmit:4 Resubmitted flow: unchanged No match Resubmitted flow: unchanged No match Resubmitted flow: tunnel0:in_port0000:tci(vlan5,pcp0) mac00:0c:29:f4:9d: 5c->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 No match Final flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff t ype0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 Datapath actions: set_tci(vid=5,pcp=0),set_tci(vid=5,pcp=6),strip_vlan
2010-12-09 15:00:36 -08:00
utilities/ovs-pcap.1.in \
Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.
2009-07-08 13:19:16 -07:00
utilities/ovs-pki.8.in \
ofproto: Add "ofproto/trace" command to help debugging flow tables. With an appropriate flow table, output from a command like this: ovs-appctl ofproto/trace system@dp0 0 0 ffffffffffff000c29f49d5c080600010 80006040001000c29f49d5cac10008a000000000000ac1004df00000000000000000000000000000 0000000 resembles the following: Packet: -8:00:00.000000 00:0c:29:f4:9d:5c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x 0806), length 60: arp who-has 172.16.4.223 tell 172.16.0.138 Flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff type080 6 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 Rule: cookie=0 in_port=65534 OpenFlow actions=resubmit:1,mod_vlan_vid:5,resubmit:2,mod_vlan_pcp:6,strip_vlan Resubmitted flow: unchanged Rule: cookie=0 in_port=1 OpenFlow actions=resubmit:3,resubmit:4 Resubmitted flow: unchanged No match Resubmitted flow: unchanged No match Resubmitted flow: tunnel0:in_port0000:tci(vlan5,pcp0) mac00:0c:29:f4:9d: 5c->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 No match Final flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff t ype0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 Datapath actions: set_tci(vid=5,pcp=0),set_tci(vid=5,pcp=6),strip_vlan
2010-12-09 15:00:36 -08:00
utilities/ovs-tcpundump.1.in \
Support vlan_group workaround implemented in XenServer kernels. Some Linux network drivers support a feature called "VLAN acceleration", associated with a data structure called a "vlan_group". A vlan_group is, abstractly, a dictionary that maps from a VLAN ID (in the range 0...4095) to a VLAN device, that is, a Linux network device associated with a particular VLAN, e.g. "eth0.9" for VLAN 9 on eth0. Some drivers that support VLAN acceleration have bugs that fall roughly into the following categories: * Some NICs strip VLAN tags on receive if no vlan_group is registered, so that the tag is completely lost. * Some drivers size their receive buffers based on whether a vlan_group is enabled, meaning that a maximum size packet with a VLAN tag will not fit if a vlan_group is not configured. * On transmit some drivers expect that VLAN acceleration will be used if it is available (which can only be done if a vlan_group is configured). In these cases, the driver may fail to parse the packet and correctly setup checksum offloading and/or TSO. The correct long term solution is to fix these driver bugs. To cope until then, we have prepared a patch to the Linux kernel network stack that works around these problems. This commit adds support for the workaround implemented by that patch. Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Jesse Gross <jesse@nicira.com>
2011-03-16 14:39:17 -07:00
utilities/ovs-vlan-bug-workaround.8.in \
ovs-test: A new tool that allows to diagnose connectivity and performance issues This tool will be a replacement for the current ovs-vlan-test utility. Besides from connectivity issues it will also be able to detect performance related issues in Open vSwitch setups. Currently it uses UDP and TCP protocols for stressing. Issue #6976
2011-10-31 14:56:08 -07:00
utilities/ovs-test.8.in \
utilities: Implement ovs-vlan-test script This patch implements a script which may be used to check for connectivity issues caused by bugs in Linux drivers relating to VLAN traffic.
2010-12-07 18:49:28 -08:00
utilities/ovs-vlan-test.8.in \
vsctl: Start making it work with ovsdb. This passes at least one test (the one named "add-br a"). It probably doesn't pass any more than that. This is *way* not up to my quality standards, but we are in a super hurry so I'm pushing it anyhow.
2009-12-08 17:18:12 -08:00
utilities/ovs-vsctl.8.in
docs: Add Makefile rule to check syntax of manpages. This should catch future nroff syntax errors immediately, instead of much later.
2011-08-24 10:45:32 -07:00
MAN_FRAGMENTS += utilities/ovs-vlan-bugs.man
Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.
2009-07-08 13:19:16 -07:00
DISTCLEANFILES += \
utilities/ovs-appctl.8 \
Refactor initscripts into distro-independent and distro-specific pieces. This should make it easier to add OVS support to new distributions.
2011-06-17 12:24:31 -07:00
utilities/ovs-ctl \
ovs-benchmark: New utility.
2011-07-27 16:23:06 -07:00
utilities/ovs-benchmark.1 \
Fix "make distcheck" failure since we weren't cleaning up a generated file. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-05-10 09:37:11 -07:00
utilities/ovs-check-dead-ifs \
Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.
2009-07-08 13:19:16 -07:00
utilities/ovs-dpctl.8 \
utilities: a top like tool for ovs-dpctl dump-flows. This python script summarizes ovs-dpctl dump-flows content by aggregating the number of packets, total bytes and occurrence of the following fields: - Datapath in_port - Ethernet type - Source and destination MAC addresses - IP protocol - Source and destination IPv4 addresses - Source and destination IPv6 addresses - UDP and TCP destination port - Tunnel source and destination addresses Testing included confirming both mega-flows and non-megaflows are properly parsed. Bit masks are applied in the case of mega-flows prior to aggregation. Test --script parameter which runs in non-interactive mode. Tested syntax against python 2.4.3, 2.6 and 2.7. Confirmed script passes pep8 and pylint run as: pylint --disable=I0011 --include-id=y --reports=n This tool has been added to these distribution: - add ovs-dpctl-top to debian distribution - add ovs-dpctl-top to rpm distribution. - add ovs-dpctl-top to XenServer RPM. Signed-off-by: Mark Hamilton <mhamilton@nicira.com> Signed-off-by: Gurucharan Shetty <gshetty@nicira.com>
2013-09-13 15:50:48 -07:00
utilities/ovs-dpctl-top \
utilities/ovs-dpctl-top.8 \
ovs-l3ping: A new test utility that allows to detect L3 tunneling issues ovs-l3ping is similar to ovs-test, but the main difference is that it does not require administrator to open firewall holes for the XML/RPC control connection. This is achieved by encapsulating the Control Connection over the L3 tunnel itself. This tool is not intended as a replacement for ovs-test, because ovs-test covers much broader set of test cases. Sample usage: Node1: ovs-l3ping -s 192.168.122.236,10.1.1.1 -t gre Node2: ovs-l3ping -c 192.168.122.220,10.1.1.2,10.1.1.1 -t gre Issue#11791 Signed-off-by: Ansis Atteka <aatteka@nicira.com>
2012-06-28 15:52:40 -07:00
utilities/ovs-l3ping \
utilities/ovs-l3ping.8 \
utilites: rename ovs-lib.sh to ovs-lib Rename this helper script to simply ovs-lib, since it's primarily a library of helper functions. Signed-off-by: Chris Wright <chrisw@sous-sol.org> Signed-off-by: Ben Pfaff <blp@nicira.com>
2011-12-08 23:36:05 -08:00
utilities/ovs-lib \
Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.
2009-07-08 13:19:16 -07:00
utilities/ovs-ofctl.8 \
utilities: New helper ovs-parse-backtrace. The new ovs-parse-backtrace utility makes the output of ovs-appctl backtrace more human readable by removing duplicate traces and converting addresses to function names. Signed-off-by: Ethan Jackson <ethan@nicira.com>
2012-10-15 12:42:48 -07:00
utilities/ovs-parse-backtrace \
ofproto: Add "ofproto/trace" command to help debugging flow tables. With an appropriate flow table, output from a command like this: ovs-appctl ofproto/trace system@dp0 0 0 ffffffffffff000c29f49d5c080600010 80006040001000c29f49d5cac10008a000000000000ac1004df00000000000000000000000000000 0000000 resembles the following: Packet: -8:00:00.000000 00:0c:29:f4:9d:5c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x 0806), length 60: arp who-has 172.16.4.223 tell 172.16.0.138 Flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff type080 6 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 Rule: cookie=0 in_port=65534 OpenFlow actions=resubmit:1,mod_vlan_vid:5,resubmit:2,mod_vlan_pcp:6,strip_vlan Resubmitted flow: unchanged Rule: cookie=0 in_port=1 OpenFlow actions=resubmit:3,resubmit:4 Resubmitted flow: unchanged No match Resubmitted flow: unchanged No match Resubmitted flow: tunnel0:in_port0000:tci(vlan5,pcp0) mac00:0c:29:f4:9d: 5c->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 No match Final flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff t ype0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 Datapath actions: set_tci(vid=5,pcp=0),set_tci(vid=5,pcp=6),strip_vlan
2010-12-09 15:00:36 -08:00
utilities/ovs-pcap \
utilities/ovs-pcap.1 \
Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.
2009-07-08 13:19:16 -07:00
utilities/ovs-pki \
utilities/ovs-pki.8 \
ofproto: Add "ofproto/trace" command to help debugging flow tables. With an appropriate flow table, output from a command like this: ovs-appctl ofproto/trace system@dp0 0 0 ffffffffffff000c29f49d5c080600010 80006040001000c29f49d5cac10008a000000000000ac1004df00000000000000000000000000000 0000000 resembles the following: Packet: -8:00:00.000000 00:0c:29:f4:9d:5c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x 0806), length 60: arp who-has 172.16.4.223 tell 172.16.0.138 Flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff type080 6 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 Rule: cookie=0 in_port=65534 OpenFlow actions=resubmit:1,mod_vlan_vid:5,resubmit:2,mod_vlan_pcp:6,strip_vlan Resubmitted flow: unchanged Rule: cookie=0 in_port=1 OpenFlow actions=resubmit:3,resubmit:4 Resubmitted flow: unchanged No match Resubmitted flow: unchanged No match Resubmitted flow: tunnel0:in_port0000:tci(vlan5,pcp0) mac00:0c:29:f4:9d: 5c->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 No match Final flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff t ype0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 Datapath actions: set_tci(vid=5,pcp=0),set_tci(vid=5,pcp=6),strip_vlan
2010-12-09 15:00:36 -08:00
utilities/ovs-tcpundump \
utilities/ovs-tcpundump.1 \
ovs-test: A new tool that allows to diagnose connectivity and performance issues This tool will be a replacement for the current ovs-vlan-test utility. Besides from connectivity issues it will also be able to detect performance related issues in Open vSwitch setups. Currently it uses UDP and TCP protocols for stressing. Issue #6976
2011-10-31 14:56:08 -07:00
utilities/ovs-test \
utilities/ovs-test.8 \
utilities: Implement ovs-vlan-test script This patch implements a script which may be used to check for connectivity issues caused by bugs in Linux drivers relating to VLAN traffic.
2010-12-07 18:49:28 -08:00
utilities/ovs-vlan-test \
utilities/ovs-vlan-test.8 \
utilities: Add ovs-vlan-bug-workaround to make distclean This was causing and error during make distcheck for me.
2011-03-22 18:55:53 -07:00
utilities/ovs-vlan-bug-workaround.8 \
New utility ovs-vsctl.
2009-09-14 10:05:13 -07:00
utilities/ovs-vsctl.8
Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.
2009-07-08 13:19:16 -07:00
man_MANS += \
utilities/ovs-appctl.8 \
ovs-benchmark: New utility.
2011-07-27 16:23:06 -07:00
utilities/ovs-benchmark.1 \
Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.
2009-07-08 13:19:16 -07:00
utilities/ovs-dpctl.8 \
utilities: a top like tool for ovs-dpctl dump-flows. This python script summarizes ovs-dpctl dump-flows content by aggregating the number of packets, total bytes and occurrence of the following fields: - Datapath in_port - Ethernet type - Source and destination MAC addresses - IP protocol - Source and destination IPv4 addresses - Source and destination IPv6 addresses - UDP and TCP destination port - Tunnel source and destination addresses Testing included confirming both mega-flows and non-megaflows are properly parsed. Bit masks are applied in the case of mega-flows prior to aggregation. Test --script parameter which runs in non-interactive mode. Tested syntax against python 2.4.3, 2.6 and 2.7. Confirmed script passes pep8 and pylint run as: pylint --disable=I0011 --include-id=y --reports=n This tool has been added to these distribution: - add ovs-dpctl-top to debian distribution - add ovs-dpctl-top to rpm distribution. - add ovs-dpctl-top to XenServer RPM. Signed-off-by: Mark Hamilton <mhamilton@nicira.com> Signed-off-by: Gurucharan Shetty <gshetty@nicira.com>
2013-09-13 15:50:48 -07:00
utilities/ovs-dpctl-top.8 \
ovs-l3ping: A new test utility that allows to detect L3 tunneling issues ovs-l3ping is similar to ovs-test, but the main difference is that it does not require administrator to open firewall holes for the XML/RPC control connection. This is achieved by encapsulating the Control Connection over the L3 tunnel itself. This tool is not intended as a replacement for ovs-test, because ovs-test covers much broader set of test cases. Sample usage: Node1: ovs-l3ping -s 192.168.122.236,10.1.1.1 -t gre Node2: ovs-l3ping -c 192.168.122.220,10.1.1.2,10.1.1.1 -t gre Issue#11791 Signed-off-by: Ansis Atteka <aatteka@nicira.com>
2012-06-28 15:52:40 -07:00
utilities/ovs-l3ping.8 \
Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.
2009-07-08 13:19:16 -07:00
utilities/ovs-ofctl.8 \
utilities: New helper ovs-parse-backtrace. The new ovs-parse-backtrace utility makes the output of ovs-appctl backtrace more human readable by removing duplicate traces and converting addresses to function names. Signed-off-by: Ethan Jackson <ethan@nicira.com>
2012-10-15 12:42:48 -07:00
utilities/ovs-parse-backtrace.8 \
ofproto: Add "ofproto/trace" command to help debugging flow tables. With an appropriate flow table, output from a command like this: ovs-appctl ofproto/trace system@dp0 0 0 ffffffffffff000c29f49d5c080600010 80006040001000c29f49d5cac10008a000000000000ac1004df00000000000000000000000000000 0000000 resembles the following: Packet: -8:00:00.000000 00:0c:29:f4:9d:5c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x 0806), length 60: arp who-has 172.16.4.223 tell 172.16.0.138 Flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff type080 6 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 Rule: cookie=0 in_port=65534 OpenFlow actions=resubmit:1,mod_vlan_vid:5,resubmit:2,mod_vlan_pcp:6,strip_vlan Resubmitted flow: unchanged Rule: cookie=0 in_port=1 OpenFlow actions=resubmit:3,resubmit:4 Resubmitted flow: unchanged No match Resubmitted flow: unchanged No match Resubmitted flow: tunnel0:in_port0000:tci(vlan5,pcp0) mac00:0c:29:f4:9d: 5c->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 No match Final flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff t ype0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 Datapath actions: set_tci(vid=5,pcp=0),set_tci(vid=5,pcp=6),strip_vlan
2010-12-09 15:00:36 -08:00
utilities/ovs-pcap.1 \
New utility ovs-vsctl.
2009-09-14 10:05:13 -07:00
utilities/ovs-pki.8 \
ofproto: Add "ofproto/trace" command to help debugging flow tables. With an appropriate flow table, output from a command like this: ovs-appctl ofproto/trace system@dp0 0 0 ffffffffffff000c29f49d5c080600010 80006040001000c29f49d5cac10008a000000000000ac1004df00000000000000000000000000000 0000000 resembles the following: Packet: -8:00:00.000000 00:0c:29:f4:9d:5c > ff:ff:ff:ff:ff:ff, ethertype ARP (0x 0806), length 60: arp who-has 172.16.4.223 tell 172.16.0.138 Flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff type080 6 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 Rule: cookie=0 in_port=65534 OpenFlow actions=resubmit:1,mod_vlan_vid:5,resubmit:2,mod_vlan_pcp:6,strip_vlan Resubmitted flow: unchanged Rule: cookie=0 in_port=1 OpenFlow actions=resubmit:3,resubmit:4 Resubmitted flow: unchanged No match Resubmitted flow: unchanged No match Resubmitted flow: tunnel0:in_port0000:tci(vlan5,pcp0) mac00:0c:29:f4:9d: 5c->ff:ff:ff:ff:ff:ff type0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 No match Final flow: tunnel0:in_port0000:tci(0) mac00:0c:29:f4:9d:5c->ff:ff:ff:ff:ff:ff t ype0806 proto1 tos0 ip172.16.0.138->172.16.4.223 port0->0 Datapath actions: set_tci(vid=5,pcp=0),set_tci(vid=5,pcp=6),strip_vlan
2010-12-09 15:00:36 -08:00
utilities/ovs-tcpundump.1 \
utilities: Fix typo in makefile that caused RPM build failure. I tested this against our autobuilder and it passed.
2011-03-16 15:45:25 -07:00
utilities/ovs-vlan-bug-workaround.8 \
ovs-test: A new tool that allows to diagnose connectivity and performance issues This tool will be a replacement for the current ovs-vlan-test utility. Besides from connectivity issues it will also be able to detect performance related issues in Open vSwitch setups. Currently it uses UDP and TCP protocols for stressing. Issue #6976
2011-10-31 14:56:08 -07:00
utilities/ovs-test.8 \
utilities: Implement ovs-vlan-test script This patch implements a script which may be used to check for connectivity issues caused by bugs in Linux drivers relating to VLAN traffic.
2010-12-07 18:49:28 -08:00
utilities/ovs-vlan-test.8 \
New utility ovs-vsctl.
2009-09-14 10:05:13 -07:00
utilities/ovs-vsctl.8
Refactor initscripts into distro-independent and distro-specific pieces. This should make it easier to add OVS support to new distributions.
2011-06-17 12:24:31 -07:00
dist_man_MANS += utilities/ovs-ctl.8
Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.
2009-07-08 13:19:16 -07:00
utilities_ovs_appctl_SOURCES = utilities/ovs-appctl.c
unixctl: New JSON RPC back-end. The unixctl library had used the vde2 management protocol since the early days of Open vSwitch. As Open vSwitch has matured, several Python daemons have been added to the code base which would benefit from a unixctl implementations. Instead of implementing the old unixctl protocol in Python, this patch changes unixctl to use JSON RPC for which we already have an implementation in both Python and C. Future patches will need to implement a unixctl library in Python on top of JSON RPC. Signed-off-by: Ethan Jackson <ethan@nicira.com>
2012-02-14 20:53:59 -08:00
utilities_ovs_appctl_LDADD = lib/libopenvswitch.a $(SSL_LIBS)
Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.
2009-07-08 13:19:16 -07:00
utilities_ovs_dpctl_SOURCES = utilities/ovs-dpctl.c
unixctl: New JSON RPC back-end. The unixctl library had used the vde2 management protocol since the early days of Open vSwitch. As Open vSwitch has matured, several Python daemons have been added to the code base which would benefit from a unixctl implementations. Instead of implementing the old unixctl protocol in Python, this patch changes unixctl to use JSON RPC for which we already have an implementation in both Python and C. Future patches will need to implement a unixctl library in Python on top of JSON RPC. Signed-off-by: Ethan Jackson <ethan@nicira.com>
2012-02-14 20:53:59 -08:00
utilities_ovs_dpctl_LDADD = lib/libopenvswitch.a $(SSL_LIBS)
Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.
2009-07-08 13:19:16 -07:00
utilities_ovs_ofctl_SOURCES = utilities/ovs-ofctl.c
ofproto: Improve abstraction by adding function ofproto_parse_name(). This means that ovs-ofctl and ovs-openflowd don't have to use the dpif layer at all, making it easier to change the ofproto implementation.
2011-04-11 15:08:19 -07:00
utilities_ovs_ofctl_LDADD = \
ofproto/libofproto.a \
lib/libopenvswitch.a \
$(SSL_LIBS)
Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.
2009-07-08 13:19:16 -07:00
idl: Move vswitch-idl to libopenvswitch. This is cleaner then having multiple programs build the idl independently. Signed-off-by: Ethan Jackson <ethan@nicira.com>
2012-03-15 17:10:41 -07:00
utilities_ovs_vsctl_SOURCES = utilities/ovs-vsctl.c
Remove PCRE dependency.
2010-02-23 15:48:28 -08:00
utilities_ovs_vsctl_LDADD = lib/libopenvswitch.a $(SSL_LIBS)
vsctl: Start making it work with ovsdb. This passes at least one test (the one named "add-br a"). It probably doesn't pass any more than that. This is *way* not up to my quality standards, but we are in a super hurry so I'm pushing it anyhow.
2009-12-08 17:18:12 -08:00
config: Add explicit support for building on ESX. The ESX userspace looks quite a bit like linux, but has some key differences which need to be specially handled in the build. To distinguish between ESX and systems which use the linux datapath module, this patch adds two new macros "ESX" and "LINUX_DATAPATH". It uses these macros to disable building code on ESX which only applies to a true Linux environment. In addition, it adds a new route-table-stub implementation which is required for the build to complete successfully on ESX. Signed-off-by: Ethan Jackson <ethan@nicira.com>
2012-10-05 13:24:21 -07:00
if LINUX_DATAPATH
Support vlan_group workaround implemented in XenServer kernels. Some Linux network drivers support a feature called "VLAN acceleration", associated with a data structure called a "vlan_group". A vlan_group is, abstractly, a dictionary that maps from a VLAN ID (in the range 0...4095) to a VLAN device, that is, a Linux network device associated with a particular VLAN, e.g. "eth0.9" for VLAN 9 on eth0. Some drivers that support VLAN acceleration have bugs that fall roughly into the following categories: * Some NICs strip VLAN tags on receive if no vlan_group is registered, so that the tag is completely lost. * Some drivers size their receive buffers based on whether a vlan_group is enabled, meaning that a maximum size packet with a VLAN tag will not fit if a vlan_group is not configured. * On transmit some drivers expect that VLAN acceleration will be used if it is available (which can only be done if a vlan_group is configured). In these cases, the driver may fail to parse the packet and correctly setup checksum offloading and/or TSO. The correct long term solution is to fix these driver bugs. To cope until then, we have prepared a patch to the Linux kernel network stack that works around these problems. This commit adds support for the workaround implemented by that patch. Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Jesse Gross <jesse@nicira.com>
2011-03-16 14:39:17 -07:00
sbin_PROGRAMS += utilities/ovs-vlan-bug-workaround
utilities_ovs_vlan_bug_workaround_SOURCES = utilities/ovs-vlan-bug-workaround.c
unixctl: New JSON RPC back-end. The unixctl library had used the vde2 management protocol since the early days of Open vSwitch. As Open vSwitch has matured, several Python daemons have been added to the code base which would benefit from a unixctl implementations. Instead of implementing the old unixctl protocol in Python, this patch changes unixctl to use JSON RPC for which we already have an implementation in both Python and C. Future patches will need to implement a unixctl library in Python on top of JSON RPC. Signed-off-by: Ethan Jackson <ethan@nicira.com>
2012-02-14 20:53:59 -08:00
utilities_ovs_vlan_bug_workaround_LDADD = lib/libopenvswitch.a $(SSL_LIBS)
Support vlan_group workaround implemented in XenServer kernels. Some Linux network drivers support a feature called "VLAN acceleration", associated with a data structure called a "vlan_group". A vlan_group is, abstractly, a dictionary that maps from a VLAN ID (in the range 0...4095) to a VLAN device, that is, a Linux network device associated with a particular VLAN, e.g. "eth0.9" for VLAN 9 on eth0. Some drivers that support VLAN acceleration have bugs that fall roughly into the following categories: * Some NICs strip VLAN tags on receive if no vlan_group is registered, so that the tag is completely lost. * Some drivers size their receive buffers based on whether a vlan_group is enabled, meaning that a maximum size packet with a VLAN tag will not fit if a vlan_group is not configured. * On transmit some drivers expect that VLAN acceleration will be used if it is available (which can only be done if a vlan_group is configured). In these cases, the driver may fail to parse the packet and correctly setup checksum offloading and/or TSO. The correct long term solution is to fix these driver bugs. To cope until then, we have prepared a patch to the Linux kernel network stack that works around these problems. This commit adds support for the workaround implemented by that patch. Signed-off-by: Ben Pfaff <blp@nicira.com> Acked-by: Jesse Gross <jesse@nicira.com>
2011-03-16 14:39:17 -07:00
Build ovs-wdt or nlmon utilities only on Linux. These utilities are Linux-specific.
2010-05-26 10:25:19 -07:00
noinst_PROGRAMS += utilities/nlmon
Import from old repository commit 61ef2b42a9c4ba8e1600f15bb0236765edc2ad45.
2009-07-08 13:19:16 -07:00
utilities_nlmon_SOURCES = utilities/nlmon.c
unixctl: New JSON RPC back-end. The unixctl library had used the vde2 management protocol since the early days of Open vSwitch. As Open vSwitch has matured, several Python daemons have been added to the code base which would benefit from a unixctl implementations. Instead of implementing the old unixctl protocol in Python, this patch changes unixctl to use JSON RPC for which we already have an implementation in both Python and C. Future patches will need to implement a unixctl library in Python on top of JSON RPC. Signed-off-by: Ethan Jackson <ethan@nicira.com>
2012-02-14 20:53:59 -08:00
utilities_nlmon_LDADD = lib/libopenvswitch.a $(SSL_LIBS)
Build ovs-wdt or nlmon utilities only on Linux. These utilities are Linux-specific.
2010-05-26 10:25:19 -07:00
endif
ovs-bugtool: Add plugins previously used only under XenServer. All of the xen-bugtool plugins that OVS has previously installed only under XenServer are equally useful with Debian and other distributions, so this commit installs and uses them everywhere.
2011-07-06 10:43:03 -07:00
ovs-benchmark: New utility.
2011-07-27 16:23:06 -07:00
bin_PROGRAMS += utilities/ovs-benchmark
utilities_ovs_benchmark_SOURCES = utilities/ovs-benchmark.c
unixctl: New JSON RPC back-end. The unixctl library had used the vde2 management protocol since the early days of Open vSwitch. As Open vSwitch has matured, several Python daemons have been added to the code base which would benefit from a unixctl implementations. Instead of implementing the old unixctl protocol in Python, this patch changes unixctl to use JSON RPC for which we already have an implementation in both Python and C. Future patches will need to implement a unixctl library in Python on top of JSON RPC. Signed-off-by: Ethan Jackson <ethan@nicira.com>
2012-02-14 20:53:59 -08:00
utilities_ovs_benchmark_LDADD = lib/libopenvswitch.a $(SSL_LIBS)
ovs-benchmark: New utility.
2011-07-27 16:23:06 -07:00
ovs-bugtool: Add plugins previously used only under XenServer. All of the xen-bugtool plugins that OVS has previously installed only under XenServer are equally useful with Debian and other distributions, so this commit installs and uses them everywhere.
2011-07-06 10:43:03 -07:00
include utilities/bugtool/automake.mk
Reference in New Issue Copy Permalink