cloud-init

identify openstack kvm platform on arm64

Bug #1663304 reported by Scott Moser on 2017-02-09

This bug affects 4 people

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 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

See original description

Tags:

Scott Moser (smoser) on 2017-02-09

Changed in cloud-init:
status:	New → Confirmed
importance:	Undecided → Medium
description:	updated
description:	updated

Scott Moser (smoser) on 2017-02-09

Changed in nova:
status:	New → Confirmed

Ryan Beisner (1chb1n) on 2017-02-09

tags:

added: uosci

Scott Moser (smoser) on 2017-03-03

tags:

added: dsid

Scott Moser (smoser) on 2017-05-25

tags:	added: dsid-nova
description:	updated
description:	updated

Francis Ginther (fginther) on 2017-09-29

tags:

added: id-589affe1b3b9aa29476fe145

Revision history for this message

James Falcon (falcojr) wrote on 2023-05-10:

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/2803

Changed in cloud-init:
status:	Confirmed → Expired

Revision history for this message

Brett Holman (holmanb) wrote on 2024-03-14:

a possible fix? Edit (940 bytes, text/plain)

copied from my response on the cloud-init mailing list:

When this was added, OpenStack was incapable of identifying itself on
non-x86 architectures[1]. The workaround, as you found, was to assume
Openstack is a possible datasource, and pass responsibility to cloud-init.
This unfortunately means that, yes, openstack is assumed on all non-x86
architectures. DMI support on aarch64 has since made its way upstream[2],
however I don't think that anyone has gotten around to verifying whether
OpenStack correctly passes this information through Libvirt.

It looks like Libvirt is aware of aarch64 support for SMBIOS[3], but it doesn't
seem like nova is aware of this yet[4]. I don't know how to go about getting
this fixed, but I naively hope that the attached patch might be a step in the
right direction.

[1] https://bugs.launchpad.net/cloud-init/+bug/1663304
[2] https://bugs.launchpad.net/bugs/1662345
[3] https://github.com/libvirt/libvirt/commit/ec6ce6363a78aaaf6e3aa4c0e2d683d7d0cce183
[4] https://github.com/openstack/nova/blob/db9351ab5191e058994209464aa7fc2b2fa34561/nova/virt/libvirt/driver.py#L6856