openstack/placement
Code Issues Proposed changes

gabbi test for same_subtree with an ancestry hole

Browse Source 
Based on the analysis at [1], we need to continue to use fully-populated
ancestry data when calculating same_subtree-ness. This commit introduces
a gabbi test that covers a particular case that can be broken if we
don't do that: where a provider involved in the request has a broken
ancestry path to another provider involved in the request.

[1] https://review.opendev.org/#/c/675606/2/placement/objects/allocation_candidate.py@908

Change-Id: I5062e725d6f29cd997b974a0dad7dc4d0ed2900f
This commit is contained in:
Eric Fried
2019-08-14 13:48:50 -05:00
committed by Chris Dent
parent a6e1a19a85
commit 9d256fa6c7
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
placement/tests/functional/gabbits/granular-same-subtree.yaml
View File

@@ -525,3 +525,14 @@ tests:
$.allocation_requests..allocations['$ENVIRON["PF3_1_UUID"]'].resources.CUSTOM_VF: [2, 2, 2]
$.allocation_requests..allocations['$ENVIRON["PF2_1_UUID"]'].resources.CUSTOM_VF: [2, 2, 2]
$.allocation_requests..allocations['$ENVIRON["PF2_3_UUID"]'].resources.CUSTOM_VF: [2, 2, 2]
- name: same_subtree with an ancestry hole
GET: /allocation_candidates
query_parameters:
required_MULTI_ATTACH: COMPUTE_VOLUME_MULTI_ATTACH
resources_BW: NET_BW_EGR_KILOBIT_PER_SEC:100
resources_COMPUTE: VCPU:4
same_subtree: _MULTI_ATTACH,_BW,_COMPUTE
group_policy: isolate
response_json_paths:
$.allocation_requests.`len`: 3