identify openstack kvm platform on arm64

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

Launchpad details

affected_projects = ['nova']

assignee = None

assignee_name = None

date_closed = None

date_created = 2017-02-09T16:30:07.568412+00:00

date_fix_committed = None

date_fix_released = None

id = 1663304

importance = medium

is_complete = False

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

milestone = None

owner = smoser

owner_name = Scott Moser

private = False

status = confirmed

submitter = smoser

submitter_name = Scott Moser

tags = ['dsid', 'dsid-nova', 'id-589affe1b3b9aa29476fe145', 'uosci']

duplicates = []

_Launchpad user **Scott Moser(smoser)** wrote on 2017-02-09T16:30:07.568412+00:00_

On i386 and amd64, openstack puts 'OpenStack Nova', into the dmi platform
information. OpenStack using kvm on arm64, does not identify itself to the
guest in any way.

The result is that OpenStack nodes will not attempt to reach the metadata
service and will be unusable.

We need two things
 a.) change openstack to provide that information through libvirt on arm.
 b.) fix qemu bug 1662345 that prevents the information from getting to the guest.

Related bugs:
 bug 1660385: Alert user of Ec2 Datasource on lookalike cloud
 bug 1662345: [qemu] smbios parameter settings not visible in guest
 https://bugs.launchpad.net/cloud-init/+bugs?field.tag=dsid-nova

Review Launchpad bug 1663304 and the related QEMU bug 1662345 first. The issue spans OpenStack Nova, libvirt, QEMU, and cloud-init on arm64, so determine which project owns each required change. Done means OpenStack KVM identifies itself to the guest and cloud-init can reach the metadata service.

Written by the indexing model from the issue text.