[openstack-dev] [neutron] why do we gate tempest using q-vpn not q-l3?
armamig at gmail.com
Thu Jul 23 15:52:13 UTC 2015
On 23 July 2015 at 05:25, Ihar Hrachyshka <ihrachys at redhat.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 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, no?
 + setsid /usr/local/bin/neutron-vpn-agent --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.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
> -----END PGP SIGNATURE-----
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev