documentation doesn't match nova code when image and flavor specify different settings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Fix Released
|
High
|
Chris Friesen |
Bug Description
As part of investigating https:/
This is generally not true, in fact it is exactly backwards. The flavors are created by administrator-level users, while images can be created by regular users. Thus, flavor extra-specs can be used to restrict what regular users are allowed to set in the image properties.
I looked through the docs for cases discussing mismatch between flavor extra-specs and image properties. I found three cases and in all three cases the docs did not match the code.
I'm proposing a fixup to deal with this.
There's one remaining piece that I haven't dealt with, which is what happens when the flavor specifies a cpu threading policy of "prefer" and the image specifies "isolate" or "require". This is still in discussion within the nova team, since the code behaviour was accidentally changed between Mitaka and Newton. Once the nova team sorts it out a final fix will be made to the docs in a separate commit.
Changed in openstack-manuals: | |
importance: | Undecided → High |
milestone: | none → pike |
Changed in openstack-manuals: | |
assignee: | Chris Friesen (cbf123) → Joseph Robinson (joseph-r-email) |
Changed in openstack-manuals: | |
assignee: | Joseph Robinson (joseph-r-email) → Chris Friesen (cbf123) |
Changed in openstack-manuals: | |
assignee: | Chris Friesen (cbf123) → Alexandra Settle (alexandra-settle) |
Changed in openstack-manuals: | |
assignee: | Alexandra Settle (alexandra-settle) → Chris Friesen (cbf123) |
Changed in openstack-manuals: | |
status: | In Progress → Fix Released |
Fix proposed to branch: master /review. openstack. org/461110
Review: https:/