Take configuraiton control to test hooks for networking-odl

This will enable us to reduce the dependency on Tempest, just
as much as the other Neutron/-* jobs do, and long term allow
us to drive testing efforts directly from networking-odl
patches.

Change-Id: I8be805958df399f29f5cd24bdb59179d41f7e447
Signed-off-by: Kyle Mestery <mestery@mestery.com>
This commit is contained in:
Kyle Mestery 2015-06-16 20:40:45 +00:00
parent 8572f62dea
commit dea15a2b17

View File

@ -16,20 +16,11 @@
export PYTHONUNBUFFERED=true
export DEVSTACK_GATE_TIMEOUT=120
export DEVSTACK_GATE_NEUTRON=1
# Make sure tempest is installed, but run it out of the post_test_hooks.sh
# script from the networking-odl repository.
export DEVSTACK_GATE_TEMPEST=1
export DEVSTACK_GATE_TEMPEST_NOTESTS=1
# Be explicit about what services we enable
ENABLED_SERVICES=q-svc,q-dhcp,q-meta,quantum,tempest,
ENABLED_SERVICES+=n-api,n-cond,n-cpu,n-crt,n-obj,n-sch
ENABLED_SERVICES+=g-api,g-reg,mysql,rabbit,key
export ENABLED_SERVICES
# For now, run a small number of tests until we get the issues
# on the ODL sorted out
export DEVSTACK_GATE_TEMPEST_REGEX="tempest.api.network.test_networks \
tempest.api.network.test_networks_negative \
tempest.api.network.test_ports"
export BRANCH_OVERRIDE={branch-override}
if [ "$BRANCH_OVERRIDE" != "default" ] ; then
export OVERRIDE_ZUUL_BRANCH=$BRANCH_OVERRIDE