Comment 3 for bug 1855458

Revision history for this message
Ryan Harper (raharper) wrote :

Thanks for filing the bug. It's unfortunate that VIO does not identify that it's running images in OpenStack.

Looking at the output provided, all we can tell is that we're on VMWare, but no indication that it's OpenStack, so cloud-init can't reasonable expect to know that it should enable the OpenStack datasource.

I'm not familiar with the VIO product, but any of the DMI tables which set values could be an option to include OpenStackCompute.

> When using OpenStack VIO (Openstack on VMWARE) the ec2 datasource fallback
> is no longer being used as of this more recent update. OpenStack VIO exposes
> user-data on 169.254.169.254 but now we get a platform unknown

In the above dump of DMI data, is VMware Virtual Platform specific to VIO? and does VIO always expose metadata service?

If so, we could detect/enable OpenStack datasource if we know we're on VIO specifically.