yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #69235
[Bug 1732731] [NEW] AllocationCandidates.get_by_filters does not handle indirectly connected sharing RPs
Public bug reported:
Consider the following resource setup:
CN1 (VCPU, MEMORY_MB)
/ \
/agg1 \agg2
/ \
SS1 ( SS2 (
DISK_GB) IPV4_ADDRESS
SRIOV_NET_VF)
Then we only request resources provided by SS1 and SS2 but not CN1. This case results in no allocation candidates returned.
I expect that in this case we get allocation candidates that contains SS1 and SS2.
See the reproduction test case in
https://review.openstack.org/#/c/519601/
** Affects: nova
Importance: Undecided
Status: New
** Tags: placement
** Tags added: placement
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1732731
Title:
AllocationCandidates.get_by_filters does not handle indirectly
connected sharing RPs
Status in OpenStack Compute (nova):
New
Bug description:
Consider the following resource setup:
CN1 (VCPU, MEMORY_MB)
/ \
/agg1 \agg2
/ \
SS1 ( SS2 (
DISK_GB) IPV4_ADDRESS
SRIOV_NET_VF)
Then we only request resources provided by SS1 and SS2 but not CN1. This case results in no allocation candidates returned.
I expect that in this case we get allocation candidates that contains SS1 and SS2.
See the reproduction test case in
https://review.openstack.org/#/c/519601/
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1732731/+subscriptions
Follow ups