[openstack-dev] Proposal for dd disk i/o performance blueprint of cinder.

CARVER, PAUL pc2929 at att.com
Wed Jan 15 22:59:44 UTC 2014

Chris Friesen [mailto:chris.friesen at windriver.com] wrote:

>I read a proposal about using thinly-provisioned logical volumes as a 
>way around the cost of wiping the disks, since they zero-fill on demand 
>rather than incur the cost at deletion time.

I think it make a difference where the requirement for deletion is coming from.

If it's just to make sure that a tenant can't read another tenant's disk then what
you're talking about should work. It sounds similar (or perhaps identical to) how
NetApp (and I assume others) work by tracking whether the current client has
written to the volume and returning zeros rather than the actual contents of the
disk sector on a read that precedes the first write to that sector.

However, in that case the previous client's bits are still on the disk. If they were
unencrypted then they're still available if someone somehow got ahold of the
physical disk out of the storage array.

That may not be acceptable depending on the tenant's security requirements.

Though one may reasonably ask why they were writing unencrypted bits to
a disk that they didn't have physical control over.

More information about the OpenStack-dev mailing list