Skip to main content
NetApp Knowledge Base

NetApp ONTAP and OpenStack Cinder Integration: cinder.conf Parameter Confirmation and SVM Connectivity

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

Applies to

  • NetApp AFF and All Flash FAS (AFF) platforms
  • OpenStack Cinder (NFS, iSCSI or Fibre Channel)
  • OpenStack environments integrating with NetApp SVMs

Answer

Question in detail:
When integrating NetApp ONTAP with OpenStack Cinder, can we connect directly to a specific SVM over HTTPS, or is it required to use the cluster management LIF from Cinder API?
Additionally, are the following cinder.conf parameters recommended and supported in production by NetApp Support?

  • netapp_pool_name_search_pattern
  • filter_function (and optionally goodness_function)

Answer:

SVM Connectivity for Cinder API:

  • Yes, we can connect directly to a specific SVM (Storage Virtual Machine) over HTTP or HTTPS for Cinder integration.
  • Ensure the SVM has a management LIF (Logical Interface) configured, and that TCP ports 443 (HTTPS) and/or 80 (HTTP) are open between the OpenStack nodes and the SVM management LIF.
  • It is not mandatory to use the cluster management LIF; connecting to the SVM management LIF is supported and commonly used in production for Cinder drivers.

cinder.conf Parameter Recommendations and Support:

  1. netapp_pool_name_search_pattern

    • Purpose: Restricts Cinder volume provisioning to specific FlexVol volumes, using a regular expression to match volume names.
    • Usage: Only applicable when the Cinder driver is configured for iSCSI or Fibre Channel.
    • Recommendation:
      • This option is recommended and supported in production environments.
      • NetApp Support will assist with issues when this parameter is used as documented.
    • Documentation reference:

  2. filter_function (and goodness_function)

    • Purpose:
      • filter_function can override the default filter to control which backends are eligible for volume placement (e.g., based on utilization).
      • goodness_function can influence backend selection to prefer less utilized controllers.
    • Recommendation:
      • Both options are supported and can be used together with netapp_pool_name_search_pattern in production.
      • The default filter (capabilities.utilization < 70) and goodness (100 - capabilities.utilization) are safe for most environments, but customization is supported per OpenStack documentation.
    • Documentation reference:

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.