← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1590133] [NEW] help text for cpu_allocation_ratio is wrong

 

Public bug reported:

In stable/mitaka in resource_tracker.py the help text for the
cpu_allocation_ratio config option reads in part:

             'NOTE: This can be set per-compute, or if set to 0.0, the value '
             'set on the scheduler node(s) will be used '
             'and defaulted to 16.0'),

However, there is no longer any value set on the scheduler node(s).
They use the per-compute-node value set in resource_tracker.py.

Instead, if the value is 0.0 then ComputeNode._from_db_object() will
convert the value to 16.0.  This ensures that the scheduler filters see
a value of 16.0 by default.

In Newton the plan appears to be to change the default value to an
explicit 16.0 (and presumably updating the help text) but that doesn't
help the already-released Mitaka code.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: compute

-- 
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/1590133

Title:
  help text for cpu_allocation_ratio is wrong

Status in OpenStack Compute (nova):
  New

Bug description:
  In stable/mitaka in resource_tracker.py the help text for the
  cpu_allocation_ratio config option reads in part:

               'NOTE: This can be set per-compute, or if set to 0.0, the value '
               'set on the scheduler node(s) will be used '
               'and defaulted to 16.0'),

  However, there is no longer any value set on the scheduler node(s).
  They use the per-compute-node value set in resource_tracker.py.

  Instead, if the value is 0.0 then ComputeNode._from_db_object() will
  convert the value to 16.0.  This ensures that the scheduler filters
  see a value of 16.0 by default.

  In Newton the plan appears to be to change the default value to an
  explicit 16.0 (and presumably updating the help text) but that doesn't
  help the already-released Mitaka code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1590133/+subscriptions


Follow ups