Squashed backport for 'NovaAllowResizeToSameHost' parameter

We squashed the backports because the first patch wasn't right, so for
full history we backports the 2 patches in the same time.

1) 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>
(cherry picked from commit 0b63621a5e)

2) Fix allow_resize_to_same_host

allow_resize_to_same_host is in nova::api class, not ::nova.

Change-Id: I4cc533b3d48f3443f3470e1b25ffc39edfc9dc22
(cherry picked from commit c583e429c2)
(cherry picked from commit 513321b3be)

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

@@ -105,6 +105,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
 
 conditions:
 
@@ -224,6 +228,7 @@ outputs:
             nova_enable_db_purge: {get_param: NovaEnableDBPurge}
             nova_enable_db_archive: {get_param: NovaEnableDBArchive}
             nova::policy::policies: {get_param: NovaApiPolicies}
+            nova::api::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.