Provide support for remote ipam driver
Latest libnetwork supports pluggable remote ipam driver (seperate from remote network driver). Infrastructure and API for this new pluggable IPAM driver decoupled from the network driver has recently been added to libnetwork and now is part of docker 1.9.0 release. Kuryr must support remote ipam driver apis.
Reference: https:/
Blueprint information
- Status:
- Complete
- Approver:
- Antoni Segura Puimedon
- Priority:
- High
- Drafter:
- vikas choudhary
- Direction:
- Approved
- Assignee:
- vikas choudhary
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- vikas choudhary
- Completed by
- vikas choudhary
Related branches
Related bugs
Sprints
Whiteboard
Considering that with docker 1.9.0 we need to have a IPAM driver, I think this is a very important work item. We need to fist investigate the use of a null IPAM driver and see if that would be adequate.
Vikas> As discussed with Banix over IRC, will start with null ipam driver
Gerrit topic: https:/
Addressed by: https:/
IPAM driver implementation
Gerrit topic: https:/
Addressed by: https:/
Implement /IpamDriver.
Addressed by: https:/
IPAM: Implement /IpamDriver.
Addressed by: https:/
IPAM: Implement /IpamDriver.
Addressed by: https:/
IPAM: Implement /IpamDriver.
Addressed by: https:/
Implement /IpamDriver.
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
[WIP] Add description about the IPAM to devref
Addressed by: https:/
Add Docker pluggable IPAM implementation to Kuryr
Addressed by: https:/
Add Docker pluggable IPAM implementation to Kuryr
Gerrit topic: https:/
