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

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

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

Ricardo Noriega De Soto
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 to share with you.


The configuration of the experimental check uses the L2GW agent which is very good, however, the API tests try to create a l2gw connection and fail since there is not an ovsdb instance with the vtep schema to execute.

If we use the dummy driver, these three failing testcases will be skipped and we have a way to test the API (without backend).

So for now, our proposal is to modify this experimental check using the dummy driver, and convert it to a possible non-voting -> voting gate executing pure API tests.

Furthermore, we will start working on a new gate with the l2gw agent and create a new OVS entity in a namespace or something similar to be able to test api and agent together.

Any comment is more than welcome!

Thanks guys

--
Ricardo Noriega

Senior Software Engineer - NFV Partner Engineer | Office of Technology  | Red Hat
irc: rnoriega @freenode


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [hidden email]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Reply | Threaded
Open this post in threaded view
|

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

Daniel Mellado
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 escribió:

> 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 to
> share with you.
>
> https://review.openstack.org/#/c/471692/
>
> The configuration of the experimental check uses the L2GW agent which is
> very good, however, the API tests try to create a l2gw connection and
> fail since there is not an ovsdb instance with the vtep schema to execute.
>
> If we use the dummy driver, these three failing testcases will be
> skipped and we have a way to test the API (without backend).
>
> So for now, our proposal is to modify this experimental check using the
> dummy driver, and convert it to a possible non-voting -> voting gate
> executing pure API tests.
>
> Furthermore, we will start working on a new gate with the l2gw agent and
> create a new OVS entity in a namespace or something similar to be able
> to test api and agent together.
>
> Any comment is more than welcome!
>
> Thanks guys
>
> --
> Ricardo Noriega
>
> Senior Software Engineer - NFV Partner Engineer | Office of Technology
>  | Red Hat
> irc: rnoriega @freenode
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: [hidden email]?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [hidden email]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Reply | Threaded
Open this post in threaded view
|

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

Ricardo Noriega De Soto
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 <[hidden email]> wrote:
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 escribió:
> 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 to
> share with you.
>
> https://review.openstack.org/#/c/471692/
>
> The configuration of the experimental check uses the L2GW agent which is
> very good, however, the API tests try to create a l2gw connection and
> fail since there is not an ovsdb instance with the vtep schema to execute.
>
> If we use the dummy driver, these three failing testcases will be
> skipped and we have a way to test the API (without backend).
>
> So for now, our proposal is to modify this experimental check using the
> dummy driver, and convert it to a possible non-voting -> voting gate
> executing pure API tests.
>
> Furthermore, we will start working on a new gate with the l2gw agent and
> create a new OVS entity in a namespace or something similar to be able
> to test api and agent together.
>
> Any comment is more than welcome!
>
> Thanks guys
>
> --
> Ricardo Noriega
>
> Senior Software Engineer - NFV Partner Engineer | Office of Technology
>  | Red Hat
> irc: rnoriega @freenode
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request@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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Ricardo Noriega

Senior Software Engineer - NFV Partner Engineer | Office of Technology  | Red Hat
irc: rnoriega @freenode


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [hidden email]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Reply | Threaded
Open this post in threaded view
|

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

Ihar Hrachyshka
In reply to this post by Ricardo Noriega De Soto
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
<[hidden email]> wrote:

> 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 to share with you.
>
> https://review.openstack.org/#/c/471692/
>
> The configuration of the experimental check uses the L2GW agent which is
> very good, however, the API tests try to create a l2gw connection and fail
> since there is not an ovsdb instance with the vtep schema to execute.
>
> If we use the dummy driver, these three failing testcases will be skipped
> and we have a way to test the API (without backend).
>
> So for now, our proposal is to modify this experimental check using the
> dummy driver, and convert it to a possible non-voting -> voting gate
> executing pure API tests.
>
> Furthermore, we will start working on a new gate with the l2gw agent and
> create a new OVS entity in a namespace or something similar to be able to
> test api and agent together.
>
> Any comment is more than welcome!
>
> Thanks guys
>
> --
> Ricardo Noriega
>
> Senior Software Engineer - NFV Partner Engineer | Office of Technology  |
> Red Hat
> irc: rnoriega @freenode
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: [hidden email]?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [hidden email]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Reply | Threaded
Open this post in threaded view
|

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

Ricardo Noriega De Soto
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 have any other good approach for this???

On Mon, Jul 3, 2017 at 5:14 PM, Ihar Hrachyshka <[hidden email]> wrote:
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
<[hidden email]> wrote:
> 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 to share with you.
>
> https://review.openstack.org/#/c/471692/
>
> The configuration of the experimental check uses the L2GW agent which is
> very good, however, the API tests try to create a l2gw connection and fail
> since there is not an ovsdb instance with the vtep schema to execute.
>
> If we use the dummy driver, these three failing testcases will be skipped
> and we have a way to test the API (without backend).
>
> So for now, our proposal is to modify this experimental check using the
> dummy driver, and convert it to a possible non-voting -> voting gate
> executing pure API tests.
>
> Furthermore, we will start working on a new gate with the l2gw agent and
> create a new OVS entity in a namespace or something similar to be able to
> test api and agent together.
>
> Any comment is more than welcome!
>
> Thanks guys
>
> --
> Ricardo Noriega
>
> Senior Software Engineer - NFV Partner Engineer | Office of Technology  |
> Red Hat
> irc: rnoriega @freenode
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request@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-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Ricardo Noriega

Senior Software Engineer - NFV Partner Engineer | Office of Technology  | Red Hat
irc: rnoriega @freenode


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [hidden email]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Reply | Threaded
Open this post in threaded view
|

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

Ihar Hrachyshka
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 Noriega De Soto
<[hidden email]> wrote:

> 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 have any other good approach for this???
>
> On Mon, Jul 3, 2017 at 5:14 PM, Ihar Hrachyshka <[hidden email]> wrote:
>>
>> 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
>> <[hidden email]> wrote:
>> > 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 to share with
>> > you.
>> >
>> > https://review.openstack.org/#/c/471692/
>> >
>> > The configuration of the experimental check uses the L2GW agent which is
>> > very good, however, the API tests try to create a l2gw connection and
>> > fail
>> > since there is not an ovsdb instance with the vtep schema to execute.
>> >
>> > If we use the dummy driver, these three failing testcases will be
>> > skipped
>> > and we have a way to test the API (without backend).
>> >
>> > So for now, our proposal is to modify this experimental check using the
>> > dummy driver, and convert it to a possible non-voting -> voting gate
>> > executing pure API tests.
>> >
>> > Furthermore, we will start working on a new gate with the l2gw agent and
>> > create a new OVS entity in a namespace or something similar to be able
>> > to
>> > test api and agent together.
>> >
>> > Any comment is more than welcome!
>> >
>> > Thanks guys
>> >
>> > --
>> > Ricardo Noriega
>> >
>> > Senior Software Engineer - NFV Partner Engineer | Office of Technology
>> > |
>> > Red Hat
>> > irc: rnoriega @freenode
>> >
>> >
>> >
>> > __________________________________________________________________________
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe:
>> > [hidden email]?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: [hidden email]?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> --
> Ricardo Noriega
>
> Senior Software Engineer - NFV Partner Engineer | Office of Technology  |
> Red Hat
> irc: rnoriega @freenode
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: [hidden email]?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [hidden email]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev