F OpenNebula/one#6474: Add host_id to External Scheduler (#2824)

source/intro_release_notes/release_notes_enterprise/resolved_issues_682.rst

@@ -9,6 +9,7 @@ A complete list of solved issues for 6.8.2 can be found in the `project developm
 The following new features have been backported to 6.8.2:
 
 - Virtual Routers now support ``FLOATING_ONLY`` attributes for their network NICs. When this attribute is set to ``yes`` no additional IPs are allocated for the VMs of the VR, :ref:`see more information on the Virtual Router guide <vrouter>`.
+- For VMs with resched flag add ``HOST_ID`` to :ref:`External Scheduler API <external_scheduler>`.
 
 The following issues has been solved in 6.8.2:
 

source/management_and_operations/capacity_planning/external.rst

@@ -18,6 +18,7 @@ The scheduler employs a simple REST API. When the external scheduler is configur
   - ``DISK``: Additional disk space in the system datastore (in megabytes)
 
 - ``HOST_IDS``: A list of IDs for hosts meeting the VM requirements
+- ``HOST_ID``: Host ID, where the VM is deployed. Used only if the VM is requested to reschedule (migrate) to other host.
 - ``ID``: VM's ID
 - ``STATE``: Current state in string form
 - ``ATTRIBUTES``: Custom attributes as specified in :ref:`scheduler configuration <schg_configuration>` in ``EXTERNAL_VM_ATTR``.
@@ -75,12 +76,12 @@ For instance, the following JSON illustrates a request for 3 VMs along with thei
             "MEMORY": 131072
           },
           "HOST_IDS": [
-            3,
             4,
             5
           ],
+          "HOST_ID": 3,
           "ID": 34,
-          "STATE": "PENDING"
+          "STATE": "RUNNING"
         }
       ]
     }