Chapter 7. cinder test
Chapter 7. 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) to test 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: Section 7.1, "cinder-volumes" Section 7.2, "cinder-backups" Section 7.3, "cinder-multi-attach-volume" Section 7.4, "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, including 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 When deploying the Control plane, ensure that: 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. Enabled the cinder-backup service during the RHOSO deployment. Configure Glance to use Cinder as its backend. For more information on configuring a block storage see, Configuring a Block Storage back end . Configure a public subnet before running the tempest tests. If your driver supports the multi-attach volume feature, perform the following steps before executing the cinder tests: Create a volume type named "multiattach" by following the procedure explained in Creating a multi-attach volume type . Ensure that Cinder's default volume type is not configured to be the multi-attach volume type. Note You must use the name "multiattach" for the volume type. 7.1. cinder-volumes The cinder-volumes test checks if the driver functionalities and base functionalities of cinder, such as volume actions, snapshots, boot, volume migrate, encryption, and clone are working. This test is mandatory. 7.2. cinder-backups The cinder-backups test verifies the driver's backup and restore functionality by testing the following: Creating and restoring a backup from existing volume Testing an incremental backup Taking a backup of a volume snapshot 7.3. cinder-multi-attach-volume The cinder-multi-attach-volume test checks if a single block storage volume can be attached to and accessed from multiple hosts or servers by running the following tests: Booting a VM from a multi-attach volume Resizing a server with a multi-attach volume Listing volume attachments for a multi-attach volume Creating a snapshot from a multi-attach volume Attaching and detaching a multi-attach volume from a shelved or offloaded server Deleting an attached multi-attach volume Attaching a multi-attach volume to the same or a different server 7.4. cinder-consistency-groups The cinder-consistency-groups test checks for disaster recovery by performing the following actions simultaneously: Creating and deleting consistency groups Creating and deleting consistency group snapshots Creating a new consistency group from an existing consistency group snapshot