Use Pecan for v3 API routing
Use Pecan instead of the custom wsgi code for the V3 REST API routing.
Blueprint information
- Status:
- Started
- Approver:
- Dan Smith
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Ryan Petrello
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Slow progress
- Milestone target:
- None
- Started by
- Russell Bryant
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Discussed at mid-cycle meetup - this is deferred to Juno
Chris, I assigned this to you but I'm pretty sure someone else is doing the work. Please re-assign as appropriate. --russellb
Gerrit topic: https:/
Addressed by: https:/
Add the ability to define API extensions as pecan controllers.
Unapproved - please re-submit via nova-spec --johnthetubagy (20th March 2014)
Removed from next, as next is now reserved for near misses from the last milestone --johnthetubagu
Chris, I assigned this to you but I'm pretty sure someone else is doing the work. Please re-assign as appropriate. --russellb
Gerrit topic: https:/
Addressed by: https:/
Add the ability to define API extensions as pecan controllers.
Unapproved - please re-submit via nova-spec --johnthetubagy (20th March 2014)
Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy
Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
