cf0e519a0e
During the implementation of blueprint request-filter-image-types, I left a FIXME to follow-up and add an ability for an operator to configure compute nodes to not expose image formats that they *can* support, for situations where they may not be desired. Consider a remote compute node which *can* support raw images, but for which you want to require that the user use qcow2 for transfer efficiency. This adds a new compute-level config option which allows excluding image types, which will be filtered out of the traits list in a general way, to avoid having to honor the list in each driver. Change-Id: Iabe6246dba212b1a287a82cc0cf16e2e8c8a24b8
10 lines
419 B
YAML
10 lines
419 B
YAML
---
|
|
features:
|
|
- |
|
|
A ``[compute]image_type_exclusion_list`` configuration option was
|
|
added to remove supported image types from being advertised by a
|
|
compute node as supported. This is to be used in conjunction with
|
|
``[scheduler]query_placement_for_image_type_support`` to prevent
|
|
instances from booting on a compute node with a given image type,
|
|
even if the underlying hypervisor supports it.
|