VPNaaS: Revise functional jobs to only setup DevStack
Bug #1445052 reported by
Paul Michali
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
Paul Michali |
Bug Description
In a manner similar to what is done for Neutron, the two functional jobs need to be modified to only set up DevStack, and not actually run DevStack.
Changed in neutron: | |
assignee: | nobody → Paul Michali (pcm) |
status: | New → In Progress |
Changed in neutron: | |
milestone: | none → liberty-1 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | liberty-1 → 7.0.0 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/168115 /git.openstack. org/cgit/ openstack/ neutron- vpnaas/ commit/ ?id=d7f65a2dbce 4d25b1c5d76500a 5365da5f9dfffd
Committed: https:/
Submitter: Jenkins
Branch: master
commit d7f65a2dbce4d25 b1c5d76500a5365 da5f9dfffd
Author: Paul Michali <email address hidden>
Date: Thu Mar 26 14:52:07 2015 -0400
VPNaaS: Revise functional test hooks
This commit does several things to allow functional tests to run, using a
DevStack configuration, but without stacking.
First, the gate_hook.sh is modified to specified environment variables vpn_for_ func_testing. sh.
needed for processing, and will call configure_
The new configure_ for_vpn_ func_testing. sh script will first call the Neutron for_func_ testing. sh script (as modified in [1]) to setup DevStack.
configure_
The script then installs the IPSec package, based on the functional job, and
will create the vpn_agent.ini file, in case it is needed for tests.
Minor changes are made to the post-test_hook.sh to indicate the location for
the Neutron and VPN repos.
Lastly, tox.ini is modified to place the rootwrap related files into the
virtual environment, copy in the VPN rootwrap filter, set up the rootwrap
commands, and copy the (customized) rootwrap.conf to /etc/neutron.
This last step is needed, because the neutron- vpn-netns- wrapper script that rootwrap. conf and
is (currently) used for StrongSwan, uses /etc/neutron/
doesn't allow overriding. This copying is a simple approach that will work
when multiple functional jobs are running, as the same config is used.
As a future follow-up commit, we could look into modifying the VPN device vpn-netns- wrapper script (--rootwrap_ config) . The setting could
drivers to pass the full path to the rootwrap.conf as a argument to the
neutron-
be added to the vpnagent.ini config file, available via config, to allow
this to be customized to something other than /etc/neutron (for production
use), and the functional tests could override it to point to the right
virtual environment.
To configure the environment for local run of the functional test, one
tools/ configure_ for_vpn_ func_testing. sh <devstack-repo> [-i]
can do:
where:
devstack- repo... Path to devstack repo (/opt/stack/ new/devstack
when run by gate)
-i..... ....... .. Indicates to install Neutron package dependencies
For StrongSwan, prefix the command with VENV=dsvm- functional- sswan
Ref: [1] https:/ /review. openstack. org/#/c/ 176064/
Change-Id: I2243b06b3cdbb3 52dac7bc47d03c8 30efb87be3c 26ad0a57d062076 e472762837e
Closes-Bug: #1445052
Depends-On: Ie490e89c1a65e1