Take advantage of the new BDM format when attaching volumes
As part of the havana blueprint improve-
* Add the needed options to the volume-attach API calls in the v3 API
* Make all the attach code paths use the new-format of block devices and not rely on the legacy data format
* Implement the new use of the new format in the libvirt driver.
Blueprint information
- Status:
- Complete
- Approver:
- Joe Gordon
- Priority:
- Low
- Drafter:
- Nikola Đipanov
- Direction:
- Approved
- Assignee:
- Nikola Đipanov
- Definition:
- Approved
- Series goal:
- Accepted for icehouse
- Implementation:
-
Implemented
- Milestone target:
-
2014.1
- Started by
- Nikola Đipanov
- Completed by
- John Garbutt
Related branches
Related bugs
Sprints
Whiteboard
I assume there is no user impact for this right? --jogo
Well - there will be new API bits that I was planning to add only to v3 at this point - but they will be backwards compatible. You will be able to specify all the data that we now have for booting with block devices also when attaching. Not sure if that qualifies as user impact though. --ndipanov
That does sound like a user impact, can you make sure you provide answers to all the questions listed in justwriteclick.
With Icehouse-1 just over two weeks away (December 5th), moving this to Icehouse-2 since it hasn't been started yet. If it does get into Icehouse-1, we can re-target the BP. --jogo
Addressed by: https:/
Allow driver BDM attach() to skip attached check
Addressed by: https:/
Make volume attach use objects
Addressed by: https:/
Add device bus and type to virt attach_volume call
Addressed by: https:/
Use disk_bus and device_type in attaching volumes
Gerrit topic: https:/
Work Items
Dependency tree
* Blueprints in grey have been implemented.
