Re: [openstack-dev] [neutron] why do we gate tempest using q-vpn not q-l3?

2015-07-24 Thread Ihar Hrachyshka
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/23/2015 05:52 PM, Armando M. wrote: On 23 July 2015 at 05:25, Ihar Hrachyshka ihrac...@redhat.com mailto:ihrac...@redhat.com wrote: Hi all, I've stumbled on this one. It turns out we gate neutron against openstack installation

[openstack-dev] [neutron] why do we gate tempest using q-vpn not q-l3?

2015-07-23 Thread Ihar Hrachyshka
-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 [1]. Is it really what we want to do? I would expect that gate validates l3 agent as is, as is usually found on

Re: [openstack-dev] [neutron] why do we gate tempest using q-vpn not q-l3?

2015-07-23 Thread Assaf Muller
It's a remnant of pre-*aaS split times - We have to reexamine our testing strategy post-split. - Original Message - -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

Re: [openstack-dev] [neutron] why do we gate tempest using q-vpn not q-l3?

2015-07-23 Thread Armando M.
On 23 July 2015 at 05:25, Ihar Hrachyshka ihrac...@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 [1]. Is it really what we want to do?