[openstack-dev] [neutron] why do we gate tempest using q-vpn not q-l3?
ihrachys at redhat.com
Fri Jul 24 09:42:51 UTC 2015
-----BEGIN PGP SIGNED MESSAGE-----
On 07/23/2015 05:52 PM, Armando M. wrote:
> On 23 July 2015 at 05:25, Ihar Hrachyshka <ihrachys at redhat.com
> <mailto:ihrachys at redhat.com>> wrote:
> Hi all,
> I've stumbled on this one. It turns out we gate neutron against
> openstack installation that runs vpn-agent instead of l3-agent .
> Is it really what we want to do? I would expect that gate validates
> l3 agent as is, as is usually found on usual installations that do
> not need vpn connections.
>> We run with q-fwaas as well (which then lead to  as command
>> line for the L3 agent execution). Same can be said for fwaas,
>>  + setsid /usr/local/bin/neutron-vpn-agent --config-file
>> --config-file=/etc/neutron/vpn_agent.ini --config-file
> Or is it the neat way we make sure we don't break vpn-agent?
>> The tempest-full test suite used to exercise network core
>> capabilities as well as advanced services (with
>> test_vpnaas_extensions and test_fwaas_extensions), now that it
>> doesn't anymore  we could drop both, as coverage is ensured by
>> the neutron-dsvm-api job.
>>  https://review.openstack.org/#/c/186559/
I will only note that it effectively disabled test coverage for stable
branches where we don't have those new jobs yet. Doug told in comments
we have a plan to introduce those back into stable branches in several
weeks, a month ago. I wonder whether we have anything reviewable to
make it happen.
I requested drop for advanced services from neutron tempest jobs:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
More information about the OpenStack-dev