Name |
Last commit
|
Last update |
---|---|---|
.. | ||
cloud | ||
commands | ||
database | ||
files | ||
internal | ||
inventory | ||
messaging | ||
monitoring | ||
net_infrastructure | ||
network | ||
notification | ||
packaging | ||
source_control | ||
system | ||
utilities | ||
web_infrastructure |
For networks that have both a v4 and a v6 subnet, the floating IP plugin currently has two problems: * When determining the subnet for the provided `internal_network_name`, it assumes that the first item in the list of subnets is the one you want. Instead, it should pick the first v4 subnet. * When multiple fixed IP's exist for a given port (as is the case in a network a v4 and a v6 subnet), neutron needs a hint as to which fixed IP to associate to the floating IP address (the v4 one).
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
cloud | Loading commit data... | |
commands | Loading commit data... | |
database | Loading commit data... | |
files | Loading commit data... | |
internal | Loading commit data... | |
inventory | Loading commit data... | |
messaging | Loading commit data... | |
monitoring | Loading commit data... | |
net_infrastructure | Loading commit data... | |
network | Loading commit data... | |
notification | Loading commit data... | |
packaging | Loading commit data... | |
source_control | Loading commit data... | |
system | Loading commit data... | |
utilities | Loading commit data... | |
web_infrastructure | Loading commit data... |