| 2017-05-25 14:28:26 |
Scott Moser |
description |
On i386 and amd64, openstack puts 'OpenStack Nova', into the dmi platform
information. OpenStack using kvm on ppc64el or ppc64, does not identify itself to the guest in any way.
The result is that cloud-init cannot identify it is running on openstack.
We need two things
a.) change openstack to provide that information through libvirt on ppc64
in some way.
b.) possibly changes in qemu to pass information through that the guest
can see. Some options here might include putting information in
the device tree or possibly on the attached disk (model of the disk could be 'OpenStack disk XXXX').
Related bugs:
https://bugs.launchpad.net/cloud-init/+bugs?field.tag=dsid-nova |
On i386 and amd64, openstack puts 'OpenStack Nova', into the dmi platform
information. OpenStack using kvm on s390, does not identify itself to the guest in any way.
The result is that cloud-init cannot identify it is running on openstack.
We need two things
a.) change openstack to provide that information through libvirt on s390
in some way.
b.) possibly changes in qemu to pass information through that the guest
can see. Some options here might include putting information in
the device tree or possibly on the attached disk (model of the disk could be 'OpenStack disk XXXX').
Related bugs:
https://bugs.launchpad.net/cloud-init/+bugs?field.tag=dsid-nova |
|
