IPAM extensions for Neutron
A high-level detail of the proposed extensions for IPAM resources
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Rudra Rugge
- Direction:
- Needs approval
- Assignee:
- Rudra Rugge
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
-
Started
- Milestone target:
-
next
- Started by
- Rudra Rugge
- Completed by
- Armando Migliaccio
Related branches
Related bugs
Sprints
Whiteboard
27-Oct (markmcclain): Many of the proposed attributes already exist in the subnet resource. Before proceeding further, the current limitations and the expected outcome of the change needs to be detailed.
28-Oct (hnakil): Agreed, However IPAM is supposed to be manager for related subnets. When we create a network we just need to assign a prefix or set of prefix and no other attributes. Even better would be that in most cases actual prefix management of the subnet can be automatic. As long as related subnets agree on set of allowed ip CIDRs. Address space within CIDRs can be managed similar memory management.
IPAM actually allows you to group related subnets that belong to different but related networks and check for overlapping ip address and other mistakes.
Current subnet structures, though it has similar attributes, is associated with single network. networks never work in isolation and we need management hierarchy.
2014-05-22 (carl_baldwin) - We are starting some work on making IPAM pluggable in Neutron (https:/
