Pluggable network providers
Today, Ironic provisions servers on the same (flat) network that tenants run on. Ironic should have the ability to logically separate provisioning and tenant networks, and switch between them as needed.
Blueprint information
- Status:
- Started
- Approver:
- aeva black
- Priority:
- High
- Drafter:
- Jim Rollenhagen
- Direction:
- Approved
- Assignee:
- Jim Rollenhagen
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
-
Needs Code Review
- Milestone target:
- None
- Started by
- aeva black
- Completed by
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add pluggable network provider spec
Addressed by: https:/
Add network provider interface and implementations
Addressed by: https:/
Add driver and driver_info fields to Port
Addressed by: https:/
Add portgroups to support LAG interfaces - RPC
Addressed by: https:/
Add portgroups to support LAG interfaces - API
Addressed by: https:/
Add portgroups to support LAG interfaces - net
Addressed by: https:/
Add portgroups to support LAG interfaces - DB
Addressed by: https:/
Add portgroups to support LAG interfaces - objs
Addressed by: https:/
Update network provider spec
Gerrit topic: https:/
Addressed by: https:/
Update the deploy drivers with network flipping logic
Gerrit topic: https:/
We're moving from using blueprints to track features to RFE bugs. vdrok filed one for your change (see above). Please track further work there using Closes-Bug, Partial-Bug or Related-Bug in commit messages and use this newly created RFE bug.
//rloo 2015-12-15
Gerrit topic: https:/
