XenServer: XenAPI Refactoring (initial steps)
It would make the code easier to maintain if we can have a clear separation between:
* xenapi client
* compute driver logic
This will help move the client into oslo to be shared with other projects.
At the same time, we should fix up and uses of expensive methods, like get_record, that can be moved to things like get_domid and similar. This should help the performance of the XenAPI driver. The worst offenders have already been merged.
Blueprint information
- Status:
- Complete
- Approver:
- Joe Gordon
- Priority:
- Low
- Drafter:
- John Garbutt
- Direction:
- Approved
- Assignee:
- John Garbutt
- Definition:
- Approved
- Series goal:
- Accepted for icehouse
- Implementation:
- Implemented
- Milestone target:
- 2014.1
- Started by
- John Garbutt
- Completed by
- John Garbutt
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Merged
======
Addressed by: https:/
xenapi: move session into new client module
Addressed by: https:/
xenapi: make session calls more discoverable
Pending
=======
Addressed by: https:/
Move xenapi/agent.py to new call_xenapi style
Addressed by: https:/
Refactor xenapi/host.py to new call_xenapi pattern
Seems very close to being merged now, all patches have a +2 --johnthetubaguy
Work Items
Work items:
Move session into its own client: DONE
Create structure of helper objects: DONE
Move old code to new format: INPROGRESS