[manila] Add "ManilaEnabledShareProtocols" param

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>

deployment/manila/manila-api-container-puppet.yaml

@@ -54,6 +54,12 @@ parameters:
   MonitoringSubscriptionManilaApi:
     default: 'overcloud-manila-api'
     type: string
+  ManilaEnabledShareProtocols:
+    default: ''
+    description: List of protocols to be allowed for share creation in manila.
+                 When not set, the list is inferred via the storage back end/s
+                 enabled.
+    type: comma_delimited_list
 
 conditions:
 
@@ -154,6 +160,7 @@ outputs:
             manila::api::service_name: 'httpd'
             manila::api::enable_proxy_headers_parsing: true
             manila::api::default_share_type: 'default'
+            manila_enabled_share_protocols: {get_param: ManilaEnabledShareProtocols}
           - manila::wsgi::apache::servername:
               str_replace:
                 template:

releasenotes/notes/bug-1831767-allow-configuring-manila-share-protocols-6ea6bcbbe21b25ee.yaml

@@ -0,0 +1,7 @@
+---
+fixes:
+  - |
+    When using the Shared File Systems service (manila), you may now use the
+    Heat template parameter "ManilaEnabledShareProtocols" to configure
+    the NAS protocols that users may use. If not set, the value is inferred
+    per the storage backends that have been enabled.