Reviewed: https://review.opendev.org/c/openstack/horizon/+/906004
Committed:
https://opendev.org/openstack/horizon/commit/3acbf227a41493032c5828945d41d0b193cd960b
Submitter: "Zuul (22348)"
Branch: master
commit 3acbf227a41493032c5828945d41d0b193cd960b
Author: Tatiana Ovchinnikova <t.v.ovtchinnik...@gmail.com>
Date: Wed Jan 17 14:52:37 2024 -0600
Add allocation ratios to Placement stats
All the Placement API stats "total" show the actual amount of the
resource that the provider can accommodate. Using allocation ratio
it is possible to exceed physical constraints.
This patch uses allocation ratios to display the diagrams properly
and adds the data to the stats table.
Closes-Bug: #1974470
Closes-Bug: #1397917
Change-Id: Iab0ce21ae63f4cc26d3ec5684615189b8ab35231
** Changed in: horizon
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1974470
Title:
Nova is Deprecating Hypervisor API Endpoints
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
As reported on https://bugs.launchpad.net/horizon/+bug/1202965, the
data brought by the responses from the Nova hypervisor API endpoint
contain inconsistencies between the data it provides and the names of
the response fields.
This causes Horizon to display incongruent information on the
hypervisor overview view, as the field for vCPUs used (vcpus_used) is
really providing the total number dedicated and shared CPUs used
while the field for total vCPUs (vcpus) provides information only
about shared CPUs. This last field also doesn't account for the
configured cpu_allocation_ration.
This results on Horizon displaying, for example, uses of 5 out of 4
vCPUs, if an hypervisor is overcommitting cpus, or even uses of 4 out
of 0 vCPUs, if all CPUs are configured as dedicated.
This is troublesome as Nova is, practically, deprecating the
Hypervisor API endpoints, see this accepted proposal that REMOVES the
fields used by horizon on the latest version of the API:
https://review.opendev.org/c/openstack/nova/+/764040/. A fix to the
contents of its response should not be expected as a solution.
A possible solution might be transitioning to the Placement API
instead, which appears to provide more consistent data and is Being
used in Skyline.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1974470/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
