yahoo-eng-team team mailing list archive

[Sean Dague <sean@xxxxxxxxx>]

This would be an API bump to add another field there, which means a
nova-spec.

Also, given that this is an admistrative API element, which was set by
configuration, it's not really clear that it's needed. A very specific
use case will need to be layed out for this.

** Changed in: nova
       Status: New => Opinion

** Changed in: nova
   Importance: Undecided => Wishlist

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

Title:
  Hypervisor show not includes ram_allocation_ratio

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  Description
  ===========
  Now the nova hypervisor-show does not contain ram_allocation_ratio,
  cpu_allocation_ratio and disk_allocation_ratio.

  I think this is unreasonable，the user sets the allocation ratio 
  by using the configuration, but they can not see through hypervisor-show.

  Now nova hypervisor-show contains the following fileds:
    - cpu_info: cpu_info
    - state: hypervisor_state
    - status: hypervisor_status
    - current_workload: current_workload
    - disk_available_least: disk_available_least
    - host_ip: host_ip
    - free_disk_gb: hypervisor_free_disk_gb
    - free_ram_mb: free_ram_mb
    - hypervisor_hostname: hypervisor_hostname
    - hypervisor_type: hypervisor_type_body
    - hypervisor_version: hypervisor_version
    - id: hypervisor_id_body
    - local_gb: local_gb
    - local_gb_used: local_gb_used
    - memory_mb: memory_mb
    - memory_mb_used: memory_mb_used
    - running_vms: running_vms
    - service: hypervisor_service
    - service.host: host_name_body
    - service.id: service_id_body
    - service.disable_reason: service_disable_reason
    - vcpus: hypervisor_vcpus
    - vcpus_used: hypervisor_vcpus_used

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