Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack

I wanted to provide a quick update - the patch is passing tests at the gate, however it is with a couple defaults hard-coded in. We are picking eth0 as the physical interface, and VLANs. https://review.openstack.org/#/c/168423/ I have another patch that is WIP that switches to VXLAN, but I also n

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

: Tuesday, April 28, 2015 1:22:44 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network to Neutron migration work] You can tcpdump the ovs ports as usual. Please keep in mind

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

- > From: "Jeremy Stanley" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Tuesday, April 21, 2015 5:00:24 PM > Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in > DevStack [was: Status of the nova-networ

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

On 2015-04-21 03:19:04 -0400 (-0400), Attila Fazekas wrote: [...] > IMHO the OVS is less complex than netfilter (iptables, *tables), > if someone able to deal with reading the netfilter rules he should > be able to deal with OVS as well. In a simple DevStack setup, you really have that many iptabl

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

- Original Message - > From: "Jeremy Stanley" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Friday, April 17, 2015 9:35:07 PM > Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in > Dev

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

S. This point has been made clear. On Sat, Apr 18, 2015 at 9:42 AM, Monty Taylor wrote: > On 04/18/2015 10:44 AM, Fox, Kevin M wrote: > > Replying inline. > > > >> -Original Message- From: Monty Taylor > >> [mailto:mord...@inaugust.com] Sent: Friday, April

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

wrote: > > I know the DevStack issue seems to be solved, but I had to > > respond.inline > > > > From: Fox, Kevin M [mailto:kevin@pnnl.gov] Sent: Friday, April > > 17, 2015 12:28 To: OpenStack Development Mailing List (not for usage > > questions) Subject: Re: [o

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

>>> From: Fox, Kevin M [mailto:kevin@pnnl.gov] Sent: Friday, >>> April 17, 2015 12:28 To: OpenStack Development Mailing List (not >>> for usage questions) Subject: Re: [openstack-dev] [Nova][Neutron] >>> Linuxbridge as the default in DevStack [was: S

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

On 2015-04-18 14:51:36 + (+), Fox, Kevin M wrote: > How will it help to have a flat network where all vms, not just > the ones that need that scarce resource are on the same network > consuming ips? You seem to make the assumption that IP addresses are always scarce. Perhaps for some envir

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

for usage questions) Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network to Neutron migration work] Monty many thanks for a clear summary, fully agree with you. I have a nightmare trying to educate developers (mainly from client

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

Replying inline. > -Original Message- > From: Monty Taylor [mailto:mord...@inaugust.com] > Sent: Friday, April 17, 2015 7:53 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in > DevStack [was: Status o

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

ack Development Mailing List (not for usage > > questions) Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge > > as the default in DevStack [was: Status of the nova-network to > > Neutron migration work] > > > > No, the complaints from ops I have heard even inte

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

l >> 17, 2015 12:28 To: OpenStack Development Mailing List (not for usage >> questions) Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge >> as the default in DevStack [was: Status of the nova-network to >> Neutron migration work] >> >> No, the complaints fr

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

nd/or single system by system upgrades > until they are either tempted with something > shiny/fun/cool/sexy/powerful or coerced by management to change. > Until you can demonstrate a *benefit* to them to move to the neutron > paradigm for their flatDHCP network, you won't get them to move. > They'll take a lear

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

lle Grober [rochelle.gro...@huawei.com] Sent: Friday, April 17, 2015 3:48 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network to Neutron migration work] I know the DevS

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

I know the DevStack issue seems to be solved, but I had to respond.inline From: Fox, Kevin M [mailto:kevin@pnnl.gov] Sent: Friday, April 17, 2015 12:28 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default

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

On Fri, Apr 17, 2015 at 3:17 PM, Salvatore Orlando wrote: > let's default to linux bridge. At the end of the day I believe users > interested in OVS will find in a simple way in the documentation - possibly > even in the README file, a way for enabling it. We might even ship a > local.conf.ovs fi

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

On 17 April 2015 at 21:35, Jeremy Stanley wrote: > On 2015-04-17 11:49:23 -0700 (-0700), Kevin Benton wrote: > > I definitely understand that. But what is the major complaint from > > operators? I understood that quote to imply it was around > > Neutron's model of self-service networking. > > My

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

On Fri, Apr 17, 2015 at 2:58 PM, Fox, Kevin M wrote: > Its because someone recommended devstack be switched to linux bridge so > that its easier for folks to learn openstack. but my assertion is, if all > production sites will have to run ovs I believe this is a false assertion and the crux of

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

Sent: Friday, April 17, 2015 12:35 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network to Neutron migration work] On 2015-04-17 11:49:23 -0700 (-0700), Kevin Benton

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

On 2015-04-17 11:49:23 -0700 (-0700), Kevin Benton wrote: > I definitely understand that. But what is the major complaint from > operators? I understood that quote to imply it was around > Neutron's model of self-service networking. My takeaway from Tom's message was that there was a concern about

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

the issue to bed. Lets do that sooner rather then later so a couple of years from now, we're done. :/ Kevin From: Kevin Benton [blak...@gmail.com] Sent: Friday, April 17, 2015 11:49 AM To: OpenStack Development Mailing List (not for usage questions) Subject:

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

I definitely understand that. But what is the major complaint from operators? I understood that quote to imply it was around Neutron's model of self-service networking. If the main reason the remaining Nova-net operators don't want to use Neutron is due to the fact that they don't want to deal wit

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

On 2015-04-17 10:55:19 -0700 (-0700), Kevin Benton wrote: > I understand. What I'm saying is that switching to Linux bridge > will not change the networking model to 'just connect everything > to a simple flat network'. All of the complaints about > self-service networking will still hold. And con

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

doens'nt give you NaaS... way to costly to do) Thanks, Kevin From: Ihar Hrachyshka [ihrac...@redhat.com] Sent: Friday, April 17, 2015 9:34 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in

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

>On the contrary, if you reread the message to which you were previously replying, it's was about the unnecessary complexity of OVS (and Neutron in general) for deployments which explicitly _don't_ need and can never take advantage of self-service networking. The implication being that Neutron need

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/17/2015 06:23 PM, Fox, Kevin M wrote: > Really, what I expect to see long term in a healthy OpenStack > ecosystem is some global AppStore like functionality baked in to > horizon. A user goes to it, selects "my awesome scalable web > hosting syst

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

extremely difficult if OpenStack clouds differ wildly in functionality. Thanks, Kevin From: Salvatore Orlando Sent: Friday, April 17, 2015 8:45:45 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbri

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

And since we've circled back I might add that perhaps we want nova-network to deliver that. Simple, reliable networking leveraging well-established off-the-shelf technologies that satisfies the use cases Jeremy is referring to. If regardless of changes in governance pertaining openstack project th

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

On 2015-04-16 21:17:03 -0700 (-0700), Kevin Benton wrote: > What do you disagree with? I was pointing out that using Linux > bridge will not reduce the complexity of the model of self-service > networking, which is what the quote was complaining about. On the contrary, if you reread the message to

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

trong OpenStack ecosystem. Thanks, Kevin From: Kevin Benton Sent: Thursday, April 16, 2015 9:17:03 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of th

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

What do you disagree with? I was pointing out that using Linux bridge will not reduce the complexity of the model of self-service networking, which is what the quote was complaining about. I just wanted to point out that one of the 'major disconnects' as I understand it will not get any better by

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

On 2015-04-16 18:34:40 -0700 (-0700), Kevin Benton wrote: [...] > This is referring to the complexity of the API model for Neutron. > While this is a problem that I hope to address by making things > like shared networks more useful, it's not really relevant to this > particular discussion because

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

onal > complexity provides, there's no way they'll consider the complexity > "necessary", and will keep using nova-network :) > > > In addition - we kinda have part of our mission statement that has the > words "simple to implement", so it's very rarely OK

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

