Bug 1391992 - Unify flavor/image keys/properties
Summary: Unify flavor/image keys/properties
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 9.0 (Mitaka)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: RHOS Documentation Team
QA Contact: RHOS Documentation Team
Don Domingo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-04 14:39 UTC by Marko Myllynen
Modified: 2022-08-11 12:10 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-06 11:04:43 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-5846 0 None None None 2022-08-11 12:10:23 UTC

Description Marko Myllynen 2016-11-04 14:39:04 UTC
Description of problem:
For example the following image properties that can be set:

hw_qemu_guest_agent
hw_vif_model
hw_vif_multiqueue_enabled
hw_watchdog_action

But only the following corresponding flavor key has effect:

hw:watchdog_action

It's unclear is there any reason for this distinction.

It would be nice of this distinction could be either documented properly (e.g., mention whether a key or a property can be used only with images or flavors or with both) or implement support for the currently unrecognised flavor keys which already are working as image properties.

There are also some properties which do not follow the above naming convention, like os_require_quiesce (but see bug 1385748), it would be nice to be able to set these as well on flavor basis.

Thanks.


Note You need to log in before you can comment on or make changes to this bug.