identify openstack kvm platform on ppc64

This bug was originally filed in Launchpad as [LP: #1663315](https://bugs.launchpad.net/cloud-init/+bug/1663315)

Launchpad details

affected_projects = ['nova']

assignee = None

assignee_name = None

date_closed = None

date_created = 2017-02-09T17:04:07.160715+00:00

date_fix_committed = None

date_fix_released = None

id = 1663315

importance = medium

is_complete = False

lp_url = https://bugs.launchpad.net/cloud-init/+bug/1663315

milestone = None

owner = smoser

owner_name = Scott Moser

private = False

status = confirmed

submitter = smoser

submitter_name = Scott Moser

tags = ['dsid', 'dsid-nova']

duplicates = []

_Launchpad user **Scott Moser(smoser)** wrote on 2017-02-09T17:04:07.160715+00:00_

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:
 bug 1660385: Alert user of Ec2 Datasource on lookalike cloud
https://bugs.launchpad.net/cloud-init/+bugs?field.tag=dsid-nova

Start with Launchpad LP #1663315 and the issue's description of OpenStack, libvirt, QEMU, and ppc64 identity. The payload names no file, test, or entry point and proposes changes across projects. Done means cloud-init can reliably identify OpenStack on ppc64 or ppc64el guests.

Written by the indexing model from the issue text.