[ml2][ovs] allow multiple physical networks map to one physical ovs bridge
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
In real cloud production environment, there are many hosts, which can access external network, which may not. Some have enough NICs to work for different networks, while some are lack of NICs.
For instance, an external network, provider:
While tenant network, provider:
So for neutron's limitation, in one single host, you have to add two ovs-bridges which are mapping external->br-ex, user->br-usr. And br-ex adds physical port eth0, br-usr adds eth1.
But, in real world, these vlans can work in same physical nic, and physical hosts may be lack of NICs, which means, Neutron should allow set bridge mapping like this:
{"external": br-vlan, "user": br-vlan}
Then, for those hosts with only one NIC (or one bond NIC), can work for both physical types of network.
You may say, may be we can set one network with two types of "provider:
Any ideas?
summary: |
- [ml2][ovs] allow physical map to one physical ovs bridge + [ml2][ovs] allow multiple physical networks map to one physical ovs + bridge |
description: | updated |
Thus "physical_network" would effectively mean "logical" network. Doesn't it contradict with "physical network" meaning? IMO it will bring inconsistency into already complex provider networks logic.