Config Drive support in the XenAPI driver
Look at the libvirt driver support for Config Driver, and mirror that ability in the XenAPI driver.
Blueprint information
- Status:
- Complete
- Approver:
- Vish Ishaya
- Priority:
- Medium
- Drafter:
- Citrix OpenStack development team
- Direction:
- Needs approval
- Assignee:
- Michael Still
- Definition:
- Approved
- Series goal:
- Accepted for grizzly
- Implementation:
- Implemented
- Milestone target:
- 2013.1
- Started by
- Vish Ishaya
- Completed by
- Russell Bryant
Related branches
Related bugs
Sprints
Whiteboard
Some steps:
- nova/virt/
- make agent optional in XenAPI
- config drive code should be triggered by the appropriate flag: instance.
- first phase: only vfat type config drive is supported (iso is complicated)
- Use ConfigDriveBuilder to build the raw file
- Create a new VDI with the size of the raw file
- Attach the VDI to compute
- dd all the contents ( the latter steps are implemented for raw image launch )
- As we only implement the vfat route, add a new public method that skips flag check (
FLAGS.config_
Non Happy path:
- Migration
- resize
- try out live migration
Lets use Generate -> ISO -> VDI (more likely to stay secure - more similar)
Gerrit topic: https:/
Addressed by: https:/
Move mkfs from libvirt.utils to utils
Addressed by: https:/
Refactor: move find_guest_agent to xenapi.agent
Addressed by: https:/
xenapi: Add null agent
Addressed by: https:/
Refactor: config drive related functions
Addressed by: https:/
xenapi: refactor: Agent class
Addressed by: https:/
xenapi: Make agent optional
Addressed by: https:/
A first cut at adding configdrive to xenapi.
Work Items
Work items:
Refactor nova/virt/
Make agent optional in XenAPI: INPROGRESS
Add configuration entries for config drive to compute config: TODO
Find the places in libvirt, where configdrive is used: TODO
Config drive behavior during migration, resize: TODO
Config drive behavior during live migration: TODO