Skip to main content
NetApp Knowledge Base

Openstack: Notes on enabling image-volume cache for Solidfire and ONTAP

Last Updated:

Applies to

  • Openstack
  • Element OS


This article was written to supplement the current Openstack documentation on how to implement Image-Volume cache for Cinder. The value of implementing image volume cache is:

  • To keep Cinder from having to repeatedly download the same image over again when provisioning
  • To significantly improve how long it takes to provision a new Cinder volume that is based on a image
  • To decrease overhead on the Openstack Controller

Note: Solidfire has a legacy image-caching option which is now deprecated:sf_allow_template_caching

  • 'sf_allow_template_caching' was a caching option that was implemented prior to the general cinder image-caching feature being developed.
  • Support for 'sf_allow_template_caching' ended with the Rocky release
  • For Openstack releases after Rocky, customers should transition to the 'image_volume_cache_enabled' option


Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.


  • Was this article helpful?