cc02854357
when a new port is created, the schedule_network in agentschedulers_db is called. Since this network may already be hosted, it will directly return None in dhcp_agent_scheduler, which cause the agentschedulers_db.schedule_network log a warning message. This is really annoying and making users confused. And, real warnings are already addressed in the real scheduler function. which is neutron.scheduler.dhcp_agent_scheduler.ChanceScheduler.schedule by default. Change-Id: I11bdbe47c2cc0fc45fb143970fb6762678bc27e5 Closes-Bug: #1192786
# -- Welcome!
You have come across a cloud computing network fabric controller. It has identified itself as "Neutron." It aims to tame your (cloud) networking!
# -- External Resources:
The homepage for Neutron is: http://launchpad.net/neutron . Use this site for asking for help, and filing bugs. Code is available on github at <http://github.com/openstack/neutron>.
The latest and most in-depth documentation on how to use Neutron is available at: <http://docs.openstack.org>. This includes:
Neutron Administrator Guide http://docs.openstack.org/trunk/openstack-network/admin/content/
Neutron API Reference: http://docs.openstack.org/api/openstack-network/2.0/content/
The start of some developer documentation is available at: http://wiki.openstack.org/NeutronDevelopment
For help using or hacking on Neutron, you can send mail to <mailto:openstack-dev@lists.openstack.org>.