yahoo-eng-team team mailing list archive

[Eric Xie <mark_xiett@xxxxxxx>]

Public bug reported:

Description
===========
In blueprint: https://blueprints.launchpad.net/nova/+spec/libvirt-hardware-policy-from-libosinfo.
A new nova.conf setting needs to be added, like this:
[libvirt]
  hardware_config=default|fixed|libosinfo
But it cannot be found in Mitaka nova.conf.

Steps to reproduce
==================
* I checked the [libvirt] group of nova.conf

Expected result
===============
'hardware_config' was exist.

Actual result
=============
No 'hardware_config'.

Environment
===========
1. Exact version of OpenStack you are running. 
# rpm -qa | grep nova
openstack-nova-compute-13.0.0-1.el7.noarch
openstack-nova-novncproxy-13.0.0-1.el7.noarch
openstack-nova-conductor-13.0.0-1.el7.noarch
python-nova-13.0.0-1.el7.noarch
openstack-nova-cert-13.0.0-1.el7.noarch
python-novaclient-3.3.0-1.el7.noarch
openstack-nova-console-13.0.0-1.el7.noarch
openstack-nova-scheduler-13.0.0-1.el7.noarch
openstack-nova-api-13.0.0-1.el7.noarch
openstack-nova-common-13.0.0-1.el7.noarch

2. Which hypervisor did you use?
   libvirt+kvm


3. Which networking type did you use?
   Neutron with OpenVSwitch

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  Lack hardware configuration for libosinfo

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  In blueprint: https://blueprints.launchpad.net/nova/+spec/libvirt-hardware-policy-from-libosinfo.
  A new nova.conf setting needs to be added, like this:
  [libvirt]
    hardware_config=default|fixed|libosinfo
  But it cannot be found in Mitaka nova.conf.

  Steps to reproduce
  ==================
  * I checked the [libvirt] group of nova.conf

  Expected result
  ===============
  'hardware_config' was exist.

  Actual result
  =============
  No 'hardware_config'.

  Environment
  ===========
  1. Exact version of OpenStack you are running. 
  # rpm -qa | grep nova
  openstack-nova-compute-13.0.0-1.el7.noarch
  openstack-nova-novncproxy-13.0.0-1.el7.noarch
  openstack-nova-conductor-13.0.0-1.el7.noarch
  python-nova-13.0.0-1.el7.noarch
  openstack-nova-cert-13.0.0-1.el7.noarch
  python-novaclient-3.3.0-1.el7.noarch
  openstack-nova-console-13.0.0-1.el7.noarch
  openstack-nova-scheduler-13.0.0-1.el7.noarch
  openstack-nova-api-13.0.0-1.el7.noarch
  openstack-nova-common-13.0.0-1.el7.noarch

  2. Which hypervisor did you use?
     libvirt+kvm

  
  3. Which networking type did you use?
     Neutron with OpenVSwitch

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