'architecture' is one of the "common image properties" that was introduced in Folsom in an effort to standardize use of image metadata. It's not a mistake in the Glance docs, it's just that Nova is looking for a differently named property.
Glance has had a metadata definitions service [0,1] since Juno. It provides a common API for vendors, admins, services, and users to meaningfully define available key / value pair metadata that can be used on different types of resources (images, artifacts, volumes, flavors, aggregates, and other resources). A definition includes a property’s key, its description, its constraints, and the resource types to which it can be associated. It's probably a better place to store this kind of information than in documentation. I think it's under-utilized. [0] https://developer.openstack.org/api-ref/image/v2/metadefs-index.html [1] https://docs.openstack.org/glance/latest/user/metadefs-concepts.html On Wed, Aug 23, 2017 at 5:45 AM, Markus Zoeller <[email protected]> wrote: > On 22.08.2017 17:10, Markus Zoeller wrote: >> I'm wondering if there is an issue in the docs which describe the >> possible image metadata properties: >> https://docs.openstack.org/python-glanceclient/latest/cli/property-keys.html# >> >> This document says to use `architecture` (e.g. x86_64 or s390x or ppc64) >> but the Nova scheduler image properties filter uses `hw_architecture` >> (note the *hw_* prefix): >> https://github.com/openstack/nova/blob/4a7502a5c9e84a8c8cef7f355d72425b26b8c379/nova/scheduler/filters/image_props_filter.py#L44 >> >> Is that simply a mistake in the Glance docs or do I miss some kind of >> conversion between those metadata keys? >> > > Looks like only `hw_architecture` works in my x86 + s390x environment. > I'm going to push an update to the Glance docs + an update to the > `os_image` Ansible module which uses `cpu_arch` in its documentation: > http://docs.ansible.com/ansible/latest/os_image_module.html > > -- > Regards, Markus Zoeller (markus_z) > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
