No way to describe block-size info

[John Griffith]

currently there's no mechanism in the Volume object to specify it's block-size info. As it stands currently we can't attach and use devices that are not the default 512 blocksize.

We'll need to add a block_size_info column to the Cinder volume object that can store things like logical_block_size and physical_block_size that can be consumed by Nova when performing an attach.

Related Nova bug: https://bugs.launchpad.net/nova/+bug/1195913

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/35217

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/36562

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/36562
Committed: http://github.com/openstack/cinder/commit/67078ab9329b8f3d844b033b4d64cf2bdcf6bab7
Submitter: Jenkins
Branch: master

commit 67078ab9329b8f3d844b033b4d64cf2bdcf6bab7
Author: John Griffith <email address hidden>
Date: Wed Jul 10 15:34:26 2013 -0600

    Enable setting blocksize on volumes.

    Some back-ends support blocksizes other than the default 512 (like 4096),
    this change adds a provider_geometry column to the volumes table,
    format is "physical_block_size logical_block_size".

    This can then be used by libvirt to determine if it should pass in
    non-default block_size info, and there's a method for future
    geometry/disk info that might be needed.

    Fixes bug: 1196248

    Change-Id: I8d40bc56403154fbe955cd4ccf8f0c55fc9eb7c5