Chapter 8. Cinder tests

Prerequisites

1. When deploying the overcloud, ensure that:

   1. You have provided two instances of the backend you intend to certify.

      Note

      Having more than one hardware storage is not required; configuring both cinder backends to use the same hardware array is supported.

   2. You have enabled the cinder-backup service. To do this, add the cinder-backup environment file in the overcloud deployment command.

      -e /usr/share/openstack-tripleo-heat-templates/environments/cinder-backup.yaml

      For more information, see Configuring your overcloud by using environment files.

   3. You have disabled cinder’s LVM/iSCSI backend, and configured Glance to use Cinder as its backend. To do this, create a new custom environment file, for example, rhcert-overrides.yaml and add the following lines:

      parameter_defaults:
        CinderEnableIscsiBackend: false
        GlanceBackend: cinder

      Then, add the rhcert-overrides.yaml file to the overcloud deployment command.

      -e /home/stack/rhcert-overrides.yaml

2. Before executing the tempest_config test, ensure that:

   1. You have enabled the following flags under their respective section header in the tempest.conf file.

      Note

      If your plugin supports the consistency groups and multi-attach volumes features, then ensure to enable their corresponding flags in the tempest.conf file.

      For example, consistency_group and volume_multiattach flags in the tempest.conf file are enabled.

      [volume-feature-enabled]
      consistency_group = True
      extend_attached_encrypted_volume = True
      extend_attached_volume = True
      manage_snapshot = True
      manage_volume = True
      volume_revert = True
      
      [image-feature-enabled]
      import_image = True
      
      [compute-feature-enabled]
      volume_multiattach = True

   2. You have set the tempest_roles as follows in the tempest.conf file:

      [auth]
      tempest_roles = member,swiftoperator

3. If your driver supports multi-attach volume feature, perform the following steps before executing cinder’s multi-attach volume tests:

   1. Create a multi-attach volume type by following the procedure explained in Creating a multi-attach volume type. Do not configure cinder’s default volume type to be the multi-attach volume type.

   2. Add a reference to the multi-attach volume type in the tempest.conf file, as shown below:

      [volume]
      volume_type_multiattach = <multiattach volume type>