yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #82184
[Bug 1871096] [NEW] when only a negation is specified for cpu_*_sets we should assume all cpus are vaild and subtract the negated cpus
Public bug reported:
when using the cpu_share_set cpu_dedicated_set or
vcpu_pin_set(deprecated) it would be nice to be able to use a ter
syntax.
currently we support negated ranges
so on a 4 core host you can set
^0-1,0-3 and the result will be {2,3}
it would be nice to be able to just set "^0-1" and have the same effect
note that if we made this change we would have to preserve backwards compatiabliyt
and it may be of limited use due to the fact we now have two ranages cpu_share_set and cpu_dedicated_set
it would still allow you to do this however
cpu_share_set=1-10 cpu_dedicated_set=^0-10
to reserve core 0 for the os and core 1-10 for shared cpus and the rest for dedicated cpus.
** Affects: nova
Importance: Wishlist
Status: Triaged
** Tags: config numa
--
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/1871096
Title:
when only a negation is specified for cpu_*_sets we should assume all
cpus are vaild and subtract the negated cpus
Status in OpenStack Compute (nova):
Triaged
Bug description:
when using the cpu_share_set cpu_dedicated_set or
vcpu_pin_set(deprecated) it would be nice to be able to use a ter
syntax.
currently we support negated ranges
so on a 4 core host you can set
^0-1,0-3 and the result will be {2,3}
it would be nice to be able to just set "^0-1" and have the same
effect
note that if we made this change we would have to preserve backwards compatiabliyt
and it may be of limited use due to the fact we now have two ranages cpu_share_set and cpu_dedicated_set
it would still allow you to do this however
cpu_share_set=1-10 cpu_dedicated_set=^0-10
to reserve core 0 for the os and core 1-10 for shared cpus and the rest for dedicated cpus.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1871096/+subscriptions