[openstack-dev] [Neutron] OVS 2.1.0 is available but not the Neutron ARP responder
mestery at noironetworks.com
Fri Mar 21 13:04:36 UTC 2014
Getting this type of functional testing into the gate would be pretty
Thanks for your continued efforts here Mathieu! If there is anything I can
help here, let me know. One other concern here is that the infra team may
issues running a version of OVS which isn't packaged into Ubuntu/CentOS.
that in mind as well.
Edourard, I look forward to your blog, please share it here once you've
On Fri, Mar 21, 2014 at 6:15 AM, Édouard Thuleau <thuleau at gmail.com> wrote:
> Thanks Mathieu for your support and work onto CI to enable multi-node.
> I wrote a blog post about how to run devstack development environment with
> I hope it will be publish next week.
> Just add a pointer about OVS support network namespaces since 2 years ago
> now .
> On Fri, Mar 21, 2014 at 11:31 AM, Mathieu Rohon <mathieu.rohon at gmail.com>wrote:
>> Hi edouard,
>> thanks for the information. I would love to see your patch getting
>> merged to have l2-population MD fully functional with an OVS based
>> deployment. Moreover, this patch has a minimal impact on neutron,
>> since the code is used only if l2-population MD is used in the ML2
>> markmcclain was concerned that no functional testing is done, but
>> L2-population MD needs mutlinode deployment to be tested. A deployment
>> based on a single VM won't create overlay tunnels, which is a
>> mandatory technology to have l2-population activated.
>> The Opensatck-CI is not able, for the moment, to run job based on
>> multi-node deployment. We proposed an evolution of devstack to have a
>> multinode deployment based on a single VM which launch compute nodes
>> in LXC containers , but this evolution has been refused by
>> Opensatck-CI since there is other ways to run multinode setup with
>> devstack, and LXC container is not compatible with iscsi and probably
>> ovs .
>> One way to have functional test for this feature would be to deploy
>> 3rd party testing environment, but it would be a pity to have to
>> maintain a 3rd party to test some functionalities which are not based
>> on 3rd party equipments. So we are currently learning about the
>> Openstack-CI tools to propose some evolutions to have mutinode setup
>> inside the gate . There are a lot of way to implement it
>> (node-pools evolution, usage of tripleO, of Heat ), and we don't
>> know which one would be the easiest, and so the one we have to work on
>> to have the multinode feature available ASAP.
>> This feature looks very important for Neutron, at least to test
>> overlay tunneling. I thinks it's very important for nova too, to test
>> On Fri, Mar 21, 2014 at 10:08 AM, Édouard Thuleau <thuleau at gmail.com>
>> > Hi,
>> > Just to inform you that the new OVS release 2.1.0 was done yesterday
>> > This release contains new features and significant performance
>> > .
>> > And in that new features, one  was use to add local ARP responder
>> > OVS agent and the plugin ML2 with the MD l2-pop . Perhaps, it's time
>> > reconsider that review?
>> >  https://firstname.lastname@example.org/msg09251.html
>> >  http://openvswitch.org/releases/NEWS-2.1.0
>> > 
>> >  https://review.openstack.org/#/c/49227/
>> > Regards,
>> > Édouard.
>> > _______________________________________________
>> > OpenStack-dev mailing list
>> > OpenStack-dev at lists.openstack.org
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev