[openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network to Neutron migration work]

Miguel Angel Ajo Pelayo mangelajo at redhat.com
Tue Apr 14 12:02:07 UTC 2015

> On 10/4/2015, at 20:10, Kyle Mestery <mestery at mestery.com> wrote:
> On Fri, Apr 10, 2015 at 1:03 PM, Sean M. Collins <sean at coreitpro.com <mailto:sean at coreitpro.com>> wrote:
> We already tried to make Neutron the default with OVS - and the results
> were not good[1].
> Operators who are currently not using Neutron have said that they do
> not want to learn both Neutron and also Open vSwitch at the same time.
> This was documented at the operator's summit. We clearly have a
> stumbling block - Open vSwitch.
> https://etherpad.openstack.org/p/PHL-ops-nova-feedback <https://etherpad.openstack.org/p/PHL-ops-nova-feedback>
> https://etherpad.openstack.org/p/PHL-ops-OVS <https://etherpad.openstack.org/p/PHL-ops-OVS>
> Based on discussions we had at the QA sprint, the idea is to start with
> a very simple Neutron configuration in DevStack, so that we can remove
> nova-network as the default. The argument is that the people
> who are still using nova-network are comfortable with Linux Bridge, and
> that having Linux Bridge as the default Neutron agent will serve as
> a "bridge" (no pun intended) into the Neutron world.
> There will be *clear* documentation that this is a very simplistic
> model, and it will be made obvious that for more advanced scenarios you
> will need to configure your local.conf to use the Open vSwitch agent.
> I've spoken with Sean Dague about testing Linux Bridge and
> the idea is that we should have test coverage of both OVS and Linux
> Bridge, and that currently there is a gap with Linux Bridge. I think
> that it's OK if we override the default at the gate to run OVS, since
> that has the most test coverage and will cause the least disruption.
> There will be jobs created, that will test Linux Bridge similar to how
> Open vSwitch is tested at the gate today.
> As a DevStack user, I would like to see Neutron as the default. After
> making Neutron the default, the changes needed for the local.conf file
> for me to run my mechanism driver of choice is significantly smaller
> than the changes needed today for my local.conf/localrc to
> disable Nova-Network, enable Neutron, and run my mechanism driver of choice.
> If Linux Bridge being the default is the way to make the above happen,
> so be it.
> ++, well said Sean. I support what's being done here.
> [1]: https://review.openstack.org/#/c/153208/ <https://review.openstack.org/#/c/153208/>

-1 ;)

Why would operators install from devstack? that’s not going to be the case.

I believe we should have both LB & OVS well tested, if LB is a good option for
some operators willing to migrate from nova, that’s great, let’s make sure LB 
is perfectly tested upstream.

But by doing such change we can’t let OVS code rot and we would be neglecting
a big customer base which is now making use of the openvswitch mechanism.
(may be I’m miss understanding  the scope of the change).

> --
> Sean M. Collins
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe <http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org <mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
Miguel Angel Ajo

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150414/8e429619/attachment.html>

More information about the OpenStack-dev mailing list