Reference IPAM driver
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:
- 7.0.0
- Started by
- Kyle Mestery
- Completed by
- Kyle Mestery
Related branches
Related bugs
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:/
Addressed by: https:/
Specification for reference IPAM driver
Gerrit topic: https:/
Addressed by: https:/
Introduce External IPAM Interface
Addressed by: https:/
wip ipam reference driver
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Merge remote-tracking branch 'origin/master' into merge-branch
Addressed by: https:/
Merge remote-tracking branch 'origin/master' into merge-branch