ó
±EYc@sôdd
lZddl
mZ
ddlmZ
ejddeddƒ
ejddd	ƒ

ejd
dddgdd
ƒ
ejdddddƒ
ejdddddƒ
ej	dddddƒ
ej
ddeddddƒ
ejddgddƒ
gZej	ddd dd dd!ƒ
ej	d"dd dd#dd$ƒ
ejd%dd&dedd'ƒ
gZ
ejd(dd)dd*ƒ
ejd+dd)dd,ƒ
ejd-dd)dd.ƒ
gZejd/dejƒd0d1dd2ƒ
ejd3dd4ƒ

ejd5dedd6ƒ
ejd7dejd8ƒ
d0d9dd:ƒ
ejd;dedd<ƒ
ej	d=dd dd>dd?ƒ
ejd@deddAƒ
ej	dBdd dd ddCƒ
ej	dDdd ddEddFƒ
ej	dGddHddIƒ
ej	dJddKddLƒ
ej	dMddNddOƒ
gZej	dPddQddRƒ
ej	dSddQddTƒ
ej	dUddKddVƒ
ej	dWdd dd ddXƒ
ej	dYdd ddZƒ
ej	d[dd\dd]ƒ
ej	d^dd dd_ƒ
ej	d`ddaddbƒ
ej	dcdddddƒ
ej	deddfddgƒ
ej	dhdd ddiƒ
gZej	djdd dd ddkƒ
ej	dldd dd ddmƒ
ej	dndd dd ddoƒ
ej	dpdd dd ddqƒ
ej	drddKddHddsƒ
gZejdtddudvd–ddzƒ
ej	d{dd|dd}ƒ
ej	d~dd ddƒ
gZej	d€dddd‚ƒ
g
Zejdƒdd„dd…ƒ
g
Zejd†dd‡dvd‡dˆd‰gddŠƒ
ejd‹deddŒƒ
ejdddŽddƒ
ejddd‘dedd’dd“ƒ
gZee
eeeeeeeeZd”„Zd•„Zd
S(—iÿÿÿÿN(
tcfg(
tpathstallow_resize_to_same_hosttdefaultthelpsð
Allow destination machine to match source for resize. Useful when
testing in single-host environments. By default it is not allowed
to resize to the same host. Setting this option to true will add
the same host to the destination options.
tdefault_schedule_zonesD

Availability zone to use when user doesn't specify one.

This option is used by the scheduler to determine which availability
zone to place a new VM instance into if the user did not specify one
at the time of VM boot request.

Possible values:

* Any string representing an availability zone name
* Default value is None.
t non_inheritable_image_propertiest
cache_in_novat
bittorrentsì

Image properties that should not be inherited from the instance
when taking a snapshot.

This option gives an opportunity to select which image-properties
should not be inherited by newly created snapshots.

Possible values:

* A list whose item is an image property. Usually only the image
  properties that are only needed by base images can be included
  here, since the snapshots that are created from the base images
  doesn't need them.
* Default list: ['cache_in_nova', 'bittorrent']
tnull_kerneltnokernels

This option is used to decide when an image should have no external
ramdisk or kernel. By default this is set to 'nokernel', so when an
image is booted with the property 'kernel_id' with the value
'nokernel', Nova assumes the image doesn't require an external kernel
and ramdisk.
t$multi_instance_display_name_templates%(name)s-%(count)dsv

When creating multiple instances with a single request using the
os-multiple-create API extension, this template will be used to build
the display name for each instance. The benefit is that the instances
end up with different hostnames. Example display names when creating
two VM's: name-1, name-2.

Possible values:

* Valid keys for the template are: name, uuid, count.
tmax_local_block_devicesis1
Maximum number of devices that will result in a local image being
created on the hypervisor node.

A negative number means unlimited. Setting max_local_block_devices
to 0 means that any request that attempts to create a local disk
will fail. This option is meant to limit the number of local discs
(so root local disc that is the result of --image being used, and
any other ephemeral and swap disks). 0 does not mean that images
will be automatically converted to volumes and boot instances from
volumes - it just means that all requests that attempt to create a
local disk will fail.

Possible values:

* 0: Creating a local disk is not allowed.
* Negative number: Allows unlimited number of local discs.
* Positive number: Allows only these many number of local discs.
                       (Default value is 3).
tcompute_available_monitorstdeprecated_for_removaltdeprecated_reasonslstevedore and setuptools entry points now allow a set of plugins to be specified without this config option.s¾
Monitor classes available to the compute which may be specified more than once.
This option is DEPRECATED and no longer used. Use setuptools entry points to
list available monitor plugins.
tcompute_monitorssñ

A list of monitors that can be used for getting compute metrics.
You can use the alias/name from the setuptools entry points for
nova.compute.monitors.* namespaces. If no namespace is supplied,
the "cpu." namespace is assumed for backwards-compatibility.

Possible values:

* An empty list will disable the feature(Default).
* An example value that would enable both the CPU and NUMA memory
  bandwidth monitors that used the virt driver variant:
  ["cpu.virt_driver", "numa_mem_bw.virt_driver"]
treserved_host_disk_mbtminis”

Amount of disk resources in MB to make them always available to host. The
disk usage gets reported back to the scheduler from nova-compute running
on the compute nodes. To prevent the disk resources from being considered
as available, this option can be used to reserve disk space for that host.

Possible values:

  * Any positive integer representing amount of disk in MB to reserve
    for the host.
treserved_host_memory_mbis¹

Amount of memory in MB to reserve for the host so that it is always available
to host processes. The host resources usage is reported back to the scheduler
continuously from nova-compute running on the compute node. To prevent the host
memory from being considered as available, this option is used to reserve
memory for the host.

Possible values:

  * Any positive integer representing amount of memory in MB to reserve
    for the host.
tcompute_stats_classsnova.compute.stats.Statss?

Abstracts out managing compute host stats to pluggable class. This class
manages and updates stats for the local compute host after an instance
is changed. These configurable compute stats may be useful for a
particular scheduler implementation.

Possible values

  * A string representing fully qualified class name.
tcpu_allocation_ratiogs!
This option helps you specify virtual CPU to physical CPU allocation
ratio which affects all CPU filters.

This configuration specifies ratio for CoreFilter which can be set
per compute node. For AggregateCoreFilter, it will fall back to this
configuration value if no per-aggregate setting is found.

Possible values:

    * Any valid positive integer or float value
    * Default value is 0.0

NOTE: This can be set per-compute, or if set to 0.0, the value
set on the scheduler node(s) or compute node(s) will be used
and defaulted to 16.0'.
tram_allocation_ratios
This option helps you specify virtual RAM to physical RAM
allocation ratio which affects all RAM filters.

This configuration specifies ratio for RamFilter which can be set
per compute node. For AggregateRamFilter, it will fall back to this
configuration value if no per-aggregate setting found.

Possible values:

    * Any valid positive integer or float value
    * Default value is 0.0

NOTE: This can be set per-compute, or if set to 0.0, the value
set on the scheduler node(s) or compute node(s) will be used and
defaulted to 1.5.
tdisk_allocation_ratios"
This option helps you specify virtual disk to physical disk
allocation ratio used by the disk_filter.py script to determine if
a host has sufficient disk space to fit a requested instance.

A ratio greater than 1.0 will result in over-subscription of the
available physical disk, which can be useful for more
efficiently packing instances created with images that do not
use the entire virtual disk, such as sparse or compressed
images. It can be set to a value between 0.0 and 1.0 in order
to preserve a percentage of the disk for uses other than
instances.

Possible values:

    * Any valid positive integer or float value
    * Default value is 0.0

NOTE: This can be set per-compute, or if set to 0.0, the value
set on the scheduler node(s) or compute node(s) will be used and
defaulted to 1.0'.
tconsole_hosttsample_defaultssocket.gethostname()sÐ
Console proxy host to be used to connect to instances on this host. It is the
publicly visible name for the console host.

Possible values:

* Current hostname (default) or any string representing hostname.
tdefault_access_ip_network_namesØ
Name of the network to be used to set access IPs for instances. If there are
multiple IPs to choose from, an arbitrary one will be chosen.

Possible values:

* None (default)
* Any string representing network name.
tdefer_iptables_applysy
Whether to batch up the application of IPTables rules during a host restart
and apply all at the end of the init phase.
tinstances_patht	instancess$state_path/instancessM

Specifies where instances are stored on the hypervisor's disk.
It can point to locally attached storage or a directory on NFS.

Possible values:

* $state_path/instances where state_path is a config option that specifies
  the top-level directory for maintaining nova's state. (default) or
  Any string representing directory path.
tinstance_usage_auditsÊ
This option enables periodic compute.instance.exists notifications. Each
compute node must be configured to generate system usage data. These
notifications are consumed by OpenStack Telemetry service.
tlive_migration_retry_countis2

Maximum number of 1 second retries in live_migration. It specifies number
of retries to iptables when it complains. It happens when an user continously
sends live-migration request to same host leading to concurrent request
to iptables.

Possible values:

* Any positive integer representing retry count.
t resume_guests_state_on_host_bootsØ
This option specifies whether to start guests that were running before the
host rebooted. It ensures that all of the instances on a Nova compute node
resume their state each time the compute node boots or restarts.
tnetwork_allocate_retriessÌ
Number of times to retry network allocation. It is required to attempt network
allocation retries if the virtual interface plug fails.

Possible values:

* Any positive integer representing retry count.
tmax_concurrent_buildsi
sž

Limits the maximum number of instance builds to run concurrently by
nova-compute. Compute service can attempt to build an infinite number of
instances, if asked to do so. This limit is enforced to avoid building
unlimited instance concurrently on a compute node. This value can be set
per compute node.

Possible Values:

* 0 : treated as unlimited.
* Any positive integer representing maximum concurrent builds.
tmax_concurrent_live_migrationsi
sË

Maximum number of live migrations to run concurrently. This limit is enforced
to avoid outbound live migrations overwhelming the host/network and causing
failures. It is not recommended that you change this unless you are very sure
that doing so is safe and stable in your environment.

Possible values:

* 0 : treated as unlimited.
* Negative value defaults to 0.
* Any positive integer representing maximum number of live migrations
  to run concurrently.
tblock_device_allocate_retriesi<sœ

Number of times to retry block device allocation on failures. Starting with
Liberty, Cinder can use image volume cache. This may help with block device
allocation performance. Look at the cinder image_volume_cache_enabled
configuration option.

Possible values:

* 60 (default)
* If value is 0, then one attempt is made.
* Any negative value is treated as 0.
* For any value > 0, total attempts are (value + 1)
tsync_power_state_pool_sizeièsD

Number of greenthreads available for use to sync power states.

This option can be used to reduce the number of concurrent requests
made to the hypervisor or system with real instance power states
for performance reasons, for example, with Ironic.

Possible values:

* Any positive integer representing greenthreads count.
tbandwidth_poll_intervaliXs–Interval to pull network bandwidth usage info. Not supported on all hypervisors. Set to -1 to disable. Setting this to 0 will run at the default rate.tsync_power_state_intervalsŒInterval to sync power states between the database and the hypervisor. Set to -1 to disable. Setting this to 0 will run at the default rate.t!heal_instance_info_cache_intervalsDNumber of seconds between instance network information cache updatestreclaim_instance_intervalshInterval in seconds for reclaiming deleted instances. It takes effect only when value is greater than 0.tvolume_usage_poll_intervals/Interval in seconds for gathering volume usagestshelved_poll_intervalis‚Interval in seconds for polling shelved instances to offload. Set to -1 to disable.Setting this to 0 will run at the default rate.tshelved_offload_times„Time in seconds before a shelved instance is eligible for removing from a host. -1 never offload, 0 offload immediately when shelvedtinstance_delete_intervali,
s„Interval in seconds for retrying failed instance file deletes. Set to -1 to disable. Setting this to 0 will run at the default rate.t&block_device_allocate_retries_intervalsSWaiting time interval (seconds) between block device allocation retries on failurest scheduler_instance_sync_intervalixs
Waiting time interval (seconds) between sending the scheduler a list of current instance UUIDs to verify that its view of instances is in sync with nova. If the CONF option `scheduler_tracks_instance_changes` is False, changing this option will have no effect.tupdate_resources_intervals'
Interval in seconds for updating compute resources. A number less than 0 means to disable the task completely. Leaving this at the default of 0 will cause this to run at the default periodic interval. Setting it to any positive value will cause it to run at approximately that number of seconds.treboot_timeoutsà

Time interval after which an instance is hard rebooted automatically.

When doing a soft reboot, it is possible that a guest kernel is
completely hung in a way that causes the soft reboot task
to not ever finish. Setting this option to a time period in seconds
will automatically hard reboot an instance if it has been stuck
in a rebooting state longer than N seconds.

Possible values:

* 0: Disables the option (default).
* Any positive integer in seconds: Enables the option.
tinstance_build_timeoutsR

Maximum time in seconds that an instance can take to build.

If this timer expires, instance status will be changed to ERROR.
Enabling this option will make sure an instance will not be stuck
in BUILD state for a longer period.

Possible values:

* 0: Disables the option (default)
* Any positive integer in seconds: Enables the option.
trescue_timeouts¯
Interval to wait before un-rescuing an instance stuck in RESCUE.

Possible values:

* 0: Disables the option (default)
* Any positive integer in seconds: Enables the option.
tresize_confirm_windows[
Automatically confirm resizes after N seconds.

Resize functionality will save the existing server before resizing.
After the resize completes, user is requested to confirm the resize.
The user has the opportunity to either confirm or revert all
changes. Confirm resize removes the original server and changes
server status from resized to active. Setting this option to a time
period (in seconds) will automatically confirm the resize if the
server is in resized state longer than that time.

Possible values:

* 0: Disables the option (default)
* Any positive integer in seconds: Enables the option.
tshutdown_timeoutsª
Total time to wait in seconds for an instance toperform a clean
shutdown.

It determines the overall period (in seconds) a VM is allowed to
perform a clean shutdown. While performing stop, rescue and shelve,
rebuild operations, configuring this option gives the VM a chance
to perform a controlled shutdown before the instance is powered off.
The default timeout is 60 seconds.

The timeout value can be overridden on a per image basis by means
of os_shutdown_timeout that is an image metadata setting allowing
different types of operating systems to specify how much time they
need to shut down cleanly.

Possible values:

* Any positive integer in seconds (default value is 60).
trunning_deleted_instance_actiontreaptchoicestnooptlogtshutdownsA
The compute service periodically checks for instances that have been
deleted in the database but remain running on the compute node. The
above option enables action to be taken when such instances are
identified.

Possible values:

* reap: Powers down the instances and deletes them(default)
* log: Logs warning message about deletion of the resource
* shutdown: Powers down instances and marks them as non-
  bootable which can be later used for debugging/analysis
* noop: Takes no action

Related options:

* running_deleted_instance_poll
* running_deleted_instance_timeout
t&running_deleted_instance_poll_intervalis‡

Time interval in seconds to wait between runs for the clean up action.
If set to 0, above check will be disabled. If "running_deleted_instance
_action" is set to "log" or "reap", a value greater than 0 must be set.

Possible values:

* Any positive integer in seconds enables the option.
* 0: Disables the option.
* 1800: Default value.

Related options:

* running_deleted_instance_action
t running_deleted_instance_timeoutsø
Time interval in seconds to wait for the instances that have
been marked as deleted in database to be eligible for cleanup.

Possible values:

* Any positive integer in seconds(default is 0).

Related options:

* "running_deleted_instance_action"
t maximum_instance_delete_attemptsis;The number of times to attempt to reap an instance's files.t
compute_topictcomputes¡

This is the message queue topic that the compute service 'listens' on. It is
used when the compute service is started up to configure the queue, and
whenever an RPC call to the compute service is made.

* Possible values:

    Any string, but there is almost never any reason to ever change this value
    from its default of 'compute'.

* Services that use this:

    ``nova-compute``

* Related options:

    None
t&osapi_compute_unique_server_name_scopettprojecttglobalsê
Sets the scope of the check for unique instance names.

The default doesn't check for unique names. If a scope for the name check is
set, a launch of a new instance or an update of an existing instance with a
duplicate name will result in an ''InstanceExists'' error. The uniqueness is
case-insensitive. Setting this option can increase the usability for end
users as they don't have to distinguish among instances with the same name
by their IDs.

Possible values:

* '': An empty value means that no uniqueness check is done and duplicate
  names are possible.
* "project": The instance name check is done only for instances within the
  same project.
* "global": The instance name check is done for all instances regardless of
  the project.
tenable_new_servicessZ
Enable new services on this host automatically.

When a new service (for example "nova-compute") starts up, it gets
registered in the database as an enabled service. Sometimes it can be useful
to register new services in disabled state and then enabled them at a later
point in time. This option can set this behavior for all services per host.

Possible values:

* ``True``: Each new service is enabled as soon as it registers itself.
* ``False``: Services must be enabled via a REST API call or with the CLI
  with ``nova service-enable <hostname> <binary>``, otherwise they are not
  ready to use.
tinstance_name_templates
instance-%08xs+
Template string to be used to generate instance names.

This template controls the creation of the database name of an instance. This
is *not* the display name you enter when creating an instance (via Horizon
or CLI). For a new deployment it is advisable to change the default value
(which uses the database autoincrement) to another value which makes use
of the attributes of an instance, like ``instance-%(uuid)s``. If you
already have instances in your deployment when you change this, your
deployment will break.

Possible values:

* A string which either uses the instance database ID (like the
  default)
* A string with a list of named database columns, for example ``%(id)d``
  or ``%(uuid)s`` or ``%(hostname)s``.

Related options:

* not to be confused with: ``multi_instance_display_name_template``
tsnapshot_name_templatessnapshot-%ss>This is not used anymore and will be removed in the O release.s5Template string to be used to generate snapshot namesc

Cs|jt
ƒ

dS(
N(t
register_optstALL_OPTS(
tconf((sF/home/tvault/.virtenv/lib/python2.7/site-packages/nova/conf/compute.pyRHÑs
cCsi
td
6S(NtDEFAULT(
RI(((sF/home/tvault/.virtenv/lib/python2.7/site-packages/nova/conf/compute.pyt	list_optsÕs
(snoopslogsshutdownR7(tsockettoslo_configRt	nova.confR
tBoolOpttFalsetStrOpttListOpttIntOpttMultiStrOpttTruetcompute_optstresource_tracker_optstFloatOpttallocation_ratio_optstgethostnametstate_path_deftcompute_manager_optst
interval_optsttimeout_optstrunning_deleted_optstinstance_cleaning_optstrpcapi_optstdb_optsRIRHRL(((sF/home/tvault/.virtenv/lib/python2.7/site-packages/nova/conf/compute.pyt<module>sb





	
























	


















































	





























#