Chapter 1. Introduction

This document describes how to use the Director to deploy a NetApp appliance as a back end to the Overcloud’s Block Storage service. The following sections assume that:

  • You intend to use only NetApp appliance and drivers for Block Storage back ends
  • The OpenStack Overcloud has already been deployed through Director
  • The NetApp appliance has already been configured and is ready to be used as a storage repository
  • You have the necessary credentials for connecting to the NetApp storage system or proxy server
  • You have the username and password of an account with elevated privileges. You can use the same account that was created to deploy the Overcloud; in Creating a Director Installation User, a stack user is created for this purpose.

When Red Hat OpenStack Platform is deployed through the Director, all major Overcloud settings (in particular, the Block Storage service back end) must be defined and orchestrated through the Director as well. This ensures that the settings will persist through any further Overcloud updates.


For manual instructions on configuring the Block Storage service to use a NetApp appliance as a back end, see Chapter 4. OpenStack Block Storage Service (from the NetApp OpenStack Deployment and Operations Guide). Manually-configured Block Storage settings will need to be re-applied during updates to the Overcloud, as the Director will overwrite any settings it did not orchestrate.

This document explains how to orchestrate your desired NetApp back end configuration to the Overcloud’s Block Storage service. This document will not discuss the different deployment configurations possible with the NetApp back end. Rather, to learn more about the different available NetApp deployment choices, see Theory of Operation & Deployment Choices (from the NetApp OpenStack Deployment and Operations Guide).

Once you are familiar with the resulting back end configuration you want to deploy (and its corresponding settings), refer to this document for instructions on how to orchestrate it through the Director.


Director has the integrated components to deploy only a single instance of a NetApp back end.

Deploying multiple instances of a NetApp back end requires a custom back end configuration. For more information, see the Custom Block Storage Back End Deployment Guide.