Port heat api to pecan and wsme
Registered by
Angus Salkeld
Lets use a more evolved wsgi framework that can natively handle xml/json/++ content types.
Ceilometer has been using this for a while without problems.
One issue is to see how it deals with AWS style apis.
The advantage to using this is less code that we need to maintain within heat and openstack.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Angus Salkeld
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Steve Baker
Related branches
Related bugs
Sprints
Whiteboard
(stevebaker) If and when we implement heat REST API v2, we should consider implementing it with pecan/wsme. However porting v1 to pecan/wsme is not a good use of resources.
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
