Open Stack

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 <sean at dague.net> wrote:

> 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 in
> place.
> >
> > Now that there is a devstack plugin for neutron-vpnaas, I want to remove
> > all the VPN setup from the *DevStack* repo's setup, as the user of
> > DevStack can specify the enable_plugin in their local.conf file now. The
> > commit is https://review.openstack.org/#/c/201119/.
> >
> > The issue I see though, is that the DevStack repo's jobs are failing,
> > because they are using devstack, are relying on VPN being set up, and
> > the enable_plugin line for VPN isn't part of any of the jobs shown in my
> > last post.
> >
> > How do we resolve that issue?
>
> Presumably there is a flag in Tempest for whether or not this service
> should be tested? That would be where I'd look.
>
>         -Sean
>
> --
> Sean Dague
> http://dague.net
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150727/895102ba/attachment.html>