Hanish,
I have observed this behavior as well. Without digging in to recall
the details, I believe that when the DHCP agent restarts, it makes a
call that schedules any unscheduled networks to it. Upon scheduling
the network to the agent, the port is created by the agent.
Without restarting the DHCP agent, the normal behavior is to wait
until a VM port is spawned on the network to schedule the network to
an agent.
I think the answer to your question is that this is expected but may
be surprising to some.
Carl
On Thu, Mar 27, 2014 at 6:30 AM, hanish gogada
hanishgogada...@gmail.com wrote:
Hi all,
I tried out the following scenario on openstack grizzly, i created a network
and subnet on it. I attached this subnet to the router ( i did not launch
any vms on it). I restarted l3 and dhcp agent, this created a dhcp port on
that network. Though there is no functionality breakage, Is this behavior
expected.
thanks regards
hanish
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
