[ovs-dev] [PATCH v3 05/10] ovn: Add bridge mappings to ovn-controller.
Russell Bryant
rbryant at redhat.com
Tue Jul 28 20:07:49 UTC 2015
On 07/28/2015 04:02 PM, Ben Pfaff wrote:
> On Tue, Jul 21, 2015 at 12:59:15PM -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.
>>
>> Documentation for this configuration value is introduced in a later
>> patch that makes use of this by introducing a "localnet" logical port
>> type.
>>
>> Signed-off-by: Russell Bryant <rbryant at redhat.com>
>
> This seems reasonable but one of the things I'm trying to do with my
> tunnel key series is to eliminate the multiple phases of startup in
> ovn-controller, where first it gets the configuration and then later
> uses the configuration. Do you think it would be possible to use that
> approach here too?
>
Thanks, that's good feedback. I did this before I saw your series. I'll
rework this on top of the stuff you've done.
--
Russell Bryant
More information about the dev
mailing list