Re: [openstack-dev] [neutron] why do we gate tempest using q-vpn not q-l3?
-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 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 usual installations that do not need vpn connections. We run with q-fwaas as well (which then lead to [1] as command line for the L3 agent execution). Same can be said for fwaas, no? [1] + setsid /usr/local/bin/neutron-vpn-agent --config-file /etc/neutron/neutron.conf --config-file=/etc/neutron/l3_agent.ini --config-file=/etc/neutron/vpn_agent.ini --config-file /etc/neutron/fwaas_driver.ini 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 [2] we could drop both, as coverage is ensured by the neutron-dsvm-api job. [2] 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: https://review.openstack.org/#/c/205473/ Ihar -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVsgiYAAoJEC5aWaUY1u57ZnEH/09olZehrRaovDD3sIlLEIPs cpV8fjHiBHBmpmo7DznGVcXDyk6jaJrIB0OMEwy0QkO11WDRw0cy1kH40of2Zd89 jImnW/Xo0KQQTHhjwm7J6tZ8lZI6SMR40WG40Hi9ZpaWVfIZPTl0SoIEzZwF8sgs cAFTxPd9h7Uc1MGM91Uazx112sMFtVBx+RMt21o53nX/uBjS5nBkXmDVFk0XDc0A EiRdhzU1JlOeYixA3FUtHUKHVAsWsV0XPeXgJn7tI2lDuZR0cwTYPuliQjXmyjiJ z3yDAFQhmFZ8PWZcvQCEC6cy8fS4C4h/ylaM/+/GK5zhcOThe90LwWeOWB0caPw= =K3qh -END PGP SIGNATURE- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [neutron] why do we gate tempest using q-vpn not q-l3?
-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 usual installations that do not need vpn connections. Or is it the neat way we make sure we don't break vpn-agent? [1]: https://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/test-f eatures.sh#n21 Ihar -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVsN1RAAoJEC5aWaUY1u57eZ0IAI9oJIikbvD5dxGPoB7wm7mX 9OE583CAjn+hGUIMGa0kpVSBeDQmkQdp92ginFOo1lvXQZVT30OCOJau5YVoGE77 Nl1d9TX6xO8vDkBNT5A69vHfZGxjL620+HvOHjupTYimqWiilj6fu0oUge2DNtI7 do8TgL7SpDx31z9pF70zxqfHbARXq3HOb/AMfTz8jBRcnZmuvOQLt4Q/Xri6KFUw uW8XaEZ+3xJYsaFsWna8YIEQY/R4TDqnyStGvRqzX9CGRDkzc/0gWalBSAkXewdQ sOwN4MhhxJcWMXRVwPp+auvBOKQJ8Bq5uIR0WRIDhAaUtDNHstDefFnCBzmX8nc= =kxs2 -END PGP SIGNATURE- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] why do we gate tempest using q-vpn not q-l3?
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 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 usual installations that do not need vpn connections. Or is it the neat way we make sure we don't break vpn-agent? [1]: https://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/test-f eatures.sh#n21 Ihar -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVsN1RAAoJEC5aWaUY1u57eZ0IAI9oJIikbvD5dxGPoB7wm7mX 9OE583CAjn+hGUIMGa0kpVSBeDQmkQdp92ginFOo1lvXQZVT30OCOJau5YVoGE77 Nl1d9TX6xO8vDkBNT5A69vHfZGxjL620+HvOHjupTYimqWiilj6fu0oUge2DNtI7 do8TgL7SpDx31z9pF70zxqfHbARXq3HOb/AMfTz8jBRcnZmuvOQLt4Q/Xri6KFUw uW8XaEZ+3xJYsaFsWna8YIEQY/R4TDqnyStGvRqzX9CGRDkzc/0gWalBSAkXewdQ sOwN4MhhxJcWMXRVwPp+auvBOKQJ8Bq5uIR0WRIDhAaUtDNHstDefFnCBzmX8nc= =kxs2 -END PGP SIGNATURE- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [neutron] why do we gate tempest using q-vpn not q-l3?
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? 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 [1] as command line for the L3 agent execution). Same can be said for fwaas, no? [1] + setsid /usr/local/bin/neutron-vpn-agent --config-file /etc/neutron/neutron.conf --config-file=/etc/neutron/l3_agent.ini --config-file=/etc/neutron/vpn_agent.ini --config-file /etc/neutron/fwaas_driver.ini 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 [2] we could drop both, as coverage is ensured by the neutron-dsvm-api job. [2] https://review.openstack.org/#/c/186559/ [1]: https://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/test-f eatures.sh#n21 Ihar -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVsN1RAAoJEC5aWaUY1u57eZ0IAI9oJIikbvD5dxGPoB7wm7mX 9OE583CAjn+hGUIMGa0kpVSBeDQmkQdp92ginFOo1lvXQZVT30OCOJau5YVoGE77 Nl1d9TX6xO8vDkBNT5A69vHfZGxjL620+HvOHjupTYimqWiilj6fu0oUge2DNtI7 do8TgL7SpDx31z9pF70zxqfHbARXq3HOb/AMfTz8jBRcnZmuvOQLt4Q/Xri6KFUw uW8XaEZ+3xJYsaFsWna8YIEQY/R4TDqnyStGvRqzX9CGRDkzc/0gWalBSAkXewdQ sOwN4MhhxJcWMXRVwPp+auvBOKQJ8Bq5uIR0WRIDhAaUtDNHstDefFnCBzmX8nc= =kxs2 -END PGP SIGNATURE- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
