identify openstack kvm platform on s390
Bug #1693524 reported by
Scott Moser
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Undecided
|
Unassigned | ||
cloud-init |
Expired
|
Medium
|
Unassigned |
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:/
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: | updated |
tags: | added: s390x |
To post a comment you must log in.
Tracked in Github Issues as https:/ /github. com/canonical/ cloud-init/ issues/ 2909