Cinder test

The cinder test applies to OpenStack products or components that implement features for the OpenStack Block Storage service only. The test uses Tempest Framework integrated with the Red Hat OpenStack Services on OpenShift (RHOSO). This tests both operational and functional features.

The cinder test verifies the functionality of the cinder driver that you are certifying by running selected feature tests. The following feature groups are currently tested:

  • cinder-volumes
  • cinder-backups
  • cinder-multi-attach-volume
  • cinder-consistency-groups
Note
  • The certification software automatically generates some configuration settings. Overrides can be applied using tempest-conf-overrides.
  • In the current RHOSO version, all the tests are executed. This includes both mandatory and optional tests, such as consistency groups and multi-attach volumes. The optional tests may fail if your driver does not support those features. This is acceptable and does not impact the overall certification process.

Prerequisites

  1. When deploying the Control plane, ensure that:
    1. You provide 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. Enable the cinder-backup service during the RHOSO deployment.
    3. Configure Glance to use Cinder as its backend.
      • For more information about block storage, see Configuring a Block Storage back end.
  2. Configure a public subnet before running the tempest tests.
  3. If your driver supports the multi-attach volume feature, perform the following steps before executing the cinder tests:
    1. Create a volume type named “multiattach” by following the procedure explained in Creating a multi-attach volume type.
    2. Ensure that the Cinder default volume type is not configured to be the multi-attach volume type. Note

      You must use the name “multiattach” for the volume type.