No way to describe block-size info

Bug #1196248 reported by John Griffith on 2013-06-30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
John Griffith

Bug Description

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:

tags: added: grizzly-backport-potential

Fix proposed to branch: master

Changed in cinder:
status: Triaged → In Progress

Fix proposed to branch: master

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

Changed in cinder:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2013-07-17
Changed in cinder:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2013-10-17
Changed in cinder:
milestone: havana-2 → 2013.2
Alan Pevec (apevec) on 2014-03-31
tags: removed: grizzly-backport-potential
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers