Open Stack

  Hello,I have a question regarding the enable_dhcp option when creating a network. 

When a VM is attached to  a network where enable_dhcp is False, I understand that the DHCP namespace is not created for the network and the VM does not get any IP address after it boots up and sends a DHCP Discover.But, I also see that the Neutron port is filled with the fixed IP value from the network pool even though there's no DHCP associated with the subnet. So, for such VM's, does one need to statically configure the IP address with whatever Neutron has allocated from the pool?
What exactly is the use case of the above? 
I do understand that for providing public network access to VM's, an external network is generally created with enable-dhcp option set to False. Is it only for this purpose?
I was thinking of a case of external/provider DHCP servers from where VM's can get their IP addresses and when one does not want to use L3 agent/DVR. In such cases, one may want to disable DHCP when creating networks.  Isn't this a use-case?
Appreciate any response or corrections with my above understanding.

Thanks,Paddu  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141217/3ddcf1d7/attachment.html>