neutron

Local vlan id range is less

Asked by kitty mark

Hello, i am a new quantum fun. I have a question about provision local
vlan of ovs plugin.
Plugin ovs agent can provide 4094 local vlan for local vlan mapping on
integration bridge 'br-int'. But each physical network can have a vlan
range, it may be 1-4094. If compute node has two physical network. Each
physical network vlan range is 1 - 4094. The node supports 4094 * 2
network. Now plugin agent of this node can only provide 4094 local vlan
id for mapping physical network segmentation id(physical vlan id). If i
create other network more than 4094, it will log error "No local VLAN
availabel for net-id=xxxx" . Is it right?

Question information

Language:
English Edit question
Status:
Solved
For:
neutron Edit question
Assignee:
No assignee Edit question
Solved by:
Robert Kukura
Solved:
Last query:
Last reply:
Revision history for this message
yong sheng gong (gongysh) said : 		#1

Yes, I think OVS agent Code in quantum is working this way.

Revision history for this message
Best Robert Kukura (rkukura) said : 		#2

The local VLAN IDs only get allocated when a port on that node needs access to a network. Local VLAN IDs are not allocated for networks that are not used on that node. Therefore, the openvswitch plugin should be able to support simultaneous access to up to 4094 different virtual networks from a single node, but these can be distributed over any number of physical networks (and/or GRE tunnels).

-Bob

Revision history for this message
kitty mark (thesea1982) said : 		#3

Thanks Robert Kukura, that solved my question.