[openstack-dev] [networking-ovn] provider networks

Ryan Moats rmoats at us.ibm.com
Fri Jun 17 17:57:15 UTC 2016

Murali R <muralirdev at gmail.com> wrote on 06/17/2016 12:33:09 PM:

> From: Murali R <muralirdev at gmail.com>
> To: Ryan Moats/Omaha/IBM at IBMUS
> Cc: Ben Pfaff <blp at ovn.org>, discuss <discuss at openvswitch.org>
> Date: 06/17/2016 12:33 PM
> Subject: Re: [ovs-discuss] [ovn] provider networks
> > Your question makes me think that you are using provider networks
> > in a way different from I have used them
> Actually it is standard
> PHYSICAL_NETWORK=providernet
> PROVIDER_SUBNET_NAME=provider-subnet
> ALLOCATION_POOL=start=,end=
> So earlier, probably the full l3 support wasn't there. I made
> changes for logical flow additions in my own repo and use it for
> testing. I had to do a big merge for l3 extensions last night
> because networking-ovn eas expecting some idl extensions in new updates.
> The setup now creates a logical router in OVN and assigns the
> gateway address given above. The gateway should not be used to
> allocate address for OVN router.
> If I create another private network, add a new router attach it to
> public network created, the traffic is hitting my external company
> gateway all the way out. Not sure what is happening. Can I just
> delete the default router1 that the devstack setup created? Looks
> like I may have to do some manual configs to get this setup working.
> Or should I disable OVN_L3 in devstack?

I'm dropping the openvswitch discuss list and adding the openstack
dev list because this is very much now questions for that channel.

Right now, my test cloud is in a state where I can't answer your
question directly, but my memory is that a router should not be
created and if it is, that would be a bug against something...

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160617/40a2505a/attachment.html>

More information about the OpenStack-dev mailing list