Add 'NovaAllowResizeToSameHost' parameter

This parameter is used quite often but is not currently exposed in THT.
Close that gap. This is used by the API so it is that container that's
modified.

Change-Id: Idb56d7e2fd741b3d0dfaa8fd376ebe6d6ae8b867
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>

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

@@ -97,6 +97,10 @@ parameters:
       e.g. { nova-context_is_admin: { key: context_is_admin, value: 'role:admin' } }
     default: {}
     type: json
+  NovaAllowResizeToSameHost:
+    default: false
+    description: Allow destination machine to match source for resize.
+    type: boolean
 
 parameter_groups:
 - label: deprecated
@@ -222,6 +226,7 @@ outputs:
             nova_enable_db_purge: {get_param: NovaEnableDBPurge}
             nova_enable_db_archive: {get_param: NovaEnableDBArchive}
             nova::policy::policies: {get_param: NovaApiPolicies}
+            nova::allow_resize_to_same_host: {get_param: NovaAllowResizeToSameHost}
           -
             if:
             - nova_workers_zero

releasenotes/notes/allow-resize-to-same-host-62f05a5370993425.yaml

@@ -0,0 +1,5 @@
+---
+features:
+  - |
+    Add parameter ``NovaAllowResizeToSameHost`` to allow instances to resize
+    to the host they are currently on. Normally the source host is excluded.