[ovs-dev] [RFC v2 02/11] ovn: Add bridge mappings to ovn-controller.

Russell Bryant rbryant at redhat.com
Mon Jul 20 15:36:51 UTC 2015


On 07/17/2015 10:53 AM, Russell Bryant wrote:
> On 07/16/2015 07:56 PM, Ben Pfaff wrote:
>> On Thu, Jul 16, 2015 at 04:55:11PM -0700, Ben Pfaff wrote:
>>> On Thu, Jul 16, 2015 at 06:06:10PM -0400, Russell Bryant wrote:
>>>> Add a new OVN configuration entry in the Open_vSwitch database called
>>>> "ovn-bridge-mappings".  This allows the configuration of mappings
>>>> between a physical network name and an OVS bridge that provides
>>>> connectivity to that network.
>>>>
>>>> For example, if you wanted to configure "physnet1" to map to "br-eth0"
>>>> and "physnet2" to map to "br-eth1", the configuration would be:
>>>>
>>>>   $ ovs-vsctl set open . \
>>>>   > external-ids:ovn-bridge-mappings=physnet1:br-eth0,physnet2:br-eth1
>>>>
>>>> In this patch, the configuration option is only parsed and validated
>>>> to make sure the referenced bridges actually exist.  Later patches
>>>> will make use of the bridge mappings.
>>>>
>>>> Signed-off-by: Russell Bryant <rbryant at redhat.com>
>>>
>>> Do later patches add documentation?  That will be important.
>>>
>>> I wonder whether we should document the ovn configuration external-ids
>>> in vswitch.xml, or whether that would indicate too intimate a
>>> relationship between OVN and OVS.x

Oops, I forgot to respond to this comment.

I didn't add the docs here because as you point out, we don't actually
have the ovn-controller configuration values documented anywhere yet, so
there wasn't a good place to put it.

Later in the patch series this is mentioned in the docs for the
"localnet" logical port type in the ovn schema docs.  It's at the end of:

http://openvswitch.org/pipermail/dev/2015-July/057641.html

It feels like we need a "OVN admin guide" that talks about configuring
and running OVN.  I can start working on something like that.

-- 
Russell Bryant



More information about the dev mailing list