Public bug reported:
The code for /allocation_candidates is set up to be able to process a
'required' parameter alongside the 'resources' parameter. This results in a
collection of RequestGroups which are used by the AllocationCandidates code in
nova/objects/resource_provider.py
But we can't request traits on /allocation_candidates because the json
schema does not allow the 'required' parameter.
Adding that results in a system that appears to work modulo at least one
issue:
* AllocationCandidates._get_by_requests raised ValueError on an unknown
trait. It should probably raise TraitNotFound, which should be caught in
the allocation_candidates handler. (There's also a raw ValueError
related to sharing providers).
Of course this doesn't address the nested situation, but that's in
progress elsewhere.
I have some wip code that demonstrates making it work, others should
feel free to leap on this though as I will be out of touch for the next
4 days.
** Affects: nova
Importance: Undecided
Status: New
** Tags: 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/1743860
Title:
allocation candidates db backend can handle non-nested traits but the
HTTP front end is not turned on
Status in OpenStack Compute (nova):
New
Bug description:
The code for /allocation_candidates is set up to be able to process a
'required' parameter alongside the 'resources' parameter. This results in a
collection of RequestGroups which are used by the AllocationCandidates code in
nova/objects/resource_provider.py
But we can't request traits on /allocation_candidates because the json
schema does not allow the 'required' parameter.
Adding that results in a system that appears to work modulo at least
one issue:
* AllocationCandidates._get_by_requests raised ValueError on an
unknown trait. It should probably raise TraitNotFound, which should be
caught in the allocation_candidates handler. (There's also a raw
ValueError related to sharing providers).
Of course this doesn't address the nested situation, but that's in
progress elsewhere.
I have some wip code that demonstrates making it work, others should
feel free to leap on this though as I will be out of touch for the
next 4 days.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1743860/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
