Backlog #3870

Redesign UI for CPU attribute, include overcommit section

Added by EOLE Team over 5 years ago. Updated over 4 years ago.

Status:NewStart date:07/09/2015
Priority:HighDue date:
Assignee:-% Done:

0%

Category:Sunstone
Target version:-

Description

Hello,

The dashboard display REAL CPU USAGE and ALLOCATED CPU as integers numbers like 2020 / 4780.

The VM CPU configuration is a float with a correspondence 1 CPU in template == 100 CPU on dashboard.

This is quite confusing for users.

This should be also considered for cloud view

Is it possible to only use integersĀ as on dashboard?

Regards.


Related issues

Related to Feature #4317: Redesign group admin view Closed 02/03/2016
Related to Backlog #4354: Enhance overcommitment configuration Pending 02/22/2016

History

#1 Updated by Ruben S. Montero over 5 years ago

  • Tracker changed from Request to Backlog
  • Target version set to Release 5.0

#2 Updated by Ruben S. Montero about 5 years ago

Hi

You are right the values for CPU in hosts are in percentage while the VM templates are not. These definitions affects multiple components from the UI, CLI, oned, scheduler down to the monitoring drivers for each hypervisor KVM, EC2, vCenter... So it is really difficult to change the definition of one of these two (VM Template CPU or Host CPU). We've been thinking of how we can avoid confusion and improve the dashboard, but we could not find a solution good enough (we prefer to keep consistency for the same metric across views and tabs, i.e. host FREECPU always in percentage). So, considering this, do you have a proposal?

Cheers and thanks for the feedback.

#3 Updated by Ruben S. Montero almost 5 years ago

  • Tracker changed from Backlog to Feature
  • Subject changed from Use constistent format between dashboard and VM template CPU to Redesign UI for CPU attribute, include overcommit section
  • Category set to Sunstone

After discussing this, we think that the best option is to hide the CPU value from the user input, and move it to an Overcommit section, which is actually the purpose of this attribute.

Updating the issue subject to reflect this.

#4 Updated by Ruben S. Montero almost 5 years ago

  • Status changed from Pending to New

#5 Updated by Daniel Molina almost 5 years ago

#6 Updated by Ruben S. Montero over 4 years ago

  • Description updated (diff)

#7 Updated by Ruben S. Montero over 4 years ago

  • Related to Backlog #4354: Enhance overcommitment configuration added

#8 Updated by Ruben S. Montero over 4 years ago

  • Tracker changed from Feature to Backlog
  • Priority changed from Normal to High
  • Target version deleted (Release 5.0)

#9 Updated by OpenNebula Systems Support Team over 4 years ago

- Cloud View should present the value of VCPU, not CPU
- Evaluate as well fine grained definitions of CPU per SOCKET (at least in vCenter)

#10 Updated by EOLE Team over 4 years ago

OpenNebula Systems Support Team wrote:

- Cloud View should present the value of VCPU, not CPU

This one could be configurable to make capacity resizing available?

Also available in: Atom PDF