openstack
/
placement
Code Issues Proposed changes

Merge "Test for multiple limit/group_policy qparams"

This commit is contained in:
Zuul 2019-02-26 13:26:33 +00:00 committed by Gerrit Code Review
parent b5eb31212a d2448ccfc3
commit 01246b0183
2 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
placement/tests/functional/gabbits/allocation-candidates.yaml
View File

@ -181,6 +181,14 @@ tests:
response_json_paths:
$.allocation_requests.`len`: 1
- name: get allocation candidates with multiple limits picks the first one
GET: /allocation_candidates?resources=VCPU:1,MEMORY_MB:1024,DISK_GB:100&limit=10&limit=1
status: 200
request_headers:
openstack-api-version: placement 1.16
response_json_paths:
$.allocation_requests.`len`: 5
- name: get allocation candidates with required traits in old version
GET: /allocation_candidates?resources=VCPU:1,MEMORY_MB:1024,DISK_GB:100&required=HW_CPU_X86_SSE
status: 400

8
placement/tests/functional/gabbits/granular.yaml
View File

@ -81,6 +81,14 @@ tests:
$.allocation_requests.`len`: 0
$.provider_summaries.`len`: 0
- name: multiple group_policy picks the first one
# NOTE(efried): gabbi query_parameters doesn't preserve param order
GET: /allocation_candidates?resources1=VCPU:1&resources2=MEMORY_MB:1024&group_policy=isolate&group_policy=none
status: 200
response_json_paths:
$.allocation_requests.`len`: 0
$.provider_summaries.`len`: 0
- name: resources combine
GET: /allocation_candidates
query_parameters: