Provide better user-facing mechanism to choose service capabilities
Neutron currently provides simple way for a user to request specific capabilities of the service. That is done by allowing to specify provider for created service.
We need to improve this way by exposing capabilities rather than exposing vendor/
Blueprint information
- Status:
- Complete
- Approver:
- Kyle Mestery
- Priority:
- High
- Drafter:
- Mark McClain
- Direction:
- Approved
- Assignee:
- Doug Wiegley
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
- Implemented
- Milestone target:
- mitaka-1
- Started by
- Kyle Mestery
- Completed by
- Kyle Mestery
Related branches
Related bugs
Sprints
Whiteboard
Dec-07-2015(armax): fixes and further code went in the Mitaka timeframe, so this is better targeting Mitaka than Liberty.
March-17 (mestery): Out of Kilo.
December-15 (mestery): Kilo-3.
Nice idea. I think we actually need the same things for networks, in fact. See the capabilities proposal from ages ago - https:/
Gerrit topic: https:/
Addressed by: https:/
neutron-
Gerrit topic: https:/
Addressed by: https:/
Flavor Framework implementation
Addressed by: https:/
Flavor Framework implementation
Addressed by: https:/
Introduce flavor framework for advance services
Addressed by: https:/
Flavor Framework implementation
Gerrit topic: https:/
Addressed by: https:/
Merge remote-tracking branch 'origin/master' into merge-branch
Addressed by: https:/
WIP: Fix Neutron flavor framework
Addressed by: https:/
Add flavor option to loadbalancerv2 creation