2aa23de58f
Original problem is that dhcp_release does not work with IPv6, but IPv6 leases still should be released. For example: 1. Start VM in dhcpv6-stateful network, make it acquire IPv6 address. 2. Delete VM. 3. Start another VM in same network before lease expires. There's a very high chance that the same IPv6 address will be allocated for both of these VMs (same address will be reused after first VM was deleted). On DHCP agent, hosts file would be changed, but not lease file, so dnsmasq will not give second VM address until lease expires. Reducing lease time is not a good solution here. Solution is adding invocation of dhcp_release6 utility when releasing IPv6 address. dhcp_release6 utility appears in dnsmasq 2.76. It crafts DHCP6_Release packet, sends it from passed network interface to IPv6 multicast address and waits for DHCP6_Reply. Closes-Bug: 1521666 Change-Id: I5efab81cdaf0676503b6c7da0d4b4f400d859286
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 git.openstack.org at <http://git.openstack.org/cgit/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
- Networking Guide
- Neutron API Reference:
-
http://docs.openstack.org/api/openstack-network/2.0/content/
- Current Neutron developer documentation is available at:
For help on usage and hacking of Neutron, please send mail to <mailto:openstack-dev@lists.openstack.org>.
For information on how to contribute to Neutron, please see the contents of the CONTRIBUTING.rst file.