[ovs-discuss] OVN external network access in Openstack

Michael Kashin mmkashin at gmail.com
Thu Nov 17 14:44:03 UTC 2016


I'm using stable/newton, not master. Is master networking-ovn backwards
compatible with newton version of Neutron or do I need to get ocata Neutron
as well?


On 17 November 2016 at 14:09, Joel Wirāmu Pauling <joel at aenertia.net> wrote:

> Why not just use ECMP for the gateway pool?
>
> On 17 November 2016 at 08:47, Russell Bryant <russell at ovn.org> wrote:
>
>>
>>
>> On Wed, Nov 16, 2016 at 12:38 PM, Michael Kashin <mmkashin at gmail.com>
>> wrote:
>>
>>> Greetings,
>>>
>>> I'm integration RDO (Packstack) Openstack with OVN and facing a problem
>>> connecting DVR to external networks. My setup consists of a couple of
>>> virtual networks and a router interconnecting them.  On each compute node
>>> I've create a "br-ex" and created a mapping "ovn-bridge-mappings=extnet:br-ex".
>>> I've also created a neutron network with "--provider:physical_network
>>> extnet" and assigned this network as a gateway to my router. I can see that
>>> OVN northDB creates a new LS with two ports as expected:
>>>
>>>  switch 151ac068-ee99-4324-b785-40709b2e2061
>>> (neutron-b4786af5-cf70-4fc2-8f36-e9d540165d37)
>>>
>>>         port provnet-b4786af5-cf70-4fc2-8f36-e9d540165d37
>>>
>>>             addresses: ["unknown"]
>>>
>>>         port fb73ca73-488f-40aa-89e1-e8e312de7a77
>>>
>>>             addresses: ["fa:16:3e:1d:75:66 169.254.0.50"]
>>>
>>> However, I can't see any link between my DVR and this LS. Am I expected
>>> to create a DVR-to-extLS patch manually?
>>>
>> What version of networking-ovn are you using?  To do this, you need
>> networking-ovn from master (ocata).
>>
>>> Can you also clarify one more thing. I've seen the setting for L3
>>> gateway scheduling which, I assume, should place that external router IP
>>> (169.254.0.50 in my case) on a particular compute node. Is there any
>>> document that describes what happens during GW scheduling?
>>>
>> Right now scheduling is primitive.  It uses a "least loaded" scheduling
>> policy to distribute gateways among the available chassis.  There are some
>> obvious enhancements that need to be made.
>>
>> 1) We need to be able to specify only a subset of hosts that should be
>> used as gateways.
>>
>> 2) We need some HA capabilities to handle when a host handling a gateway
>> goes down.
>>
>> --
>> Russell Bryant
>>
>> _______________________________________________
>> discuss mailing list
>> discuss at openvswitch.org
>> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20161117/0a152d2b/attachment.html>


More information about the discuss mailing list