openstack/nova
Code Issues Proposed changes

Merge "FUP: Remove noqa and tone down an exception"

Browse Source
This commit is contained in:
Zuul 2020-03-18 01:28:57 +00:00 committed by Gerrit Code Review
commit ca4226cb87
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
nova/exception.py
View File

@ -2274,7 +2274,7 @@ class VPMEMCleanupFailed(NovaException):
class RequestGroupSuffixConflict(NovaException):
msg_fmt = _("Duplicate request group suffix %(suffix)s!")
msg_fmt = _("Duplicate request group suffix %(suffix)s.")
class AmbiguousResourceProviderForPCIRequest(NovaException):

4
nova/scheduler/utils.py
View File

@ -73,7 +73,7 @@ class ResourceRequest(object):
...where ``$S`` is a string suffix as supported via Placement
microversion 1.33
https://docs.openstack.org/placement/train/specs/train/implemented/2005575-nested-magic-1.html#arbitrary-group-suffixes # noqa
https://docs.openstack.org/placement/train/specs/train/implemented/2005575-nested-magic-1.html#arbitrary-group-suffixes
.. note::
@ -82,7 +82,7 @@ class ResourceRequest(object):
The string suffix is used as the RequestGroup.requester_id to
facilitate mapping of requests to allocation candidates using the
``mappings`` piece of the response added in Placement microversion 1.34
https://docs.openstack.org/placement/train/specs/train/implemented/placement-resource-provider-request-group-mapping-in-allocation-candidates.html # noqa
https://docs.openstack.org/placement/train/specs/train/implemented/placement-resource-provider-request-group-mapping-in-allocation-candidates.html
For image metadata, traits are extracted from the ``traits_required``
property, if present.