Public bug reported:
When AggregateCoreFilter, AggregateDiskFilter and AggregateRamFilter are
enabled, we will
use the allocation ratio set in aggregate metadata instead of config set per
host.
But when we latter at the weighting process, we used again the config per host,
this might
lead to some undisirerd behavior. We should consider also use the aggregate
allocation ratio.
** Affects: nova
Importance: Undecided
Status: New
--
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/1805917
Title:
Should use aggregate allocation ratio when weigh if set
Status in OpenStack Compute (nova):
New
Bug description:
When AggregateCoreFilter, AggregateDiskFilter and AggregateRamFilter are
enabled, we will
use the allocation ratio set in aggregate metadata instead of config set per
host.
But when we latter at the weighting process, we used again the config per
host, this might
lead to some undisirerd behavior. We should consider also use the aggregate
allocation ratio.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1805917/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
