New messaging API
Before any API can move out of "incubation" in openstack-common, we should be confident in our ability to evolve the API and implementation without breaking backwards compatibility.
To gain this confidence, we should carefully review each of the exposed public interfaces to be sure it makes long term sense.
Things to watch out for:
* Implementation details exposed in the API
* cfg options which may not make sense long term
* Unused APIs
* API design which makes future additions difficult
Blueprint information
- Status:
- Complete
- Approver:
- Mark McLoughlin
- Priority:
- High
- Drafter:
- Mark McLoughlin
- Direction:
- Approved
- Assignee:
- Mark McLoughlin
- Definition:
- Approved
- Series goal:
- Accepted for havana
- Implementation:
-
Implemented
- Milestone target:
-
2013.2
- Started by
- Mark McLoughlin
- Completed by
- Mark McLoughlin
Related branches
Related bugs
Sprints
Whiteboard
I think 1.2.0a3 is pretty much feature complete for Havana, but it's not well tested aside from unit tests at this stage
http://
---
Latest version here: https:/
---
Detailed writeup : https:/
etherpad: https:/
---
First cut proposal of the API structure https:/
Settled on targeting this to havana-2 at this meeting http://
---
I'm filing bugs tagged with rpc-api-review - https:/
---
Projects currently using the RPC API - nova, cinder, quantum, ceilometer, heat
Some notes/questions:
* Why isn't glance importing rpc for notifiers?
* create_worker() is only used by ceilometer - is it generic enough?
---
WIP patch to port Nova to the new API: https:/
Work Items
Dependency tree
* Blueprints in grey have been implemented.
