canonical / canonical/cloud-init
identify openstack kvm platform on s390
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 1.1k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 18
Description
This bug was originally filed in Launchpad as [LP: #1693524](https://bugs.launchpad.net/cloud-init/+bug/1693524)
Launchpad details
affected_projects = ['nova']
assignee = None
assignee_name = None
date_closed = None
date_created = 2017-05-25T14:26:04.759266+00:00
date_fix_committed = None
date_fix_released = None
id = 1693524
importance = medium
is_complete = False
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1693524
milestone = None
owner = smoser
owner_name = Scott Moser
private = False
status = confirmed
submitter = smoser
submitter_name = Scott Moser
tags = ['dsid', 'dsid-nova', 's390x']
duplicates = []
_Launchpad user **Scott Moser(smoser)** wrote on 2017-05-25T14:26:04.759266+00:00_
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
Contributor guide
Assessment
This issue has not been assessed yet.