vlan to tenant mapping is broken
The relationship between networks/tenants and vlans in OpenStack networking needs to be redone in general.
At the moment it enables to define private networks on different VLANs and assign them to tenants.
As at the moment quantum seems to support only one network device (eth or bond) for alle networks that's okay ...
... as long as no 2 or more networks are using the same VLAN-ID.
The Problem here is a parent<>child relationship mismatch on bridge level.
If a private network get's assigned to a VM then the Hypervisor Host creates a bridge for the private network on the private networks's VLAN-ID.
If another private network on the same VLAN get's assigned to a VM on the same host, OpenStack will try to create a new bridge and add the same VLAN device to it, which is not possible and fails.
It is at the moment not possible to use multiple networks on the same VLAN - which is quite common in large network installations.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Armando Migliaccio
Related branches
Related bugs
Sprints
Whiteboard
I wonder if:
https:/
Is a step in a similar direction of this one. Since this is so stale, we are left no choice to mark it obsolete.
[gongysh] Are u talking about current quantum implementation?
[baumann] yes
[rkukura] Which plugin(s) are you concerned with? Both openvswitch and linuxbridge do support multiple L2 networks that map to VLANs. Any two of those VLANs can be on the same physical interface or on different physical interfaces. If they are on different physical interfaces, they can have the same VLAN tag, but are still two separate L2 networks. If a plugin allowed two different L2 networks on the same physical interface to have the same VLAN tag, then these would actually be the same L2 network (with no isolation). I'm not sure exactly what you mean by "multiple networks on the same VLAN"? Do you mean multiple L3 subnets on the same L2 network (which may or may not be a VLAN)? If so, I believe that should be supported.
[danwent] what plugin are you using? I suspect based on your description that it is the linux bridge plugin, which may have this limitation. I do not think that other plugins like OVS or NVP would not have a limitation as you describe. Perhaps file this as a bug on the linux bridge plugin?
