yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #71077
[Bug 1748858] [NEW] allocation_ratio set by aggregate metadata don't work in NUMATopologyFilter
Public bug reported:
Description
===========
Allocation_ratio setted by aggregate metadata don't work in NUMATopologyFilter. NUMATopologyFilter always takes the allocation_ratio from the compute node's configuration file.
We do not provide a consistent way to set the allocation_ratio when user use the AggregateCoreFilter, AggregateRamFilter and NUMATopologyFilter at same time.
Environment
===========
nova16.0.4
** Affects: nova
Importance: Undecided
Assignee: yangjie (yang.jie)
Status: New
** Changed in: nova
Assignee: (unassigned) => yangjie (yang.jie)
--
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/1748858
Title:
allocation_ratio set by aggregate metadata don't work in
NUMATopologyFilter
Status in OpenStack Compute (nova):
New
Bug description:
Description
===========
Allocation_ratio setted by aggregate metadata don't work in NUMATopologyFilter. NUMATopologyFilter always takes the allocation_ratio from the compute node's configuration file.
We do not provide a consistent way to set the allocation_ratio when user use the AggregateCoreFilter, AggregateRamFilter and NUMATopologyFilter at same time.
Environment
===========
nova16.0.4
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1748858/+subscriptions
Follow ups