neutron

OVS plugin on different bridges and nova networks

Asked by Salvatore Orlando

Hi,

I have deployed the Open vSwitch plugin on a testbed with several compute nodes.
The integration bridge created by the plugin agent is not the same on each host (this can be expected as xapi decides the name for the bridge).

In my deployment, the integration bridges are created as follows:

HOST BRIDGE
---------------------------------------------------
xen-01 xapi1
xen-02 xapi2
xen-03 xapi11

Unfortunately in the networks table in nova db it is possible to specify only a single bridge for the network (e.g.: xapi1).
Doing so implies that if the scheduler dispatches the instance create operation to either xen-02 the operation will fail with a 'NotFound: No network for bridge xapi2' error (a similar error occurs when the operation is dispatched to xen-03).

Is there a way to avoid this issue? I could use a distinct record in the network table for each integration bridge, but it does not look like a viable solution.

Thanks,
Salvatore

Question information

Language:
English Edit question
Status:
Solved
For:
neutron Edit question
Assignee:
No assignee Edit question
Solved by:
Salvatore Orlando
Solved:
Last query:
Last reply:
Revision history for this message
Salvatore Orlando (salvatore-orlando) said : 		#1

Addendum: By the way I was trying to run the plugin on multiple nodes even know it seems this feature is not supported at the moment as there's no uplink port on the integration bridges.
I manually added an eth device using ovs cli utilities in dom0.

Revision history for this message
Brad Hall (bgh) said : 		#2

We were talking about setting something standard in the name-label (or some other attribute) for the network so that we could easily find the integration bridge. This creates another step for the user (to set the label if they've already created the bridge) but it would probably make it easier than it is now.

Revision history for this message
Salvatore Orlando (salvatore-orlando) said : 		#3

I too like the idea of using attributes different by 'bridge'. For xenapi we could use name-label or other-config; however it will be probably better to first have a look at all the hypervisors the plugin will support and then take a decision.

In nova-network, for the xenapi VLAN manager driver we currently use the name-label attribute, setting it to the value in the 'bridge' column in the networks table in nova db.

Revision history for this message
Salvatore Orlando (salvatore-orlando) said : 		#4

I think we can now close this question