Gemfury

triliodata-4-0-patch / contego deb

Repository URL to install this package:

Details

contego / home / tvault / .virtenv / lib / python2.7 / site-packages / nova / conf / scheduler.pyc

ó
±EYc@smddlmZdZdZdZejddddd Zejd
dddd
dddddgddZej dde
ddZejdddgddZ
ejddddddd
ddddg ddZejddd gdd!Zej d"dedd#Zejd$dd%dd&Zejd'dd(dd)Zejd*dd+d,dqdd.Zejd/dd0dd1Zejd2dd3dd4Zejd5dgdd6Zejd7dgdd8Zej d9dedd:Zejd;dd<ejd=dd>ejd?dd@ddAejdBddCddDejdEddFejdGdd3ddHej dIde
ddJgZejdKddLddMZejdNddOZejdPddQddRZejdSddTddUZej dVddWddXZ!ej dYddWddZZ"ej d[dd\dd]Z#ej d^ddWdd_ejd`dgddaej dbdeddcej ddde$deddfgZ%ejdgddhddiZ&ej djddWddkZ'ej dlddWddmZ(eeee
eeeeeeeeeeeeeeee!e"e#e&e'e(gZ)dnZ*doZ+dpS(riÿÿÿÿ(tcfgtDEFAULTtmetricsttrusted_computingtscheduler_host_subset_sizetdefaultithelps
New instances will be scheduled on a host chosen randomly from a subset of the
N best hosts, where N is the value set by this option. Valid values are 1 or
greater. Any value less than one will be treated as 1.

Setting this to a value greater than 1 will reduce the chance that multiple
scheduler processes handling similar requests will select the same host,
creating a potential race condition. By selecting a host randomly from the N
hosts that best fit the request, the chance of a conflict is reduced. However,
the higher you set this value, the less optimal the chosen host may be for a
given request.

This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.

* Related options:

None
t#baremetal_scheduler_default_filterstRetryFiltertAvailabilityZoneFiltert
ComputeFiltertComputeCapabilitiesFiltertImagePropertiesFiltertExactRamFiltertExactDiskFiltertExactCoreFilters%
This option specifies the filters used for filtering baremetal hosts. The value
should be a list of strings, with each string being the name of a filter class
to be used. When used, they will be applied in order, so place your most
restrictive filters first to make the filtering process more efficient.

This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.

* Related options:

If the 'scheduler_use_baremetal_filters' option is False, this option has
no effect.
tscheduler_use_baremetal_filterss6
Set this to True to tell the nova scheduler that it should use the filters
specified in the 'baremetal_scheduler_default_filters' option. If you are not
scheduling baremetal nodes, leave this at the default setting of False.

This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.

* Related options:

If this option is set to True, then the filters specified in the
'baremetal_scheduler_default_filters' are used instead of the filters
specified in 'scheduler_default_filters'.
tscheduler_available_filterss"nova.scheduler.filters.all_filterssU
This is an unordered list of the filter classes the Nova scheduler may apply.
Only the filters specified in the 'scheduler_default_filters' option will be
used, but any filter appearing in that option must also be included in this
list.

By default, this is set to all filters that are included with Nova. If you wish
to change this, replace this with a list of strings, where each element is the
path to a filter.

This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.

* Related options:

scheduler_default_filters
tscheduler_default_filterst RamFiltert
DiskFiltertServerGroupAntiAffinityFiltertServerGroupAffinityFilters¨
This option is the list of filter class names that will be used for filtering
hosts. The use of 'default' in the name of this option implies that other
filters may sometimes be used, but that is not the case. These filters will be
applied in the order they are listed, so place your most restrictive filters
first to make the filtering process more efficient.

This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.

* Related options:

All of the filters in this option *must* be present in the
'scheduler_available_filters' option, or a SchedulerHostFilterNotFound
exception will be raised.
tscheduler_weight_classess#nova.scheduler.weights.all_weigherssË
This is a list of weigher class names. Only hosts which pass the filters are
weighed. The weight for any host starts at 0, and the weighers order these
hosts by adding to or subtracting from the weight assigned by the previous
weigher. Weights may become negative.

An instance will be scheduled to one of the N most-weighted hosts, where N is
'scheduler_host_subset_size'.

By default, this is set to all weighers that are included with Nova. If you
wish to change this, replace this with a list of strings, where each element is
the path to a weigher.

This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.

* Related options:

None
t!scheduler_tracks_instance_changessÒ
The scheduler may need information about the instances on a host in order to
evaluate its filters and weighers. The most common need for this information is
for the (anti-)affinity filters, which need to choose a host based on the
instances already running on a host.

