
Preemptible instances run on a configurable host aggregate, using the freepool by default. Compared to the proposed spec, the use of a separate aggregate allows to better control scheduling of preemptibles. For example, we can prevent preemptible instances from being launched on hosts that are about to be used by reservations. To be used, this feature will need additional support in the main Blazar service. Blueprint: blazar-preemptible-instances Change-Id: I294c22b22a1d9e3df01c56a518476a33782d1196
8 lines
276 B
YAML
8 lines
276 B
YAML
---
|
|
features:
|
|
- |
|
|
Adds support for running preemptible instances on unreserved Blazar hosts.
|
|
This functionality is disabled by default and can be enabled using
|
|
``[blazar:physical:host]/allow_preemptibles``. It also needs to be enabled
|
|
in the Blazar service.
|