neutron-vpnaas/neutron_vpnaas
Paul Michali d8dd053b0a VPNaaS: Don't clone neutron automatically for tests
As part of the work to allow VPN functionals job to run when Neutron
commits are reviewed, we need to be more intelligent about how
dependencies are resolved in the tox.ini for this repo.

This commit does the same as LBaaS, using a script to determine whether
an existing Neutron repo exists (and use that for a Neutron patch-set
running the VPN tests) or whether the Neutron repo needs to be cloned
(for a VPN patch set).

With the VPN repo, the rootwrap config file and filters need to be set
up. The deploy_rootwrap script is modified to do all actions related to
setup, instead of doing part of that in tox.ini, as before. In addition,
rootwrap config and needed filters for testing from Neutron are added to
this repo, so there is no dependency on Neutron (whose location cannot
be assumed in the gate).

NOTE: To run functional tests locally, one needs to set VENV for the
desired functional target and invoke configure_vpn_for_func_testing.sh.
Next, run tox for the functional target with --notest to setup the
virtual environment. Then, install Neutron into the virtual env. Finally,
the functional test can then be invoked.

This must be upstreamed, before allowing the VPN functional job to run
for Neutron jobs.

Change-Id: Idb3c4dff0dbb40e30b2b49591df0b014b769f167
2015-07-06 09:51:47 -04:00
..
cmd Introduce Vyatta VPN agent cmd in monkey patched eventlet module 2015-03-20 13:35:56 -07:00
db Switch to oslo_utils.uuidutils 2015-06-22 11:02:57 +00:00
extensions Assign external_ip based on ip version of peer_address 2015-05-20 06:28:47 +00:00
services Switch to oslo.service 2015-06-25 12:19:43 +03:00
tests VPNaaS: Don't clone neutron automatically for tests 2015-07-06 09:51:47 -04:00
__init__.py Split vpnaas services code into neutron-vpnaas 2014-12-08 13:37:08 -07:00
version.py After the services split, get neutron-vpnaas Jenkins jobs passing 2014-12-09 00:00:04 -07:00