If the configured filters and weighers do not need this information, disabling
this option will improve performance. It may also be disabled when the tracking
overhead proves too heavy, although this will cause classes requiring host
usage data to query the database on each request instead.

This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.

* Related options:

None
tscheduler_topict schedulers
This is the message queue topic that the scheduler 'listens' on. It is used
when the scheduler service is started up to configure the queue, and whenever
an RPC call to the scheduler is made. There is almost never any reason to ever
change this value.

* Related options:

None
tscheduler_json_config_locationtsc
The absolute path to the scheduler configuration JSON file, if any. This file
location is monitored by the scheduler for changes and reloads it if needed. It
is converted from JSON to a Python data structure, and passed into the
filtering and weighing functions of the scheduler, which can use it for dynamic
configuration.

* Related options:

None
tscheduler_host_managerthost_managertchoicestironic_host_managersö
The scheduler host manager to use, which manages the in-memory picture of the
hosts that the scheduler uses.

The option value should be chosen from one of the entrypoints under the
namespace 'nova.scheduler.host_manager' of file 'setup.cfg'. For example,
'host_manager' is the default setting. Aside from the default, the only other
option as of the Mitaka release is 'ironic_host_manager', which should be used
if you're using Ironic to provision bare-metal instances.

* Related options:

None
tscheduler_drivertfilter_schedulers
The class of the driver used by the scheduler. This should be chosen from one
of the entrypoints under the namespace 'nova.scheduler.driver' of file
'setup.cfg'. If nothing is specified in this option, the 'filter_scheduler' is
used.

This option also supports deprecated full Python path to the class to be used.
For example, "nova.scheduler.filter_scheduler.FilterScheduler". But note: this
support will be dropped in the N Release.

Other options are:

* 'caching_scheduler' which aggressively caches the system state for better
individual scheduler performance at the risk of more retries when running
multiple schedulers.

* 'chance_scheduler' which simply picks a host at random.

* 'fake_scheduler' which is used for testing.

* Related options:

None
tscheduler_driver_task_periodi<se
This value controls how often (in seconds) to run periodic tasks in the
scheduler. The specific tasks that are run for each period are determined by
the particular scheduler being used.

If this is larger than the nova-service 'service_down_time' setting, Nova may
report the scheduler service as down. This is because the scheduler driver is
responsible for sending a heartbeat and it will only do that as often as this
option allows. As each scheduler can work a little differently than the others,
be sure to test this with your selected scheduler.

* Related options:

``nova-service service_down_time``
tisolated_imagessÃ
If there is a need to restrict some images to only run on certain designated
hosts, list those image UUIDs here.

* Related options:

scheduler/isolated_hosts
scheduler/restrict_isolated_hosts_to_isolated_images
tisolated_hostssÃ
If there is a need to restrict some images to only run on certain designated
hosts, list those host names here.

* Related options:

scheduler/isolated_images
scheduler/restrict_isolated_hosts_to_isolated_images
t*restrict_isolated_hosts_to_isolated_imagess

This setting determines if the scheduler's isolated_hosts filter will allow
non-isolated images on a host designated as an isolated host. When set to True
(the default), non-isolated images will not be allowed to be built on isolated
hosts. When False, non-isolated images can be built on both isolated and
non-isolated hosts alike.

This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect. Also note that this setting
only affects scheduling if the 'IsolatedHostsFilter' filter is enabled. Even
then, this option doesn't affect the behavior of requests for isolated images,
which will *always* be restricted to isolated hosts.

* Related options:

scheduler/isolated_images
scheduler/isolated_hosts
tattestation_servers_
The host to use as the attestation server.

Cloud computing pools can involve thousands of compute nodes located at
different geographical locations, making it difficult for cloud providers to
identify a node's trustworthiness. When using the Trusted filter, users can
request that their VMs only be placed on nodes that have been verified by the
attestation server specified in this option.

The value is a string, and can be either an IP address or FQDN.

* Related options:

attestation_server_ca_file
attestation_port
attestation_api_url
attestation_auth_blob
attestation_auth_timeout
attestation_insecure_ssl
tattestation_server_ca_files¡
The absolute path to the certificate to use for authentication when connecting
to the attestation server. See the `attestation_server` help text for more
information about host verification.

The value is a string, and must point to a file that is readable by the
scheduler.

* Related options:

attestation_server
attestation_port
attestation_api_url
attestation_auth_blob
attestation_auth_timeout
attestation_insecure_ssl
tattestation_portt8443sj
The port to use when connecting to the attestation server. See the
`attestation_server` help text for more information about host verification.

Valid values are strings, not integers, but must be digits only.

