No DB Messaging
Right now, the communication between components in Nova occurs through rpc.cast and rpc.call (which uses rabbitMQ to pass messages). In many cases we only pass the id of the object in the message, and the component on the other end looks up the object in the database. This means we are essentially using the database to pass data between components
In preparation for separating the services into separate projects, it is important that we make sure that all relevant data is passed between components in the message. This will pave the way for the different components to have separate databases.
Blueprint information
- Status:
- Complete
- Approver:
- Vish Ishaya
- Priority:
- High
- Drafter:
- Nova Scaling Team
- Direction:
- Approved
- Assignee:
- Russell Bryant
- Definition:
- Approved
- Series goal:
- Accepted for folsom
- Implementation:
-
Implemented
- Milestone target:
-
2012.2
- Started by
- Russell Bryant
- Completed by
- Russell Bryant
Related branches
Related bugs
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Fix rpc error with live_migration.
Work Items
Dependency tree

* Blueprints in grey have been implemented.