openstack/openstack-manuals
Code Issues Proposed changes

Added note about multiple values for some filters

Browse Source 
The aggregate_image_properties_isolation and aggregate_instance_extra_specs
filters are capable of accepting multiple values as a comma-separated list.
This change specifies that in the documentation. Note that the original bug
touches two other filters as well (aggregate_multitenancy_isolation_filter
and availability_zone_filter), however these aren't mentioned in this book.

Change-Id: If2a3f0757fde2e63a86f5c212579d78f4113ea0e
Closes-Bug: 1427706
This commit is contained in:
Lana Brindley 2015-09-03 16:12:17 +10:00
parent d6d10a5fb7
commit 8db51449a8
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/config-reference/compute/section_compute-scheduler.xml
View File

@ -225,7 +225,8 @@ scheduler_available_filters = myfilter.MyFilter</programlisting>
<systemitem>AggregateImagePropertiesIsolation</systemitem>
filter by using the following options in the
<filename>nova.conf</filename> file:</para>
<programlisting language="ini"># Considers only keys matching the given namespace (string).
<programlisting language="ini"># Considers only keys matching the given
namespace (string). Multiple values can be given, as a comma-separated list.
aggregate_image_properties_isolation_namespace = &lt;None>
# Separator used between the namespace and keys (string).
@ -236,7 +237,8 @@ aggregate_image_properties_isolation_separator = .</programlisting>
<para>Matches properties defined in extra specs for an
instance type against admin-defined properties on a host
aggregate. Works with specifications that are scoped with
<literal>aggregate_instance_extra_specs</literal>. For
<literal>aggregate_instance_extra_specs</literal>. Multiple
values can be given, as a comma-separated list. For
backward compatibility, also works with non-scoped
specifications; this action is highly discouraged because
it conflicts with <link