Public bug reported: 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 ** Affects: cloud-init Importance: Medium Status: Confirmed ** Affects: nova Importance: Undecided Status: Confirmed ** Tags: dsid dsid-nova s390x ** Also affects: nova Importance: Undecided Status: New ** Changed in: cloud-init Status: New => Confirmed ** Changed in: nova Status: New => Confirmed ** Changed in: cloud-init Importance: Undecided => Medium ** Tags added: dsid-nova ** Description changed: 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. + 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 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'). + 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 + https://bugs.launchpad.net/cloud-init/+bugs?field.tag=dsid-nova ** Tags added: s390x -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1693524 Title: identify openstack kvm platform on s390 Status in cloud-init: Confirmed Status in OpenStack Compute (nova): Confirmed Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1693524/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
