Re: [Openstack] Moving from Legacy with GRE to Provider with Linux bridge

2016-01-07 Thread Tyler Couto
also failing to bind. Sent from my android device. -Original Message- From: Matt Kassawara To: Tyler Couto Cc: "openstack@lists.openstack.org" Sent: Thu, 07 Jan 2016 10:43 AM Subject: Re: [Openstack] Moving from Legacy with GRE to Provider with Linux bridge Do your a

Re: [Openstack] Moving from Legacy with GRE to Provider with Linux bridge

2016-01-07 Thread Tyler Couto
AM, "Tyler Couto" wrote: > >>Yes, the deployment worked with OVS + GRE. >> >>> From: Matt Kassawara >>> Date: Wednesday, January 6, 2016 at 10:57 AM >>> To: Tyler Couto >>> Cc: "openstack@lists.openstack.org" >>> Su

Re: [Openstack] Moving from Legacy with GRE to Provider with Linux bridge

2016-01-06 Thread Tyler Couto
ith OVS + GRE. > >> From: Matt Kassawara >> Date: Wednesday, January 6, 2016 at 10:57 AM >> To: Tyler Couto >> Cc: "openstack@lists.openstack.org" >> Subject: Re: [Openstack] Moving from Legacy with GRE to Provider with >>Linux bridge >> >&

Re: [Openstack] Moving from Legacy with GRE to Provider with Linux bridge

2016-01-06 Thread Tyler Couto
Yes, the deployment worked with OVS + GRE. > From: Matt Kassawara > Date: Wednesday, January 6, 2016 at 10:57 AM > To: Tyler Couto > Cc: "openstack@lists.openstack.org" > Subject: Re: [Openstack] Moving from Legacy with GRE to Provider with >Linux bridge >

Re: [Openstack] Moving from Legacy with GRE to Provider with Linux bridge

2016-01-06 Thread Matt Kassawara
Could be a number of things. Did the deployment work with OVS + GRE before you moved to LB with provider networks? On Wed, Jan 6, 2016 at 11:36 AM, Tyler Couto wrote: > Hi all, > > I¹m moving openstack from legacy networking with GRE to provider > networking with linux bridge. I¹m new to Opensta

[Openstack] Moving from Legacy with GRE to Provider with Linux bridge

2016-01-06 Thread Tyler Couto
Hi all, I¹m moving openstack from legacy networking with GRE to provider networking with linux bridge. I¹m new to Openstack so I followed the Kilo installation guide and then decided provider networking would be better suited for our implementation. I¹ve modified neutron.conf, ml2_conf.ini, and d