when only a negation is specified for cpu_*_sets we should assume all cpus are vaild and subtract the negated cpus

Bug #1871096 reported by sean mooney
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Triaged
Wishlist
Unassigned

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.

Tags: config numa
Revision history for this message
Yusuf Güngör (yusuf2) wrote :

+1 for this feature

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.