Use in_tree getting allocation candidates

Registered by Tetsuro Nakamura on 2017-09-05

In Stein, we introduced ``in_tree=<rp_uuid>`` parameter in placement for the
``GET /allocation_candidates`` endpoints, which limits the response to
resource providers within the same tree of the specified resource provider.

This blueprint proposes to use this parameter for optimization when we move
instances and the target host is already picked before asking to the scheduler.

Blueprint information

Status:
Complete
Approver:
Matt Riedemann
Priority:
Medium
Drafter:
Tetsuro Nakamura
Direction:
Approved
Assignee:
Tetsuro Nakamura
Definition:
Approved
Series goal:
Accepted for train
Implementation:
Implemented
Milestone target:
milestone icon train-1
Started by
Eric Fried on 2019-04-11
Completed by
Matt Riedemann on 2019-05-03

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/use-placement-in-tree,n,z

Addressed by: https://review.openstack.org/646029
    Spec: Use in_tree getting allocation candidates

Addressed by: https://review.openstack.org/649534
    Add in_tree field to RequestGroup object

Addressed by: https://review.openstack.org/649535
    node_uuid from RequestSpec to ResourceRequest

Addressed by: https://review.openstack.org/650877
    Add get_compute_nodes_by_host_or_node()

Addressed by: https://review.openstack.org/650878
    Pass target host to RequestGroup.in_tree

Gerrit topic: https://review.openstack.org/#/q/topic:bug/1777591

The functional changes for this series are merged so I'm marking this complete for Train. -- mriedem 20190503

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.