openstack/zun
Code Issues Proposed changes

enable RuntimeFilter

Browse Source 
Change-Id: I6c0a483b76ec7cb024aee4620c5c7480528d5012
Partially-Implements: blueprint runtime-aware-scheduling
Depends-On: I513c3b7088fa09cc14a9a541609bfa0f2b0bad60
This commit is contained in:
Feng Shengqin 2018-08-07 10:03:24 +08:00 committed by feng.shengqin
parent d5f8e86d9b
commit 5b9eb5ef8b
2 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/user/filter-scheduler.rst
View File

@ -31,6 +31,8 @@ There are many standard filter classes which may be used
labels.
* ComputeFilter - filters hosts that are operational and enabled. In general,
you should always enable this filter.
* RuntimeFilter - filters hosts by their runtime. It passes hosts with
the specified runtime.
Configuring Filters
-------------------
@ -47,7 +49,7 @@ The default values for these settings in zun.conf are:
::
--filter_scheduler.available_filters=zun.scheduler.filters.all_filters
--filter_scheduler.enabled_filters=RamFilter,CPUFilter,ComputeFilter
--filter_scheduler.enabled_filters=RamFilter,CPUFilter,ComputeFilter,RuntimeFilter
With this configuration, all filters in ``zun.scheduler.filters``
would be available, and by default the RamFilter and CPUFilter would be

1
zun/conf/scheduler.py
View File

@ -68,6 +68,7 @@ Related options:
"RamFilter",
"ComputeFilter",
"DiskFilter",
"RuntimeFilter",
],
help="""
Filters that the scheduler will use.