openstack/nova-specs
Code Issues Proposed changes

Clarify wording in Searchlight spec - error conditions

Browse Source 
There was some confusing / conflicting wording in the error
conditions part of the spec (do we log error or warning?). This
clarifies that to be consistent about saying we just log a warning
if configured to use Searchlight but it's not available (which is
what we do if Placement isn't available).

Related to blueprint list-instances-using-searchlight

Change-Id: I1331d685e82f100a1965bd835e89147c10cbcda1
This commit is contained in:
Matt Riedemann
2017-05-08 14:22:49 -04:00
parent c505d25f07
commit 533a5ebcb5
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
specs/pike/approved/list-instances-using-searchlight.rst
View File

@@ -61,8 +61,8 @@ Error conditions
* If configured to use Searchlight but it is not available in the service
catalog or Nova does not have access to it, we will fallback to the default
path which means iterating the cells to list instances and merge sort the
results. An error would be logged in this case but the API request should not
fail with a 500. We will log a warning and set a flag so that we do not
results. A warning would be logged in this case but the API request should
not fail with a 500. We will also set a flag so that we do not
continue to check until the service is restarted, similar to how we handled
the placement API in ``nova.scheduler.client.report.SchedulerReportClient``
with the ``@safe_connect`` decorator in Newton.