1. Description
The operator provides public images to the users and users can also add their own images in glance and use these images to launch VMs. As an operator, all images provided by an operator should be launched on a specific set of compute nodes whereas images that are created by non-admin users should be launched on other set of compute nodes. The decision to launch VMs on certain compute nodes will be decided based on image metadata. When an operator will create images, they can specify certain image metadata which will be used by placement api or scheduler service to decide where the vm should be launched but if user creates image, there is no way user will know what image metadata properties to set and hence in the present placement api and scheduler logic, it is possible to launch a VM on any compute nodes. This is a big problem.
3. Upstream reference
Bugzillas? No
Blueprints? Yes https://blueprints.launchpad.net/glance/+spec/inject-automatic-metadata
Specs? No
4. RH bugzilla dependencies?
No
5. Primary Red Hat contact:
a. Name: MD Sufiyan
b. Email: msufiyan
Adding a link to the merged lite-spec.
Someone upstream seems assigned to this feature. Depending on when the upstream patches merge, we may or may not have time to test and include this feature in Queens.
Comment 3Christian Schwede (cschwede)
2018-03-07 12:22:01 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2019:0045
1. Description The operator provides public images to the users and users can also add their own images in glance and use these images to launch VMs. As an operator, all images provided by an operator should be launched on a specific set of compute nodes whereas images that are created by non-admin users should be launched on other set of compute nodes. The decision to launch VMs on certain compute nodes will be decided based on image metadata. When an operator will create images, they can specify certain image metadata which will be used by placement api or scheduler service to decide where the vm should be launched but if user creates image, there is no way user will know what image metadata properties to set and hence in the present placement api and scheduler logic, it is possible to launch a VM on any compute nodes. This is a big problem. 3. Upstream reference Bugzillas? No Blueprints? Yes https://blueprints.launchpad.net/glance/+spec/inject-automatic-metadata Specs? No 4. RH bugzilla dependencies? No 5. Primary Red Hat contact: a. Name: MD Sufiyan b. Email: msufiyan