You would build variants of the jobs you want that specifically enable
your plugin.
That being said, you should focus on jobs that substantially test your
component, not just the giant list of all jobs. Part of our focus in on
decoupling so that for something like vpnaas you can start with the
Maybe I'm not explaining myself well (sorry)...
For VPN commits, there are functional jobs that (now) enable the devstack
plugin for neutron-vpnaas as needed (and grenade job will do the same).
From the neutron-vpnaas repo standpoint everything is in place.
Now that there is a devstack plugin
Yes, the plugin enables the service, and for the neutron-vpnaas DSVM based
jobs, I have the enable_plugin line added to the job so that everything
works.
However, for the DevStack repo, which runs a bunch of other DSVM jobs, this
fails, as there is (obviously) no enable_plugin line.:
-
On 07/27/2015 08:21 AM, Paul Michali wrote:
Maybe I'm not explaining myself well (sorry)...
For VPN commits, there are functional jobs that (now) enable the
devstack plugin for neutron-vpnaas as needed (and grenade job will do
the same). From the neutron-vpnaas repo standpoint everything is
Not being very familiar with how this all works, can someone provide a bit
more hand holding here?
The overall question is, do we remove VPN from all the DevStack based tests
(except for those run by VPN repo)?
Thanks,
PCM
On Mon, Jul 27, 2015 at 8:26 AM Sean Dague s...@dague.net wrote:
On
Hi,
I've created a DevStack plugin for the neutron-vpnaas repo. Now, I'm trying
to remove the q-vpn service setup from the DevStack repo (
https://review.openstack.org/#/c/201119/).
However, I'm hitting an issue in that (almost) every test that uses
DevStack fails, because it is no longer
On Fri, Jul 24, 2015, at 02:05 PM, Paul Michali wrote:
Hi,
I've created a DevStack plugin for the neutron-vpnaas repo. Now, I'm
trying
to remove the q-vpn service setup from the DevStack repo (
https://review.openstack.org/#/c/201119/).
However, I'm hitting an issue in that (almost)
