From 5b9eb5ef8bb9eb00f11b6a559466d62056f527fa Mon Sep 17 00:00:00 2001 From: Feng Shengqin Date: Tue, 7 Aug 2018 10:03:24 +0800 Subject: [PATCH] enable RuntimeFilter Change-Id: I6c0a483b76ec7cb024aee4620c5c7480528d5012 Partially-Implements: blueprint runtime-aware-scheduling Depends-On: I513c3b7088fa09cc14a9a541609bfa0f2b0bad60 --- doc/source/user/filter-scheduler.rst | 4 +++- zun/conf/scheduler.py | 1 + 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/source/user/filter-scheduler.rst b/doc/source/user/filter-scheduler.rst index 2995c9a7f..7d7829f85 100644 --- a/doc/source/user/filter-scheduler.rst +++ b/doc/source/user/filter-scheduler.rst @@ -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 diff --git a/zun/conf/scheduler.py b/zun/conf/scheduler.py index 37b533aa4..366d7d4fa 100644 --- a/zun/conf/scheduler.py +++ b/zun/conf/scheduler.py @@ -68,6 +68,7 @@ Related options: "RamFilter", "ComputeFilter", "DiskFilter", + "RuntimeFilter", ], help=""" Filters that the scheduler will use.