7b76873150
Manila's API service has a configuration option to control what NAS protocols are allowed for user shared file systems. Storage backends in manila can advertise a number of possible NAS protocols. Deployers need to be able to limit the protocols enabled on their deployments, or specify an override when enabling custom backends. Change-Id: I877063dd3ab9369b09c84136a58f5565aa3f7720 Closes-Bug: #1831767 Depends-On: I7b36e5c45b029f070976e58335d79678752a990c Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com> Co-Authored-By: Alan Bishop <abishop@redhat.com> (cherry picked from commit |
||
---|---|---|
.. | ||
manila-api-container-puppet.yaml | ||
manila-backend-cephfs.yaml | ||
manila-backend-isilon.yaml | ||
manila-backend-netapp.yaml | ||
manila-backend-unity.yaml | ||
manila-backend-vmax.yaml | ||
manila-backend-vnx.yaml | ||
manila-base.yaml | ||
manila-scheduler-container-puppet.yaml | ||
manila-share-common.yaml | ||
manila-share-container-puppet.yaml | ||
manila-share-pacemaker-puppet.yaml |