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 <[email protected]> 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 <[email protected]> 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 >> <[email protected]> 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: >> > [email protected]?subject:unsubscribe >> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: [email protected]?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: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
