| 2017-02-09 17:04:07 |
Scott Moser |
bug |
|
|
added bug |
| 2017-02-09 17:05:15 |
Scott Moser |
bug task added |
|
cloud-init |
|
| 2017-02-09 17:05:24 |
Scott Moser |
cloud-init: status |
New |
Confirmed |
|
| 2017-02-09 17:05:28 |
Scott Moser |
cloud-init: importance |
Undecided |
Medium |
|
| 2017-02-10 01:11:47 |
Mikhail S Medvedev |
bug |
|
|
added subscriber Mikhail S Medvedev |
| 2017-02-10 12:18:55 |
Rafael Folco |
bug |
|
|
added subscriber Rafael Folco |
| 2017-02-15 16:12:11 |
Sylvain Bauza |
nova: status |
New |
Opinion |
|
| 2017-02-17 10:52:07 |
Thierry Carrez |
bug |
|
|
added subscriber Thierry Carrez |
| 2017-03-03 02:28:20 |
Scott Moser |
tags |
|
dsid |
|
| 2017-03-30 12:44:35 |
Markus Zoeller (markus_z) |
tags |
dsid |
dsid s390x |
|
| 2017-05-25 14:23:49 |
Scott Moser |
description |
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
bug 1661797: identify lxd-nova platform to enable Openstack datasource
bug 1661693: identify brightbox platform to enable Ec2 datasource
bug 1663304: identify openstack kvm platform on arm64
bug 1662345: [qemu] smbios parameter settings not visible in guest |
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
bug 1661797: identify lxd-nova platform to enable Openstack datasource
bug 1661693: identify brightbox platform to enable Ec2 datasource
bug 1663304: identify openstack kvm platform on arm64
bug 1662345: [qemu] smbios parameter settings not visible in guest
bug 1663315: identify openstack kvm platform on ppc64 |
|
| 2017-05-25 14:24:05 |
Scott Moser |
tags |
dsid s390x |
dsid dsid-nova s390x |
|
| 2017-05-25 14:24:23 |
Scott Moser |
description |
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
bug 1661797: identify lxd-nova platform to enable Openstack datasource
bug 1661693: identify brightbox platform to enable Ec2 datasource
bug 1663304: identify openstack kvm platform on arm64
bug 1662345: [qemu] smbios parameter settings not visible in guest
bug 1663315: identify openstack kvm platform on ppc64 |
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
bug 1661797: identify lxd-nova platform to enable Openstack datasource
bug 1661693: identify brightbox platform to enable Ec2 datasource
bug 1663304: identify openstack kvm platform on arm64
bug 1662345: [qemu] smbios parameter settings not visible in guest
bug 1663315: identify openstack kvm platform on ppc64 |
|
| 2017-05-25 14:28:42 |
Scott Moser |
tags |
dsid dsid-nova s390x |
dsid dsid-nova |
|
| 2017-05-25 14:31:28 |
Scott Moser |
description |
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
bug 1661797: identify lxd-nova platform to enable Openstack datasource
bug 1661693: identify brightbox platform to enable Ec2 datasource
bug 1663304: identify openstack kvm platform on arm64
bug 1662345: [qemu] smbios parameter settings not visible in guest
bug 1663315: identify openstack kvm platform on ppc64 |
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 |
|
| 2023-05-10 20:09:56 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/2804 |
|
| 2023-05-10 20:09:57 |
James Falcon |
cloud-init: status |
Confirmed |
Expired |
|
