Hello OpenStack community,

I'm working with OpenStack (2023.1 kolla ansible) Nova and using the /os-hypervisors API to gather hypervisor information. I noticed that the CPU and RAM allocation ratios (which are shown in the Horizon dashboard) are not included in the response from:

We're currently using Nova API version 2.91, but I see that the /os-hypervisors API appears to support only up to version 2.1,

I’d like to clarify the following points:

  1. Is it expected behavior that the /os-hypervisors API does not return CPU and RAM allocation ratios?

  2. Is there any API endpoint that exposes these ratios programmatically?

  3. As we are using Nova API version 2.91, but /os-hypervisors seems limited to v2.1, is this a known limitation or design choice?

  4. If the only source of truth is the nova.conf configuration file (e.g., cpu_allocation_ratio, ram_allocation_ratio), is there any plan to expose this via API in future releases?

It would be helpful to know if this is something we should work around by manually collecting config values, or if there's a more appropriate method in modern Nova setups.





Thamanna Farhath  

Associate Engineer R&D 

thamanna.f@zybisys.com

 

       





Disclaimer :  The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender.

 

E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."