top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

OpenStack: Why Horizon and CLI don't show updated resources after the CPU overcommitment procedure?

+2 votes
276 views

I configured nova.conf file with:
cpu_allocation_ratio=16.0
ram_allocation_ratio=1.5
specifying CoreFilter in scheduler_default_filters.
After this configuration i can't see the overcommitment results in the CLI or in Horizon.
Why? Any tips?

posted Jan 17, 2018 by Salvatore Campanella

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button
I discovered that:
"The Compute API always returns the actual number of CPU cores available on a compute node regardless of the value of the cpu_allocation_ratio configuration key. As a result changes to the cpu_allocation_ratio are not reflected via the command line clients or the dashboard. Changes to this configuration key are only taken into account internally in the scheduler."

Similar Questions
+2 votes

What is the difference between:

  1. using "the Command-line interface to the OpenStack APIs" through the command "openstack"
    and
  2. using the separate APIs of the different components (for example using the command-line interface to the Neutron APIs directly)?

Advantages and disadvantages?

0 votes

What kind of different output came out from these two commands and what is the significance of each field of the output ?

...