Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/neutron-ipam. Description: Currently most (if not all) Neutron plugins leverage an IPAM implementation that is embedded in the db_plugin base implementation. While this works well in a self contained system, it makes it difficult to integrate with an external IPAM backend. The proposal is to hash out an IPAM interface derived from the existing IPAM-related interfaces defined in the db_plugin and refactor the current implementation into a configurable IPAM driver. One can then envision implementing and configuring additional independent drivers to external IPAM backends as well. Specification URL (additional information): None
Customers have a requirement to integrate OpenStack into their existing infrastructure that uses external IPAM system. This feature introduces a new pluggable IPAM framework into Neutron. While the reference implementation remains the same, customers can now plug-in an external IPAM system. RHEL OpenStack Platform customers who do not use third party IPAM solutions are not affected by this feature.
this is a test only bug, to understand the quality of this feature. Note that when using pluggable IPAM you should configure the default driver based on dnsmasq.
Moving to OSP 9, will need retesting.