Re: [openstack-dev] [neutron] [l2gw] DSVM gates for networking-l2gw

It may be a non-negligible effort to make ovs containerized in the namespace in the first place (that's one of the things we still miss in fullstack in neutron repo). I know that Terry Wilson had some code for that, but I can't find it right now. Ihar On Thu, Jul 6, 2017 at 1:57 AM, Ricardo

Re: [openstack-dev] [neutron] [l2gw] DSVM gates for networking-l2gw

The idea for the future is to enable a new job with the l2gw agent enabled. In order to do that, I thought about creating a network namespace running an OVS instance with the hwvtep schema so the l2gw agent can connect to it. This is just a first rough idea and I haven't tested anything. Do you

Re: [openstack-dev] [neutron] [l2gw] DSVM gates for networking-l2gw

Plan sounds fine. Those interested in ovs backend may build on top, but at least laying basic api coverage with a fake/dummy driver is a must for a service plugin project that is serious about integration with Neutron. Ihar On Wed, Jun 14, 2017 at 9:38 PM, Ricardo Noriega De Soto

Re: [openstack-dev] [neutron] [l2gw] DSVM gates for networking-l2gw

Hello, The dummy driver allows you to make writes/reads from the database and that's something we should be continuously testing. I think you cannot achieve that mocking the API calls. Cheers On Thu, Jun 15, 2017 at 11:50 AM, Daniel Mellado wrote: > Hi Ricardo, >

Re: [openstack-dev] [neutron] [l2gw] DSVM gates for networking-l2gw

Hi Ricardo, That sounds like a totally valid approach to me, but I was wondering if there'd be a way to mock that API call. If just using the dummy driver would achieve that then I'd be more than happy to see that modification. Cheers! Daniel El 15/06/17 a las 06:38, Ricardo Noriega De Soto

[openstack-dev] [neutron] [l2gw] DSVM gates for networking-l2gw

Hello L2GWers Currently networking-l2gw CI only covers unit tests. However, there is an experimental check that starts a devstack VM to be able to run more complex tests. That experimental check is not working, and we are trying to fix it, however we encountered some difficulties that we wanted