Chapter 5. Test the Configured Back End


After deploying the back end, test whether you can successfully create volumes on it. Doing so will require loading the necessary environment variables first. These variables are defined in /home/stack/overcloudrc by default.

To load these variables, run the following command as the stack user:

Copy to Clipboard Toggle word wrap
$ source /home/stack/overcloudrc
Note

For more information, see Accessing the Overcloud.

You should now be logged in to the Controller node. From there, you can create a volume type, which can be used to specify the back end you want to use (in this case, the newly-defined back end in Chapter 3, Define a Single Back End). This is required in an OpenStack deployment where you have other back ends enabled (preferably, also through Director).

To create a volume type named dellps, run:

Copy to Clipboard Toggle word wrap
$ cinder type-create dellps

Next, map this volume type to the back end defined in ]. Given the back end name tripleo_dellps (as defined through the CinderDellPsBackendName parameter, in xref:edityaml[), run:

Copy to Clipboard Toggle word wrap
$ cinder type-key dellps set volume_backend_name=tripleo_dellps

You should now be able to create a 2GB volume on the newly defined back end by invoking its volume type. To do so, run:

Copy to Clipboard Toggle word wrap
$ cinder create --volume-type dellps 2
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, Inc.