On 4/23/2018 4:43 PM, Jay Pipes wrote:
How about just having the conductor call GET /resource_providers?in_tree=<CN_UUID>&required=<IMAGE_TRAITS>, see if there is a result, and if not, don't even call the scheduler at all (because conductor would already know there would be a NoValidHost returned)?

This makes filtering on image properties required, which is something I was pushing back on because the ImagePropertiesFilter today, by design of all scheduler filters, is configurable and optional, which is why I wanted to add the filtering logic for image-defined required traits into the ImagePropertiesFilter itself.




OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to