Associated customer case: https://access.redhat.com/support/cases/#/case/04070410

This feature is an API based feature that allows a manila share to be transferred from a project to another, making this process more simple for day-2 cloud operations. 

The feature is only available for DHSS=False mode, considering that if a DHSS=True share was transferred to another project, we would also need to transfer the associated share network and share server, which would potentially lead to even more shares being transferred at once. The DHSS=True transfer remains a future plan, and we are planning to research the feasibility and action items as part of a spike.

Goal:

• Make the feature that allows a share to be transferred in between tenants available in the RHOSO 18 feature release.

Acceptance Criteria:

• Ensure both API and client are available for this feature.
• Test with CephFS/NFS.
• Test with CephFS native and ensure nothing is broken.

Questions:

• Is this feature driver dependent?
  • No, this feature is not driver dependent, as only the API and database are involved. However, in case a driver has access rules or shares that depend on the manila project/user ID under the hood, they will need to reject the operation. For CephFS, there are some dependencies, so the share transfers feature is disabled in case there are access rules in place. If the user wants to transfer a Ceph share, all access rules must be deleted and recreated after the transfer is complete.
• How will share transfers work with encrypted shares?
  • At the moment, transferring the shares whose share server is encrypted is not blocked. However, this feature deserves more testing and consideration.