> Your question makes me think that you are using provider networks > in a way different from I have used them
Actually it is standard Q_USE_PROVIDER_NETWORKING=True PHYSICAL_NETWORK=providernet PROVIDER_NETWORK_TYPE=flat OVS_PHYSICAL_BRIDGE=br-provider PROVIDER_SUBNET_NAME=provider-subnet FIXED_RANGE=10.145.253.0/24 NETWORK_GATEWAY=10.145.253.1 ALLOCATION_POOL=start=10.145.253.111,end=10.145.253.242 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?
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
