[ovs-dev] [PATCH] ovs-xapi-sync: Handle multiple xs-network-uuids for xs 6.1.

[Gurucharan Shetty]

On Tue, May 21, 2013 at 6:27 AM, Zoltan Kiss <zoltan.kiss at citrix.com> wrote:

> Hi,
>
> Can you explain a little bit what was the effect of this bug for you? What
> kind of problems you have seen?
>
For proper integration of Open vSwitch with controllers such that
controllers get the state of the Hypervisor in question is by setting the
external_ids column in different Open vSwitch tables (This is explained in
more detail in the IntegrationGuide file). For the bridge table, the
external_ids column to set is "bridge_id".  This should contain information
that uniquely identifies a bridge. For XenServer 6.1, we ended up in a
state where external_ids:bridge_id was being populated with a value that
identifies a VLAN network instead of the regular bridge network. This broke
the integration with a controller.

Thanks,
Guru




>
> Regards,
>
> Zoli
>
>
> On 20/05/13 15:56, Gurucharan Shetty wrote:
>
>> For xenservers with version less than 6.1, interface reconfiguration
>> happened through interface-reconfigure scripts in this repo. In cases
>> where there were multiple xs-network-uuids for a single bridge,
>> interface-reconfigure script would add the network uuid associated
>> with the non-VLAN network as the first record. ovs-xapi-sync would
>> just blindly use the first record to create the bridge-id
>>
>> But it looks like for xenserver 6.1, interface-reconfigure script
>> is no longer used and xenserver natively writes the xs-network-uuids.
>> So, in ovs-xapi-sync we no longer can copy the first value in
>> xs-network-uuids as bridge-id. This commit fetches the PIF record
>> for each xs-network-uuids and the network that does not have a VLAN
>> associated with it is copied over to bridge-id.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-dev/attachments/20130521/0e4ab48f/attachment-0003.html>