et a truly scalable NaaS, which I think is critical, you need advanced SDN and I'm not convinced LinuxBridge is advanced enough to work long term... Thanks, Kevin ____________ From: Tom Fifield [t...@openstack.org] Sent: Wednesday, April 15, 2015 7:09 PM To: openstac

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

, > Kevin > > > From: Tom Fifield [t...@openstack.org] > Sent: Wednesday, April 15, 2015 7:09 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in > DevStack [was: Sta

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

vinced LinuxBridge is advanced enough to work long term... Thanks, Kevin From: Tom Fifield [t...@openstack.org] Sent: Wednesday, April 15, 2015 7:09 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the

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

On Wed, Apr 15, 2015 at 10:09:24PM EDT, Tom Fifield wrote: > On 16/04/15 10:54, Fox, Kevin M wrote: > >Yes, but if stuff like dvr is the only viable replacement to > >nova-network in production, then learning the non representitive config > >of neutron with linuxbridge might be misleading/count

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

>> *From:* Tom Fifield >> *Sent:* Wednesday, April 15, 2015 5:58:43 PM >> *To:* openstack-dev@lists.openstack.org >> *Subject:* Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the >> default in DevStack [was: Status of the

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

st HA replacement, you'd be OK with this change? Kevin * * *From:* Tom Fifield *Sent:* Wednesday, April 15, 2015 5:58:43 PM *To:* openstack-dev@lists.openstack.org *Subject:* Re: [openstack-dev] [Nova][Neutron] Linuxbri

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

Fifield Sent: Wednesday, April 15, 2015 5:58:43 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network to Neutron migration work] On 14/04/15 23:36, Dean Troyer wrote: > On Tue, Apr 14, 2015 a

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

On Wed, Apr 15, 2015 at 7:58 PM, Tom Fifield wrote: > If they do they need more help than we can give... >> > > So, ummm, there is actually a valid use case for ops on devstack: it's > part of the learning process. > Yes, this is very true. The context in my mind included the not-present-above

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

On 14/04/15 23:36, Dean Troyer wrote: On Tue, Apr 14, 2015 at 7:02 AM, Miguel Angel Ajo Pelayo mailto:mangel...@redhat.com>> wrote: Why would operators install from devstack? that’s not going to be the case. If they do they need more help than we can give... So, ummm, there is actu

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

On Tue, Apr 14, 2015 at 9:36 AM, Dean Troyer wrote: > On Tue, Apr 14, 2015 at 7:02 AM, Miguel Angel Ajo Pelayo < > mangel...@redhat.com> wrote: > >> Why would operators install from devstack? that’s not going to be the >> case. >> > > If they do they need more help than we can give... > > >> I be

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

On Tue, Apr 14, 2015 at 7:02 AM, Miguel Angel Ajo Pelayo < mangel...@redhat.com> wrote: > Why would operators install from devstack? that’s not going to be the case. > If they do they need more help than we can give... > I believe we should have both LB & OVS well tested, if LB is a good option

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

> On 10/4/2015, at 20:10, Kyle Mestery wrote: > > On Fri, Apr 10, 2015 at 1:03 PM, Sean M. Collins > 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