Expose mistral::rpc_response_timeout as a Heat parameter

It can now be set via the use of 'MistralRpcResponseTimeout'.

Note: the original commit into Victoria and master used 'RPC'
in the name instead of 'Rpc'. Refer to the Related-Change-Id
below. This slightly altered patch now has the same naming
convention as used elsewhere for other RPC service
configurations.

Change-Id: Ie2ecfcc054238bb3780f3052de4b4e12c09fa7d9
Related-Change-Id: I1fb16e6db72316dae7143e77c1508e7e091feb6a
(cherry picked from commit 1890ab0fb9)

deployment/mistral/mistral-base.yaml

@@ -58,6 +58,10 @@ parameters:
     type: string
     default: 'regionOne'
     description: Keystone region for endpoint
+  MistralRpcResponseTimeout:
+    type: number
+    default: 120
+    description: Mistral RPC timeout
 
 conditions:
   service_debug_unset: {equals : [{get_param: MistralDebug}, '']}
@@ -95,7 +99,7 @@ outputs:
           - service_debug_unset
           - {get_param: Debug }
           - {get_param: MistralDebug }
-        mistral::rpc_response_timeout: 120
+        mistral::rpc_response_timeout: {get_param: MistralRpcResponseTimeout}
         mistral::keystone::authtoken::project_name: 'service'
         mistral::keystone::authtoken::user_domain_name: 'Default'
         mistral::keystone::authtoken::project_domain_name: 'Default'