Skip to main content
NetApp Knowledge Base

How does Openstack provision disks when using Solidfire backing storage

  1. Last updated
  2. Save as PDF
Views:
108
Visibility:
Public
Votes:
0
Category:
openstack
Specialty:
VIRT
Last Updated:

Applies to

  • Openstack
  • SolidFire

Answer

Openstack volumes are created using thin-provisioning by default.

You cannot choose the provisioning disk type at deployment time. The provisioning disk type is inherited from the image template:
  • If the template is created with a thin-provisioned disk, the instances that are deployed from that template are thin-provisioned.
  • If the template is created with a thick-provisioned disk, the instances that are deployed from that template are thick-provisioned.

SolidFire volumes are also created using thin-provisioning by default.

  • Space is consumed on write but only after passing through a series of inline data reduction processes within the SolidFire cluster.
  • The SolidFire Cinder driver does not comply with the Cinder over-subscription framework and the SolidFire cluster maintains total control over space usage.
  • SolidFire free space is considered during Cinder volume creation; free space is predicted upon used space rather than allocated space.

 

Additional Information

additionalInformation_text

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.