In Neutron IP address management and distribution are separated concepts. IP addresses are assigned to ports even when DHCP is disabled. That IP address is indeed used to configure anti-spoofing rules and security groups.
It is however understandable that one wonders why an IP address is assigned to a port if there is no DHCP server to communicate that address. Operators might decide to use different tools to ensure the IP address is then assigned to the instance's ports. On XenServer for instance one could use a guest agent reading network configuration from XenStore; as another example, older versions of Openstack used to inject network configuration into the instance file system; I reckon that today's configdrive might also be used to configure instance's networking. Summarising I don't think this is a bug. Nevertheless if you have any idea regarding improvements on the API UX feel free to file a bug report. Salvatore On 16 December 2014 at 10:41, Pasquale Porreca < pasquale.porr...@dektech.com.au> wrote: > > Is there a specific reason for which a fixed ip is bound to a port on a > subnet where dhcp is disabled? it is confusing to have this info shown > when the instance doesn't have actually an ip on that port. > Should I fill a bug report, or is this a wanted behavior? > > -- > Pasquale Porreca > > DEK Technologies > Via dei Castelli Romani, 22 > 00040 Pomezia (Roma) > > Mobile +39 3394823805 > Skype paskporr > > _______________________________________________ > OpenStack-dev mailing list > OpenStackemail@example.com > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev