No direct DB access by compute manager
The compute manager should not have any direct database calls, but rely on conductor
Blueprint information
- Status:
- Complete
- Approver:
- Russell Bryant
- Priority:
- High
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Dan Smith
- Definition:
- Approved
- Series goal:
- Accepted for grizzly
- Implementation:
-
Implemented
- Milestone target:
-
2013.1
- Started by
- Russell Bryant
- Completed by
- Thierry Carrez
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Move security_group operations in VirtAPI to conductor
Addressed by: https:/
Add VirtAPI tests
Addressed by: https:/
Move remaining aggregate operations to conductor
Addressed by: https:/
Move provider_
Addressed by: https:/
Move agent_build_
Addressed by: https:/
Move block_device_
Addressed by: https:/
Move block_device_
Addressed by: https:/
Move block_device_
Addressed by: https:/
Sync timeutils changes from Oslo
Addressed by: https:/
Move instance_get_*() to conductor
Addressed by: https:/
Move instance_destroy() to conductor
Addressed by: https:/
Move instance_
Addressed by: https:/
Move instance_type_get() to conductor
Addressed by: https:/
Remove system_metadata db calls from compute manager
Addressed by: https:/
Use full instance in virt driver volume usage
Addressed by: https:/
Move vol_usage methods to conductor
Addressed by: https:/
Move migration_
Addressed by: https:/
Move service_get_all operations to conductor
Addressed by: https:/
Get instances from conductor in init_host.
Gerrit topic: https:/
Addressed by: https:/
Move update_
Work Items
Dependency tree

* Blueprints in grey have been implemented.