Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 2. Requirements

The following sections assume that:

  • A NetApp storage controller is deployed and ready to be used as a back end.
  • You intend to use only one NetApp storage controller as a back end for your Shared File System service.
  • You can use the director installation user account, which is created as part of the overcloud deployment. For more information, see Creating the stack user in the Director Installation and Usage guide.
  • The Shared File System service will still be installed on the Controller nodes, as is the default behavior.

This document does discuss the different deployment configurations possible for your NetApp back end. To learn more about possible NetApp storage deployment configurations suitable for the Shared File System service, consult the upstream NetApp documentation (in particular, see Theory of Operation and Deployment Choices).

After mapping your target configuration (the settings you want for each NetApp back end), you can translate your configuration to a custom environment file. The director uses this file to orchestrate the configuration of your back ends and makes them persistent across overcloud updates.

Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat