Reference IPAM driver

Registered by Salvatore Orlando on 2014-12-03

This blueprint is the first step of a series aimed at making IPAM an independent component of Neutron.
The aim of this blueprint is to move the current IPAM code, mostly as-it-is, into a driver accessed through a well-defined IPAM interface.

Code changes to the IPAM logic should be avoided as possible. However enhancement should not be disregarded if they can be achieved with minimal effort.

Blueprint information

Status:
Complete
Approver:
Kyle Mestery
Priority:
Essential
Drafter:
Salvatore Orlando
Direction:
Approved
Assignee:
Salvatore Orlando
Definition:
Approved
Series goal:
Accepted for liberty
Implementation:
Implemented
Milestone target:
milestone icon 7.0.0
Started by
Kyle Mestery on 2015-02-13
Completed by
Kyle Mestery on 2015-07-24

Related branches

Sprints

Whiteboard

March-24 (mestery): Moving to Liberty.

March-18 (mestery): FFE for Kilo, and moving to essential and RC1.

December-22 (mestery): I'm like Santa Claus, so marking this as Kilo-3.

Gerrit topic: https://review.openstack.org/#q,topic:reference-ipam-driver,n,z

Addressed by: https://review.openstack.org/138803
    Specification for reference IPAM driver

Gerrit topic: https://review.openstack.org/#q,topic:bp/reference-ipam-driver,n,z

Addressed by: https://review.openstack.org/134339
    Introduce External IPAM Interface

Addressed by: https://review.openstack.org/150485
    wip ipam reference driver

Gerrit topic: https://review.openstack.org/#q,topic:bp/neutron-ipam,n,z

Gerrit topic: https://review.openstack.org/#q,topic:bug/1468828,n,z

Addressed by: https://review.openstack.org/196701
    Merge remote-tracking branch 'origin/master' into merge-branch

Addressed by: https://review.openstack.org/196920
    Merge remote-tracking branch 'origin/master' into merge-branch

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.