Seems that Nova is looking for wrong keys from image metadef when
putting this information together.
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1568191
Title:
Pre-defined VirtCPUTopology metadata should have the same name as
flavor extra specs in nova
Status in Glance:
In Progress
Status in OpenStack Compute (nova):
New
Bug description:
If I understand correctly, the concept of flavor extra specs has been
replaced by metadata.
On nova/virt/hardware.py, it's checking for some specific flavor extra
specs in _get_cpu_topology_constraints().
https://github.com/openstack/nova/blob/f396826314b9f37eb57151f0dd8a8e3b7d8a8a5c/nova/virt/hardware.py
These specific flavor extra specs are included in the pre-defined
metadata json so the user can load them with command "glance-manage
db_load_metadefs". However, the names are not exactly the same.
https://github.com/openstack/glance/blob/1c242032fbb26fed3a82691abb030583b4f8940b/etc/metadefs
/compute-vcputopology.json
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1568191/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
