aa5b1326c8
When using ImagePropertiesFilter with multiple architectures inside the same deployment, it is possible that images can be uploaded without the hw_architecture property defined. This results in behaviour where the instance could be scheduled on any type of hypervisor, resulting in an instance that will successfully transition to ACTIVE but never properly run because of the difference in architecture. This makes the ImagePropertiesFilter problematic as most images are generally uploaded without the architecture property set because most documentation does not encourage doing that. The addition of this flag allows to make using the filter possible because it allows the deployer to assume a default architecture if the user did not supply one (assuming it would be the most common architecture in their deployment, such as x86_64) yet if the user wants a more specific architecture, they can do it in their image properties. In order to avoid a circular import loop, the references to the architecture field have been moved to a seperate module so that they can be properly and cleaned imported inside configuration. Change-Id: Ib52deb095028e93619b93ef9e5f70775df2a403a Closes-Bug: #1769283
10 lines
497 B
YAML
10 lines
497 B
YAML
---
|
|
fixes:
|
|
- The behaviour of ImagePropertiesFilter when using multiple architectures
|
|
in a cloud can be unpredictable for a user if they forget to set the
|
|
architecture property in their image. Nova now allows the deployer to
|
|
specify a fallback in ``[filter_scheduler]image_properties_default_architecture``
|
|
to use a default architecture if none is specified. Without this, it
|
|
is possible that a VM would get scheduled on a compute node that does not
|
|
support the image.
|