Open admytren opened 11 years ago
Neutron binds it to this "network:dhcp" , it's not our plugin. Why is it confusing? What would the customer want?
Sorry, maybe confusing is the wrong word. This port is providing metadata service exclusively. So it's weird that it's named "network:dhcp", as it doesn't actually provide any dhcp services. I know Midokura integration works within API constraints, so if you don't feel it's possible to do anything about the port type please feel free to close this issue as wontfix. Ideally the port should be named something like "network:md" or "network:metadata" or simply left without type.
Maybe my comment was not very clear. We don't pick this name, it's Neutron that creates and names this port. We should change the Neutron source code to change that name.
Metadata service is bound to "network:dhcp" port. This is confusing to the end user.