Take advantage of the new BDM format when attaching volumes

Registered by Nikola Đipanov

As part of the havana blueprint improve-block-device-handling we added some data that can be associated with the volume. We can now use this data when attaching volumes (not only when booting). Several things will need to be done.

* 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

Joe Gordon
Nikola Đipanov
Nikola Đipanov
Series goal:
Accepted for icehouse
Milestone target:
milestone icon 2014.1
Started by
Nikola Đipanov
Completed by
John Garbutt

Related branches



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.com/2013/09/17/openstack-docimpact-flag-walk-through/ somewhere in this BP or commit messages to help the docs team. --jogo

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://review.openstack.org/63826
    Allow driver BDM attach() to skip attached check

Addressed by: https://review.openstack.org/63827
    Make volume attach use objects

Addressed by: https://review.openstack.org/66373
    Add device bus and type to virt attach_volume call

Addressed by: https://review.openstack.org/66374
    Use disk_bus and device_type in attaching volumes

Gerrit topic: https://review.openstack.org/#q,topic:bdm_objects_attach,n,z


Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.


No subscribers.