419e02e786
1.What is the problem: If availability zone (az in short) does not exit in the server creation request or extenal network, 400 bad request was given in current handling, this handling is inconsistent with Nova and Neutron.In Nova and Neutron, az is one optional parameter, i.e, even the az is not speficied in the request, a scheduled az should be used for the creation, but not return 400 bad request. 2.What's need to be fixed: To fix the issue, server creation should allow no az parameter in the request, and select one default bottom pod to continue the server creation. 3.What is the purpose of this patch set: To make the az handling behavior is consistent with that in Nova and Neutron. Change-Id: I9281914bad482573c6540bf2a14e51e7ca4d744c Signed-off-by: joehuang <joehuang@huawei.com> |
||
|---|---|---|
| .. | ||
| api | ||
| cinder_apigw | ||
| common | ||
| db | ||
| network | ||
| nova_apigw | ||
| tempestplugin | ||
| tests | ||
| xjob | ||
| __init__.py | ||