95dbd03a0b
Having 2 separate dhcp lease period flags (dhcp_lease_duration used by the quantum db plugin, and dhcp_lease_time used by the dnsmasq dhcp agent) means that you could potentially have different lease periods being set, and used by different parts of the codebase. It seems to me there is no real need to have 2 separate flags, so this commit basically replaces references to dhcp_lease_time (which is used by the dnsmasq dhcpagent) with dhcp_lease_duration. This way, there is only one flag to set, and both the quantum db plugin and dnsmasq dhcp agent will use the same lease period. Change-Id: Ia99dfa9284b6e737144f61a80c59cd898c0949bb Fixes: bug #1192550
# -- Welcome!
You have come across a cloud computing network fabric controller. It has identified itself as "Quantum." It aims to tame your (cloud) networking!
# -- External Resources:
The homepage for Quantum is: http://launchpad.net/quantum . Use this site for asking for help, and filing bugs. Code is available on github at <http://github.com/openstack/quantum>.
The latest and most in-depth documentation on how to use Quantum is available at: <http://docs.openstack.org>. This includes:
Quantum Administrator Guide http://docs.openstack.org/trunk/openstack-network/admin/content/
Quantum 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/QuantumDevelopment
For help using or hacking on Quantum, you can send mail to <mailto:openstack-dev@lists.openstack.org>.