ba083b0c98
This by default would be scheduling to all cells since all cells would be enabled at the time of creation unless specified otherwise. Since the list of enabled cells are stored as a global cache on the host_manager, a reset() handler for the SIGHUP signal has also been added in the scheduler. Hence upon every create-cell/enable-cell/ disable-cell operation the scheduler has to be signaled so that the cache is refreshed. Co-Authored-By: Dan Smith <dms@danplanet.com> Implements blueprint cell-disable Change-Id: I6a9007d172b55238d02da8046311f8dc954703c5
17 lines
785 B
YAML
17 lines
785 B
YAML
---
|
|
features:
|
|
- |
|
|
Support for filtering out disabled cells during scheduling for server
|
|
create requests has been added. Firstly the concept of disabled
|
|
cells has been introduced which means such disabled cells will not be
|
|
candidates for the scheduler. Secondly changes have been made to the filter
|
|
scheduler to ensure that it chooses only the enabled cells for scheduling
|
|
and filters out the disabled ones. Note that operations on existing
|
|
instances already inside a disabled cell like move operations will not be
|
|
blocked.
|
|
upgrade:
|
|
- |
|
|
If the scheduler service is started before the cell mappings are created or
|
|
setup, nova-scheduler needs to be restarted or SIGHUP-ed for the newly
|
|
added cells to get registered in the scheduler cache.
|