mir/ovs
2
0
Fork 0
mirror of https://github.com/openvswitch/ovs synced 2025-08-22 09:58:01 +00:00
Code Issues Releases Wiki Activity
ovs/python/automake.mk

71 lines
2.1 KiB
Makefile
Raw Normal View History

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
ovstest_pyfiles = \
python/ovstest/__init__.py \
python/ovstest/args.py \
python/ovstest/rpcserver.py \
python/ovstest/tcp.py \
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
python/ovstest/tests.py \
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
python/ovstest/udp.py \
ovs-test: Enhancements to the ovs-test tool -Implemented support for ovs-test client, so that it could automatically spawn an ovs-test server process from itself. This reduces the number of commands the user have to type to get tests running. -Automated creation of OVS bridges and ports (for VLAN and GRE tests), so that user would not need to invoke ovs-vsctl manually to switch from direct, 802.1Q and GRE tests. -Fixed some pylint reported warnings. -Fixed ethtool invocation so that we always try to query the physical interface to get the driver name and version. -and some others enhancements. The new usage: Node1:ovs-test -s 15531 Node2:ovs-test -c 127.0.0.1,1.1.1.1 192.168.122.151,1.1.1.2 -d -l 125 -t gre Signed-off-by: Ansis Atteka <aatteka@nicira.com>
2012-03-29 19:03:08 -07:00
python/ovstest/util.py \
python/ovstest/vswitch.py
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
Implement initial Python bindings for Open vSwitch database. These initial bindings pass a few hundred of the corresponding tests for C implementations of various bits of the Open vSwitch library API. The poorest part of them is actually the Python IDL interface in ovs.db.idl, which has not received enough attention yet. It appears to work, but it doesn't yet support writes (transactions) and it is difficult to use. I hope to improve it as it becomes clear what semantics Python applications actually want from an IDL.
2010-08-25 10:26:40 -07:00
ovs_pyfiles = \
python/ovs/__init__.py \
python/ovs/daemon.py \
python/ovs/db/__init__.py \
python/ovs/db/data.py \
python/ovs/db/error.py \
python/ovs/db/idl.py \
python/ovs/db/parser.py \
python/ovs/db/schema.py \
python/ovs/db/types.py \
python/ovs/fatal_signal.py \
python/ovs/json.py \
python/ovs/jsonrpc.py \
python/ovs/ovsuuid.py \
python/ovs/poller.py \
python/ovs/process.py \
python/ovs/reconnect.py \
python/ovs/socket_util.py \
python/ovs/stream.py \
python/ovs/timeval.py \
python: Break unixctl implementation into registry, client, and server. I wish to add some unixctl commands to the Python vlog module. However, importing ovs.unixctl in ovs.vlog creates a circular dependency, because ovs.unixctl imports ovs.vlog already. The solution, in this commit, is to break the unixctl module into three parts: a register (ovs.unixctl) that does not depend on ovs.vlog, and client (ovs.unixctl.client) and server (ovs.unixctl.server) modules that do. This breaks the circular dependency. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-05-14 11:26:36 -07:00
python/ovs/unixctl/__init__.py \
python/ovs/unixctl/client.py \
python/ovs/unixctl/server.py \
python: Port unixctl to Python. Many of the currently implemented Python daemons, and likely many daemons to be implemented in the future, could benefit from unixctl support even if only to implement "exit" and "version" commands. This patch implements unixctl in Python. Signed-off-by: Ethan Jackson <ethan@nicira.com>
2012-02-16 19:15:01 -08:00
python/ovs/util.py \
python: New method to retrieve OVS version at runtime. Version information is typically fairly useful when debugging Open vSwitch. This patch adds a new version.py module which python code can use to report its version to callers. Signed-off-by: Ethan Jackson <ethan@nicira.com>
2012-02-29 17:20:03 -08:00
python/ovs/version.py \
python: Port unixctl to Python. Many of the currently implemented Python daemons, and likely many daemons to be implemented in the future, could benefit from unixctl support even if only to implement "exit" and "version" commands. This patch implements unixctl in Python. Signed-off-by: Ethan Jackson <ethan@nicira.com>
2012-02-16 19:15:01 -08:00
python/ovs/vlog.py
tests: Add code coverage for Python. Adds support for Ned Batchelder's code coverage tool to the test suite. http://nedbatchelder.com/code/coverage/ Signed-off-by: Ethan Jackson <ethan@nicira.com>
2012-02-28 16:28:08 -08:00
PYFILES = $(ovs_pyfiles) python/ovs/dirs.py $(ovstest_pyfiles)
EXTRA_DIST += $(PYFILES)
PYCOV_CLEAN_FILES += $(PYFILES:.py=.py,cover)
Implement initial Python bindings for Open vSwitch database. These initial bindings pass a few hundred of the corresponding tests for C implementations of various bits of the Open vSwitch library API. The poorest part of them is actually the Python IDL interface in ovs.db.idl, which has not received enough attention yet. It appears to work, but it doesn't yet support writes (transactions) and it is difficult to use. I hope to improve it as it becomes clear what semantics Python applications actually want from an IDL.
2010-08-25 10:26:40 -07:00
if HAVE_PYTHON
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
nobase_pkgdata_DATA = $(ovs_pyfiles) $(ovstest_pyfiles)
Implement initial Python bindings for Open vSwitch database. These initial bindings pass a few hundred of the corresponding tests for C implementations of various bits of the Open vSwitch library API. The poorest part of them is actually the Python IDL interface in ovs.db.idl, which has not received enough attention yet. It appears to work, but it doesn't yet support writes (transactions) and it is difficult to use. I hope to improve it as it becomes clear what semantics Python applications actually want from an IDL.
2010-08-25 10:26:40 -07:00
ovs-install-data-local:
$(MKDIR_P) python/ovs
Make installation directories overridable at runtime. This makes it possible to run tests that need access to installation directories, such as the rundir, without having access to the actual installation directories (/var/run is generally not world-writable), by setting environment variables. This is not a good way to do things in general--usually it would be better to choose the correct directories at configure time--so for now this is undocumented.
2010-11-29 12:28:26 -08:00
(echo "import os" && \
echo 'PKGDATADIR = os.environ.get("OVS_PKGDATADIR", """$(pkgdatadir)""")' && \
echo 'RUNDIR = os.environ.get("OVS_RUNDIR", """@RUNDIR@""")' && \
echo 'LOGDIR = os.environ.get("OVS_LOGDIR", """@LOGDIR@""")' && \
Make the location of the database separately configurable. The default is unchanged, /etc/openvswitch/conf.db. This makes it possible to transition each Open vSwitch packaging from /etc/openvswitch/conf.db to /var/lib/openvswitch/conf.db independently. Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-07-27 15:52:21 -07:00
echo 'DBDIR = os.environ.get("OVS_DBDIR", """@DBDIR@""")' && \
Make installation directories overridable at runtime. This makes it possible to run tests that need access to installation directories, such as the rundir, without having access to the actual installation directories (/var/run is generally not world-writable), by setting environment variables. This is not a good way to do things in general--usually it would be better to choose the correct directories at configure time--so for now this is undocumented.
2010-11-29 12:28:26 -08:00
echo 'BINDIR = os.environ.get("OVS_BINDIR", """$(bindir)""")') \
> python/ovs/dirs.py.tmp
Implement initial Python bindings for Open vSwitch database. These initial bindings pass a few hundred of the corresponding tests for C implementations of various bits of the Open vSwitch library API. The poorest part of them is actually the Python IDL interface in ovs.db.idl, which has not received enough attention yet. It appears to work, but it doesn't yet support writes (transactions) and it is difficult to use. I hope to improve it as it becomes clear what semantics Python applications actually want from an IDL.
2010-08-25 10:26:40 -07:00
$(MKDIR_P) $(DESTDIR)$(pkgdatadir)/python/ovs
$(INSTALL_DATA) python/ovs/dirs.py.tmp $(DESTDIR)$(pkgdatadir)/python/ovs/dirs.py
rm python/ovs/dirs.py.tmp
python: Fix "make install" on systems without Python. Reported-by: 冯全树(Crab) <fqs888@126.com>
2011-06-13 09:37:09 -07:00
else
ovs-install-data-local:
@:
Implement initial Python bindings for Open vSwitch database. These initial bindings pass a few hundred of the corresponding tests for C implementations of various bits of the Open vSwitch library API. The poorest part of them is actually the Python IDL interface in ovs.db.idl, which has not received enough attention yet. It appears to work, but it doesn't yet support writes (transactions) and it is difficult to use. I hope to improve it as it becomes clear what semantics Python applications actually want from an IDL.
2010-08-25 10:26:40 -07:00
endif
install-data-local: ovs-install-data-local
Mark "uninstall-local" targets phony.
2011-08-25 10:19:23 -07:00
UNINSTALL_LOCAL += ovs-uninstall-local
Implement initial Python bindings for Open vSwitch database. These initial bindings pass a few hundred of the corresponding tests for C implementations of various bits of the Open vSwitch library API. The poorest part of them is actually the Python IDL interface in ovs.db.idl, which has not received enough attention yet. It appears to work, but it doesn't yet support writes (transactions) and it is difficult to use. I hope to improve it as it becomes clear what semantics Python applications actually want from an IDL.
2010-08-25 10:26:40 -07:00
ovs-uninstall-local:
rm -f $(DESTDIR)$(pkgdatadir)/python/ovs/dirs.py
python: New method to retrieve OVS version at runtime. Version information is typically fairly useful when debugging Open vSwitch. This patch adds a new version.py module which python code can use to report its version to callers. Signed-off-by: Ethan Jackson <ethan@nicira.com>
2012-02-29 17:20:03 -08:00
ALL_LOCAL += $(srcdir)/python/ovs/version.py
$(srcdir)/python/ovs/version.py: config.status
python: Fix "make distcheck" error on version.py. The generated version.py has to go in the srcdir and has to be regenerated based on config.status, which breaks "make distcheck" because it write-protects the srcdir. However, the contents of version.py only change when the version number changes, so we can just "touch" it when it doesn't really need to change. The same pattern is used elsewhere in the tree for other files in the same situation, e.g. the various RPM spec files. Reported-by: Chris Wright <chrisw@sous-sol.org> Acked-by: Chris Wright <chrisw@sous-sol.org> Signed-off-by: Ben Pfaff <blp@nicira.com>
2012-03-12 10:34:22 -07:00
$(ro_shell) > $(@F).tmp
echo 'VERSION = "$(VERSION)"' >> $(@F).tmp
if cmp -s $(@F).tmp $@; then touch $@; rm $(@F).tmp; else mv $(@F).tmp $@; fi
Reference in New Issue Copy Permalink