Closed admytren closed 11 years ago
This is an issue for Neutron. The plugin receives the IP from Neutron server.
That is weird, DHCP service running on external network can cause all kinds of headaches in administration. While metadata service accessible from external network could cause a security problem. Is there an openstack issue filed about this problem?
Not that I know of. The DHCP agent takes the first available address in the subnet. He doesn't really care if it's public of not. That's what I can see from the code.
Closing this, there's nothing we can do in the plugin...
Observed this issue with Grizzly/MidoNet 1.1 deployment. A public network creates DHCP ports for metadata service and assigns public IP addresses to it. This causes public IP addresses to be wasted.