Virtualization Driver Cleanup
The nova.virt drivers currently aren't fully dynamic and use the connection_type and a static list of known drivers in loading. We should clean this up so that drivers are fully dynamically loaded using the openstack commons importutils, and let users specify drivers by class name in nova.conf. Additional cleanup and refactoring of the virt drivers will be done to make driver class naming consistent and predictable.
Blueprint information
- Status:
- Complete
- Approver:
- Vish Ishaya
- Priority:
- Low
- Drafter:
- Sean Dague
- Direction:
- Approved
- Assignee:
- Sean Dague
- Definition:
- Approved
- Series goal:
- Accepted for folsom
- Implementation:
-
Implemented
- Milestone target:
-
2012.2
- Started by
- Sean Dague
- Completed by
- Sean Dague
Related branches
Related bugs
Sprints
Whiteboard
Proposed path forward from email list discussion and initial prototype:
a) remove get_connection from the drivers (and just have it construct the 'connection' class directly)
b) modify the global get_connection to construct the drivers for backwards compatibilty
c) modify the documentation to suggest changing drivers by specifying the full path to the driver instead of connection_type
d) rename the connection classes to something reasonable representing drivers (libvirt.
e) bonus points if it could be done with a short path for ease of use (compute_
Gerrit topic: https:/
Addressed by: https:/
convert virt drivers to fully dynamic loading
Addressed by: https:/
add unit tests for new virt driver loader
Addressed by: https:/
refactor libvirt from connection -> driver
Addressed by: https:/
update importutils from openstack-common
Addressed by: https:/
use import_object_ns for compute_driver loading
Addressed by: https:/
refactor vmwareapi_conn => vmwareapi/driver
Addressed by: https:/
refactor xenapi/connection => xenapi/driver
Addressed by: https:/
refactor baremetal/proxy => baremetal/driver
Addressed by: https:/
flags documentation to deprecate connection_type
