Red Hat SummitQuesto contenuto non è disponibile nella lingua selezionata.
Chapter 8. manila test
The manila test applies to OpenStack products or components that implement features for the OpenStack Shared File System Storage service. The test uses Tempest Framework integrated with the Red Hat OpenStack Services on OpenShift (RHOSO) to test both operational and functional features.
The manila test verifies the functionality of the manila driver that you are certifying by running selected feature tests. The following feature groups are currently tested:
- Section 8.1, “manila-shr” (required)
- Section 8.2, “manila-shr-managed” (optional)
- Section 8.3, “manila-shr-shrink” (optional)
- Section 8.4, “manila-shr-extend” (required)
- Section 8.5, “manila-snap” (optional)
- Section 8.6, “manila-snap-managed” (optional)
- Section 8.7, “manila-shr-frm-snap” (optional)
- Section 8.8, “manila-snap-revert” (optional)
- Section 8.9, “manila-snap-mount” (optional)
- Section 8.10, “manila-shr-replicas” (optional)
- Section 8.11, “manila-shr-groups” (required)
Section 8.12, “manila-svr-managed” (only for DHSS=True, optional)
Manila testing must include the tests defined in the test plan, covering the required tests and any implemented additional features.
If you are certifying a backend that supports multiple driver modes indicated by the attribute “driver_handles_share_servers”, abbreviated as DHSS, set to true or false, or multiple storage protocols such as Network File System (NFS) and Common Internet File System (CIFS), you must adjust the test configuration to submit one test result per combination of driver mode and supported protocols. For example, if the driver being certified supports both NFS and CIFS, and both DHSS=True and DHSS=False, you must submit separate certification tests for each combination:
- DHSS=True with NFS.
- DHSS=False with NFS.
- DHSS=True with CIFS.
- DHSS=False with CIFS.
Prerequisites
When deploying the Control plane, ensure that you provide at least two instances of the shared file system backend driver you intend to certify.
NoteHaving more than one hardware storage is not required; configuring both manila backends to use the same hardware array is supported.
- Ensure you configure the separate manila backends on separate “manila-share” pods. Multi-backend configuration on a single pod was supported in earlier releases of RHOSP, but is no longer supported in RHOSO.
The
rhoso-certtooling will automatically detect and set some test configurations, however, manual adjustments may still be required to ensure that the features being tested are appropriately configured. These configurations should be specified in a file namedtempest-conf-overrides.NoteWhen defining custom configuration options, avoid setting options that could mask test failures, such as
share.suppress_errors_in_cleanup.- In the current RHOSO version, all manila tests are executed, including both required and optional tests such as replication, managing snapshots, and so on. The optional tests may fail if your driver does not support those features. This is acceptable and does not impact the overall certification process.
When certifying a
DHSS=Trueback end, ensure the following:-
When testing with NFS, ensure that the manila service is configured with
NeutronNetworkPluginor its derivative. The use ofStandaloneNetworkPluginis discouraged. -
When testing with CIFS, the use of
NeutronNetworkPluginmay be complicated if the authentication server (typically an active directory server) is external to the cloud. You may useStandaloneNetworkPluginin such a case to represent the datacenter’s storage networking. -
Create an
accounts.yamlfile for the rhcert tooling to use. This is essential to avoid cleanup errors in tempest tests.
-
When testing with NFS, ensure that the manila service is configured with
8.1. manila-shr
The manila-shr test checks the base file operations with either the NFS or CIFS protocols. This test also covers the base operations with or without the “driver handles share servers” (DHSS) feature enabled.
It tests the APIs to create, delete, update, and retrieve core manila resources like share types, availability zones, storage pool statistics, limits, quotas, metadata, API versioning, access rules, user messages, security services, share networks, share actions, and share instances.
8.2. manila-shr-managed
The manila-shr-managed test checks the driver’s ability to abandon existing shares and adopt them back into manila.
8.3. manila-shr-shrink
The manila-shr-shrink test checks the driver’s capability to shrink manila shares.
8.4. manila-shr-extend
The manila-shr-extend test checks the driver’s capability to extend manila shares.
8.5. manila-snap
A snapshot allows users to capture the contents of a share at a point in time. Users have the option to restore the data in place, clone the snapshot into a new share, or control access to the snapshot via access rules and mount the snapshot directly as a read-only filesystem. The plugin or driver functionalities that are tested as part of manila_snapshot test are:
- Creating snapshots
- Altering snapshot status
- Deleting or force delete snapshots
- Interacting with share snapshot instances
- Deleting shares with existing snapshots
- Creating larger shares with a snapshot of a smaller size
- Creating shares from snapshot within a different share network
- Deleting snapshot with incorrect share id
- Creating snapshot with incorrect snapshot id
- Listing shares by snapshot id
- Listing and renaming snapshots
- Adding and manipulating snapshot metadata
8.6. manila-snap-managed
The manila-snap-managed test checks the driver’s capability to abandon existing snapshots and adopt them back into Manila.
8.7. manila-shr-frm-snap
The manila-shr-frm-snap test checks the driver’s capability to create new shares from existing snapshots.
8.8. manila-snap-revert
The manila-snap-revert test checks the driver’s capability to revert a share to its latest snapshot.
8.9. manila-snap-mount
The manila-snap-mount test checks the driver’s capability to create snapshots that can directly be mounted as read-only filesystems.
8.10. manila-shr-replicas
The manila-shr-replicas test checks the driver’s capability to create replicas of a share across availability zones and perform actions on a replica such as promotion, forced syncing, deletion, and taking snapshots.
8.11. manila-shr-groups
The manila-shr-groups test checks the driver’s capability to create share group types and share groups, including the ability to create shares within these groups. It also tests the ability to update groups, delete groups, and take group snapshots. The ability of the driver to take consistent snapshots of the group must be configured.
8.12. manila-svr-managed
The manila-svr-managed test checks the driver’s capability to abandon a share server that was created within manila and adopt it again. It also tests the ability to abandon all the shares exported on the share server and adopt them back.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}