diff --git a/doc/config-reference/compute/section_compute-scheduler.xml b/doc/config-reference/compute/section_compute-scheduler.xml index 2845a9377e..88b8cddb2f 100644 --- a/doc/config-reference/compute/section_compute-scheduler.xml +++ b/doc/config-reference/compute/section_compute-scheduler.xml @@ -435,6 +435,20 @@ aggregate_image_properties_isolation_separator=. isolated_hosts=server1,server2 isolated_images=342b492c-128f-4a42-8d3a-c5088cf27d13,ebd267a6-ca86-4d6c-9a0e-bd132d6b7d09 +
+ IoOpsFilter + + The IoOpsFilter filters hosts by concurrent I/O operations + on it. Hosts with too many concurrent I/O operations will + be filtered out. The + option specifies the maximum number of I/O intensive + instances allowed to run on a host. A host will be ignored + by the scheduler if more than + instances in build, + resize, snapshot, migrate, rescue or unshelve task states + are running on it. + +
JsonFilter The JsonFilter allows a user to construct a custom @@ -492,6 +506,22 @@ isolated_images=342b492c-128f-4a42-8d3a-c5088cf27d13,ebd267a6-ca86-4d6c-9a0e-bd1 os:scheduler_hints key:
+
+ NumInstancesFilter + + Hosts that have more instances running than specified by + the option are + filtered out when this filter is in place. + +
+
+ PciPassthroughFilter + + The filter schedules instances on a host if the host has + devices that meet the device requests in the + extra_specs attribute for the flavor. + +
RamFilter Only schedules instances on hosts that have