* Related options:

attestation_server
attestation_server_ca_file
attestation_api_url
attestation_auth_blob
attestation_auth_timeout
attestation_insecure_ssl
tattestation_api_urls /OpenAttestationWebServices/V1.0s
The URL on the attestation server to use. See the `attestation_server` help
text for more information about host verification.

This value must be just that path portion of the full URL, as it will be joined
to the host specified in the attestation_server option.

* Related options:

attestation_server
attestation_server_ca_file
attestation_port
attestation_auth_blob
attestation_auth_timeout
attestation_insecure_ssl
tattestation_auth_blobsô
Attestation servers require a specific blob that is used to authenticate. The
content and format of the blob are determined by the particular attestation
server being used. There is no default value; you must supply the value as
specified by your attestation service. See the `attestation_server` help text
for more information about host verification.

* Related options:

attestation_server
attestation_server_ca_file
attestation_port
attestation_api_url
attestation_auth_timeout
attestation_insecure_ssl
tattestation_auth_timeoutsG
This value controls how long a successful attestation is cached. Once this
period has elapsed, a new attestation request will be made. See the
`attestation_server` help text for more information about host verification.

The value is in seconds. Valid values must be positive integers for any
caching; setting this to zero or a negative value will result in calls to the
attestation_server for every request, which may impact performance.

* Related options:

attestation_server
attestation_server_ca_file
attestation_port
attestation_api_url
attestation_auth_blob
attestation_insecure_ssl
tattestation_insecure_sslsw
When set to True, the SSL certificate verification is skipped for the
attestation service. See the `attestation_server` help text for more
information about host verification.

Valid values are True or False. The default is False.

* Related options:

attestation_server
attestation_server_ca_file
attestation_port
attestation_api_url
attestation_auth_blob
attestation_auth_timeout
tmax_io_ops_per_hostis

This setting caps the number of instances on a host that can be actively
performing IO (in a build, resize, snapshot, migrate, rescue, or unshelve task
state) before that host becomes ineligible to build new instances.

Valid values are positive integers: 1 or greater.

* Related options:

None
t.aggregate_image_properties_isolation_namespaces
Images and hosts can be configured so that certain images can only be scheduled
to hosts in a particular aggregate. This is done with metadata values set on
the host aggregate that are identified by beginning with the value of this
option. If the host is part of an aggregate with such a metadata key, the image
in the request spec must have the value of that metadata in its properties in
order for the scheduler to consider the host as acceptable.

Valid values are strings.

* Related options:

aggregate_image_properties_isolation_separator
t.aggregate_image_properties_isolation_separatort.s
When using the aggregate_image_properties_isolation filter, the relevant
metadata keys are prefixed with the namespace defined in the
aggregate_image_properties_isolation_namespace configuration option plus a
separator. This option defines the separator to be used. It defaults to a
period ('.').

Valid values are strings.

* Related options:

aggregate_image_properties_isolation_namespace
tmax_instances_per_hosti2sy
If you need to limit the number of instances on any given host, set this option
to the maximum number of instances you want to allow. The num_instances_filter
will reject any host that has at least as many instances as this option's
value.

Valid values are positive integers; setting it to zero will cause all hosts to
be rejected if the num_instances_filter is active.

* Related options:

None
tram_weight_multipliergð?s
This option determines how hosts with more or less available RAM are weighed. A
positive value will result in the scheduler preferring hosts with more
available RAM, and a negative number will result in the scheduler preferring
hosts with less available RAM. Another way to look at it is that positive
values for this option will tend to spread instances across many hosts, while
negative values will tend to fill up (stack) hosts as much as possible before
scheduling to a less-used host. The absolute value, whether positive or
negative, controls how strong the RAM weigher is relative to other weighers.

Valid values are numeric, either integer or float.

* Related options:

None
tdisk_weight_multipliersWMultiplier used for weighing free disk space. Negative numbers mean to stack vs spread.tio_ops_weight_multipliergð¿sk
This option determines how hosts with differing workloads are weighed. Negative
values, such as the default, will result in the scheduler preferring hosts with
lighter workloads whereas positive values will prefer hosts with heavier
workloads. Another way to look at it is that positive values for this option
will tend to schedule instances onto hosts that are already busy, while
negative values will tend to distribute the workload across more hosts. The
absolute value, whether positive or negative, controls how strong the io_ops
weigher is relative to other weighers.

Valid values are numeric, either integer or float.

* Related options:

None
tweight_multipliers¤
When using metrics to weight the suitability of a host, you can use this option
to change how the calculated weight influences the weight assigned to a host as
follows:

