Chapter 4. Testing the configured back end

Procedure

1. Run the following command as the stack user to load the environment variables defined in home/stack/overcloudrec:

   $ source /home/stack/overcloudrc

   Copy to Clipboard Toggle word wrap

1. Create a volume type for each back end. Log in to the Controller node of the overcloud as the stack user and run the following command:

   $ cinder type-create backend1
   $ cinder type-create backend2

   Copy to Clipboard Toggle word wrap

   These commands create the volume types backend1 and backend2, one for each back end that is defined with the cinder::config::cinder_config class of the environment file that you created.

2. Map each volume type to the volume_backend_name of a back end that is enabled with the cinder_user_enabled_backends class of the environment file that you created The following commands map the volume type backend1 to netapp1 and backend2 to netapp2:

   $ cinder type-key backend1 set volume_backend_name=netapp1
   $ cinder type-key backend2 set volume_backend_name=netapp2

   Copy to Clipboard Toggle word wrap

3. Run the following command to test that it is possible to create a back end on netapp1 by invoking the backend1 volume type:

   $ cinder create --volume-type backend1 --display_name netappvolume_1 1

   Copy to Clipboard Toggle word wrap

4. Create a similar volume on the netapp2 back end by invoking the backend2 volume type:

   $ cinder create --volume-type backend2 --display_name netappvolume_2 1

   Copy to Clipboard Toggle word wrap