diff options
| author | Jim Rollenhagen <jim@jimrollenhagen.com> | 2016-07-07 15:17:31 -0400 |
|---|---|---|
| committer | Jim Rollenhagen <jim@jimrollenhagen.com> | 2016-07-14 14:37:02 -0400 |
| commit | 2e10d7b32cc32a2d367bbd38ec612fd283aaac8e (patch) | |
| tree | 036ae817b7aed5e5c43b2770787849c29a48c132 /ironic_python_agent/hardware.py | |
| parent | b139dccf3c7886942b99fd6a77d1d4c1cadb91a9 (diff) | |
| download | ironic-python-agent-2e10d7b32cc32a2d367bbd38ec612fd283aaac8e.tar.gz | |
Fix doc warnings
Per Doug's email[0], 'warnerrors' in setup.cfg hasn't actually been
working for some time now, and we've piled up a few warnings. Fix these
before a pbr release to unbreak it gets pushed out and breaks our doc
builds.
[0] http://lists.openstack.org/pipermail/openstack-dev/2016-June/097849.html
Change-Id: I6576a56234918febb21e7e4860544eb952123c09
Diffstat (limited to 'ironic_python_agent/hardware.py')
| -rw-r--r-- | ironic_python_agent/hardware.py | 14 |
1 files changed, 8 insertions, 6 deletions
diff --git a/ironic_python_agent/hardware.py b/ironic_python_agent/hardware.py index 203245dd..5755b541 100644 --- a/ironic_python_agent/hardware.py +++ b/ironic_python_agent/hardware.py @@ -354,12 +354,14 @@ class HardwareManager(object): If multiple hardware managers return the same step name, the following logic will be used to determine which manager's step "wins": - - Keep the step that belongs to HardwareManager with highest - HardwareSupport (larger int) value. - - If equal support level, keep the step with the higher defined - priority (larger int). - - If equal support level and priority, keep the step associated - with the HardwareManager whose name comes earlier in the alphabet. + + * Keep the step that belongs to HardwareManager with highest + HardwareSupport (larger int) value. + * If equal support level, keep the step with the higher defined + priority (larger int). + * If equal support level and priority, keep the step associated + with the HardwareManager whose name comes earlier in the + alphabet. The steps will be called using `hardware.dispatch_to_managers` and handled by the best suited hardware manager. If you need a step to be |