* Greater than 1.0: increases the effect of the metric on overall weight.

* Equal to 1.0: No change to the calculated weight.

* Less than 1.0, greater than 0: reduces the effect of the metric on
overall weight.

* 0: The metric value is ignored, and the value of the
'weight_of_unavailable' option is returned instead.

* Greater than -1.0, less than 0: the effect is reduced and reversed.

* -1.0: the effect is reversed

* Less than -1.0: the effect is increased proportionally and reversed.

Valid values are numeric, either integer or float.

This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.

* Related options:

weight_of_unavailable
tweight_settings7
This setting specifies the metrics to be weighed and the relative ratios for
each metric. This should be a single string value, consisting of a series of
one or more 'name=ratio' pairs, separated by commas, where 'name' is the name
of the metric to be weighed, and 'ratio' is the relative weight for that
metric.

Note that if the ratio is set to 0, the metric value is ignored, and instead
the weight will be set to the value of the 'weight_of_unavailable' option.

As an example, let's consider the case where this option is set to:

``name1=1.0, name2=-1.3``

The final weight will be:

``(name1.value * 1.0) + (name2.value * -1.3)``

This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.

* Related options:

weight_of_unavailable
trequireds-
This setting determines how any unavailable metrics are treated. If this option
is set to True, any hosts for which a metric is unavailable will raise an
exception, so it is recommended to also use the MetricFilter to filter out
those hosts before weighing.

When this option is False, any metric being unavailable for a host will set the
host weight to 'weight_of_unavailable'.

This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.

* Related options:

weight_of_unavailable
tweight_of_unavailablegÃÀs)
When any of the following conditions are met, this value will be used in place
of any actual metric value:

* One of the metrics named in 'weight_setting' is not available for a host,
and the value of 'required' is False.

* The ratio specified for a metric in 'weight_setting' is 0.

* The 'weight_multiplier' option is set to 0.

This option is only used by the FilterScheduler and its subclasses; if you use
a different scheduler, this option has no effect.

* Related options:

weight_setting
required
weight_multiplier
tscheduler_max_attemptsis
This is the maximum number of attempts that will be made to schedule an
instance before it is assumed that the failures aren't due to normal occasional
race conflicts, but rather some other problem. When this is reached a
MaxRetriesExceeded exception is raised, and the instance is set to an error
state.

Valid values are positive integers (1 or greater).

* Related options:

None
tsoft_affinity_weight_multipliers»Multiplier used for weighing hosts for group soft-affinity. Only a positive value is meaningful. Negative means that the behavior will change to the opposite, which is soft-anti-affinity.t$soft_anti_affinity_weight_multipliers»Multiplier used for weighing hosts for group soft-anti-affinity. Only a positive value is meaningful. Negative means that the behavior will change to the opposite, which is soft-affinity.cCs\|jttjdtdd}|j||jtd||jtdtdS(NtnamettitlesTrust parameterstgroup( t
register_optstdefault_optsRtOptGrouptTRUSTED_GROUP_NAMEtregister_groupttrusted_optstmetrics_weight_optstMETRICS_GROUP_NAME(tconfttrust_group((sH/home/tvault/.virtenv/lib/python2.7/site-packages/nova/conf/scheduler.pyRAs

cCsitt6tt6tt6S(N(RBtDEFAULT_GROUP_NAMERFRDRGRH(((sH/home/tvault/.virtenv/lib/python2.7/site-packages/nova/conf/scheduler.pyt list_opts s
N(RR (,toslo_configRRKRHRDtIntOptthost_subset_size_opttListOpttbm_default_filter_opttBoolOpttFalsetuse_bm_filters_opttMultiStrOptthost_mgr_avail_filt_optthost_mgr_default_filt_optthost_mgr_sched_wgt_cls_opttTruethost_mgr_tracks_inst_chg_opttStrOpttrpc_sched_topic_optt"scheduler_json_config_location_opttsched_driver_host_mgr_optt
driver_opttdriver_period_opttisolated_img_opttisolated_host_opttrestrict_iso_host_img_optRFtmax_io_ops_per_host_opttagg_img_prop_iso_namespace_opttagg_img_prop_iso_separator_opttmax_instances_per_host_opttFloatOpttram_weight_mult_opttdisk_weight_mult_opttio_ops_weight_mult_opttfloatRGtscheduler_max_att_opttsoft_affinity_weight_opttsoft_anti_affinity_weight_optRBRARL(((sH/home/tvault/.virtenv/lib/python2.7/site-packages/nova/conf/scheduler.pyt<module>s6

triliodata-4-0-patch / contego deb

Products

About

Resources

Contact Gemfury