ó
±EYc)@sˆdd
lZddl
mZ
ddlmZ
dZdZdZejddd	d
dƒ
Z	ej
dd
d
ƒ

ej
dd
dƒ

ej
dd
dƒ

ej
dddddàd
dƒ
ej
dddd
dƒ
ejdded
d ƒ
ejd!ded
d"ƒ
ej
d#dd$d%d$d
d&ƒ
ejd'ded(ed)d*d
d+ƒ
ej
d,d
d-ƒ

ej
d.d
d/ƒ

ejd0ded
d1ƒ
ej
d2dd3d
d4ƒ
ej
d5dd6d
d7eƒ
ej
d8ddd
d9eƒ
ej
d:dd;d
d<eƒ
ej
d=dd>d?ed
d@ƒ
ej
dAddBd?ed
dCƒ
ejdDded
dEƒ
ejdFded
dGƒ
ej
dHddád
dMƒ
ej
dNd
dOƒ

ej
dPddQd
dRƒ
ej
dSddâd
dXƒ
ej
dYd
dZƒ

ej
d[dd\d
d]ƒ
ej
d^dd_d
d`ƒ
ejdadgd
dbƒ
ej
dcd
ddƒ

ejded
dfƒ

ej
dgddhddãd
dkƒ
ej
dlddd
dmƒ
ejdndgd
doƒ
ejdpdgd
dqƒ
ej
drddsd
dtƒ
ejdudgd
dvƒ
g$Zej
dwddddäd
d|ƒ
ej
d}d
d~ƒ

ejdded
d€ƒ
ej
dddzd
d‚ƒ
ej
dƒddd
d„ƒ
ej
d…ddåd
dˆƒ
gZej
d‰ddŠd
d‹d(ed)dŒƒ
ej
dddŽd
dƒ
ejdded
d‘d(ed)d’ƒ
ej
d“ddŽd
d”d(ed)d’ƒ
gZej
d•dd–ddæd
d˜ƒ
ej
d™dd3d
dšƒ
gZejd›ded
dœƒ
g
Zejdded
džƒ
g
ZejdŸdgd
d ƒ
ejd¡ded
d¢d£d¤ƒ
gZej
d¥ddd
d¦ƒ
g
Zej
d§dejd¨ƒ
d
d©ƒ
g
Zej
dªdd«d
d¬ƒ
ej
d­d£d®d
d¯ƒ
gZej
d°dd«d
d±ƒ
ejd²ded
d³ƒ
gZej
d´d
dµƒ

ej
d¶d
d·ƒ

gZej
d¸dejd¨ƒ
d
d¹ƒ
ej
dºd
d»ƒ

gZej
d¼dejd¨ƒ
d
d½ƒ
ej
d¾d
d¿ƒ

gZej
dÀd
dÁƒ

ej
dÂddÃd
dă
gZej
dÅdejd¨ƒ
d
dƃ
ej
dÇddd
dȃ
gZ ej
dÉddÊddçd
d̃
g
Z!ej
dÍdejd¨ƒ
d
d΃
ej
dÏddÐd
dу
ej
dÒddd
dӃ
ej
dÔddÕd
dփ
ej
d×ddØd
dك
ej
dÚdd
d
dۃ
ejdÜdgd
d݃
gZ#e$ej%eeeeeeeeeeeeeeee e!e#ƒƒ
Z&dބZ'd߄Z(d
S(èiÿÿÿÿN(
tcfg(
tpathsidii
tlibvirtttitlesLibvirt Optionsthelps†
Libvirt options allows cloud administrator to configure related
libvirt hypervisor driver to be used within an OpenStack deployment.
trescue_image_idsú
The ID of the image to boot from to rescue data from a corrupted instance.

If the rescue REST API operation doesn't provide an ID of an image to
use, the image which is referenced by this ID is used. If this
option is not set, the image from the instance is used.

Possible values:

* An ID of an image or nothing. If it points to an *Amazon Machine
  Image* (AMI), consider to set the config options ``rescue_kernel_id``
  and ``rescue_ramdisk_id`` too. If nothing is set, the image of the instance
  is used.

Related options:

* ``rescue_kernel_id``: If the chosen rescue image allows the separate
  definition of its kernel disk, the value of this option is used,
  if specified. This is the case when *Amazon*'s AMI/AKI/ARI image
  format is used for the rescue image.
* ``rescue_ramdisk_id``: If the chosen rescue image allows the separate
  definition of its RAM disk, the value of this option is used if,
  specified. This is the case when *Amazon*'s AMI/AKI/ARI image
  format is used for the rescue image.
trescue_kernel_idsV
The ID of the kernel (AKI) image to use with the rescue image.

If the chosen rescue image allows the separate definition of its kernel
disk, the value of this option is used, if specified. This is the case
when *Amazon*'s AMI/AKI/ARI image format is used for the rescue image.

Possible values:

* An ID of an kernel image or nothing. If nothing is specified, the kernel
  disk from the instance is used if it was launched with one.

Related options:

* ``rescue_image_id``: If that option points to an image in *Amazon*'s
  AMI/AKI/ARI image format, it's useful to use ``rescue_kernel_id`` too.
trescue_ramdisk_idsT
The ID of the RAM disk (ARI) image to use with the rescue image.

If the chosen rescue image allows the separate definition of its RAM
disk, the value of this option is used, if specified. This is the case
when *Amazon*'s AMI/AKI/ARI image format is used for the rescue image.

Possible values:

* An ID of a RAM disk image or nothing. If nothing is specified, the RAM
  disk from the instance is used if it was launched with one.

Related options:

* ``rescue_image_id``: If that option points to an image in *Amazon*'s
  AMI/AKI/ARI image format, it's useful to use ``rescue_ramdisk_id`` too.
t	virt_typetdefaulttkvmtchoicestlxctqemutumltxent	parallelssŸ

Describes the virtualization type (or so called domain type) libvirt should
use.

The choice of this type must match the underlying virtualization strategy
you have chosen for this host.

Possible values:

* See the predefined set of case-sensitive values.

Related options:

* ``connection_uri``: depends on this
* ``disk_prefix``: depends on this
* ``cpu_mode``: depends on this
* ``cpu_model``: depends on this
tconnection_urits—

Overrides the default libvirt URI of the chosen virtualization type.

If set, Nova will use this URI to connect to libvirt.

Possible values:

* An URI like ``qemu:///system`` or ``xen+ssh://oirase/`` for example.
  This is only necessary if the URI differs to the commonly known URIs
  for the chosen virtualization type.

Related options:

* ``virt_type``: Influences what is used as default value here.
tinject_passwords
Allow the injection of an admin password for instance only at ``create`` and
``rebuild`` process.

There is no agent needed within the image to do this. If *libguestfs* is
available on the host, it will be used. Otherwise *nbd* is used. The file
system of the image will be mounted and the admin password, which is provided
in the REST API call will be injected as password for the root user. If no
root user is available, the instance won't be launched and an error is thrown.
Be aware that the injection is *not* possible when the instance gets launched
from a volume.

Possible values:

* True: Allows the injection.
* False (default): Disallows the injection. Any via the REST API provided
admin password will be silently ignored.

Related options:

* ``inject_partition``: That option will decide about the discovery and usage
  of the file system. It also can disable the injection at all.
t
inject_keys^
Allow the injection of an SSH key at boot time.

There is no agent needed within the image to do this. If *libguestfs* is
available on the host, it will be used. Otherwise *nbd* is used. The file
system of the image will be mounted and the SSH key, which is provided
in the REST API call will be injected as SSH key for the root user and
appended to the ``authorized_keys`` of that user. The SELinux context will
be set if necessary. Be aware that the injection is *not* possible when the
instance gets launched from a volume.

This config option will enable directly modifying the instance disk and does
not affect what cloud-init may do using data from config_drive option or the
metadata service.

Related options:

* ``inject_partition``: That option will decide about the discovery and usage
  of the file system. It also can disable the injection at all.
tinject_partitioniþÿÿÿtminsÎ
Determines the way how the file system is chosen to inject data into it.

*libguestfs* will be used a first solution to inject data. If that's not
available on the host, the image will be locally mounted on the host as a
fallback solution. If libguestfs is not able to determine the root partition
(because there are more or less than one root partition) or cannot mount the
file system it will result in an error and the instance won't be boot.

Possible values:

* -2 => disable the injection of data.
* -1 => find the root partition with the file system to mount with libguestfs
*  0 => The image is not partitioned
* >0 => The number of the partition to use for the injection

Related options:

* ``inject_key``: If this option allows the injection of a SSH key it depends
  on value greater or equal to -1 for ``inject_partition``.
* ``inject_password``: If this option allows the injection of an admin password
  it depends on value greater or equal to -1 for ``inject_partition``.
* ``guestfs`` You can enable the debug log level of libguestfs with this
  config option. A more verbose output will help in debugging issues.
* ``virt_type``: If you use ``lxc`` as virt_type it will be treated as a
  single partition image
tuse_usb_tablettdeprecated_for_removaltdeprecated_reasons<This option is being replaced by the 'pointer_model' option.s
Enable a mouse cursor within a graphical VNC or SPICE sessions.

This will only be taken into account if the VM is fully virtualized and VNC
and/or SPICE is enabled. If the node doesn't support a graphical framebuffer,
then it is valid to set this to False.

Related options:
* ``[vnc]enabled``: If VNC is enabled, ``use_usb_tablet`` will have an effect.
* ``[spice]enabled`` + ``[spice].agent_enabled``: If SPICE is enabled and the
  spice agent is disabled, the config value of ``use_usb_tablet`` will have
  an effect.
tlive_migration_inbound_addrsšLive migration target ip or hostname (if this option is set to None, which is the default, the hostname of the migration target compute node will be used)tlive_migration_uris›Override the default libvirt live migration target URI (which is dependent on virt_type) (any included "%s" is replaced with the migration target hostname)tlive_migration_tunnelleds­
Whether to use tunnelled migration, where migration data is transported over the libvirtd connection. If True, we use the VIR_MIGRATE_TUNNELLED migration flag, avoiding the need to configure the network to allow direct hypervisor to hypervisor communication. If False, use the native transport. If not set, Nova will choose a sensible default based on, for example the availability of native encryption support in the hypervisor.tlive_migration_bandwidthis
Maximum bandwidth(in MiB/s) to be used during migration. If set to 0, will choose a suitable default. Some hypervisors do not support this feature and will return an error if bandwidth is not 0. Please refer to the libvirt documentation for further detailstlive_migration_downtimeiô
s¨Maximum permitted downtime, in milliseconds, for live migration switchover. Will be rounded up to a minimum of %dms. Use a large value if guest liveness is unimportant.tlive_migration_downtime_stepssdNumber of incremental steps to reach max downtime value. Will be rounded up to a minimum of %d stepstlive_migration_downtime_delayiKsÖTime to wait, in seconds, between each step increase of the migration downtime. Minimum delay is %d seconds. Value is per GiB of guest RAM + disk to be transferred, with lower bound of a minimum of 2 GiB per devicet!live_migration_completion_timeouti tmutables.
Time to wait, in seconds, for migration to successfully complete transferring data before aborting the operation. Value is per GiB of guest RAM + disk to be transferred, with lower bound of a minimum of 2 GiB. Should usually be larger than downtime delay * downtime steps. Set to 0 to disable timeouts.tlive_migration_progress_timeouti–s’Time to wait, in seconds, for migration to make forward progress in transferring data before aborting the operation. Set to 0 to disable timeouts.tlive_migration_permit_post_copys½
This option allows nova to switch an on-going live migration to post-copy
mode, i.e., switch the active VM to the one on the destination node before the
migration is complete, therefore ensuring an upper bound on the memory that
needs to be transferred. Post-copy requires libvirt>=1.3.3 and QEMU>=2.5.0.

When permitted, post-copy mode will be automatically activated if a
live-migration memory copy iteration does not make percentage increase of at
least 10% over the last iteration.

The live-migration force complete API also uses post-copy when permitted. If
post-copy mode is not available, force complete falls back to pausing the VM
to ensure the live-migration operation will complete.

When using post-copy mode, if the source and destination hosts loose network
connectivity, the VM being live-migrated will need to be rebooted. For more
details, please see the Administration guide.

Related options:

    * live_migration_permit_auto_converge
t#live_migration_permit_auto_converges±

This option allows nova to start live migration with auto converge on.
Auto converge throttles down CPU if a progress of on-going live migration
is slow. Auto converge will only be used if this flag is set to True and
post copy is not permitted or post copy is unavailable due to the version
of libvirt and QEMU in use. Auto converge requires libvirt>=1.2.3 and
QEMU>=1.6.0.

Related options:

    * live_migration_permit_post_copy
tsnapshot_image_formattrawtqcow2tvmdktvdis7Snapshot image format. Defaults to same as source imagetdisk_prefixs

Override the default disk prefix for the devices attached to an instance.

If set, this is used to identify a free disk device name for a bus.

Possible values:

* Any prefix which will result in a valid disk device name like 'sda' or 'hda'
  for example. This is only necessary if the device names differ to the
  commonly known device name prefixes for a virtualization type such as: sd,
  xvd, uvd, vd.

Related options:

* ``virt_type``: Influences which device type is used, which determines
  the default disk prefix.
twait_soft_reboot_secondsixs¤Number of seconds to wait for instance to shut down after soft reboot request is made. We fall back to hard reboot if instance does not shutdown within this window.tcpu_modes
host-modelshost-passthroughtcustomtnones
Is used to set the CPU mode an instance should have.

If virt_type="kvm|qemu", it will default to "host-model", otherwise it will
default to "none".

Possible values:

* ``host-model``: Clones the host CPU feature flags.
* ``host-passthrough``: Use the host CPU model exactly;
* ``custom``: Use a named CPU model;
* ``none``: Not set any CPU model.

Related options:

* ``cpu_model``: If ``custom`` is used for ``cpu_mode``, set this config
  option too, otherwise this would result in an error and the instance won't
  be launched.
t	cpu_modelsx

Set the name of the libvirt CPU model the instance should use.

Possible values:

* The names listed in /usr/share/libvirt/cpu_map.xml

Related options:

* ``cpu_mode``: Don't set this when ``cpu_mode`` is NOT set to ``custom``.
  This would result in an error and the instance won't be launched.
* ``virt_type``: Only the virtualization types ``kvm`` and ``qemu`` use this.
tsnapshots_directorys$instances_path/snapshotssYLocation where libvirt driver will store snapshots before uploading them to image servicetxen_hvmloader_paths/usr/lib/xen/boot/hvmloaders(Location where the Xen hvmloader is kepttdisk_cachemodessSSpecific cachemodes to use for different disk types e.g: file=directsync,block=nonetrng_dev_pathswA path to a device that will be used as source of entropy on the host. Permitted options are: /dev/random or /dev/hwrngthw_machine_types]
For qemu or KVM guests, set this option to specify a default machine type per host architecture. You can find a list of supported machine types in your environment by checking the output of the "virsh capabilities"command. The format of the value for this config option is host-arch=machine-type. For example: x86_64=machinetype1,armv7l=machinetype2tsysinfo_serialtautotosthardwaresaThe data source used to the populate the host "serial" UUID exposed to guest in the virtual BIOS.tmem_stats_period_secondssvA number of seconds to memory usage statistics period. Zero or negative value mean to disable memory usage statistics.tuid_mapssVList of uid targets and ranges.Syntax is guest-uid:host-uid:countMaximum of 5 allowed.tgid_mapssWList of guid targets and ranges.Syntax is guest-gid:host-gid:countMaximum of 5 allowed.trealtime_scheduler_priorityi
sƒIn a realtime host context vCPUs for guest will run in that scheduling priority. Priority depends on the host kernel (usually 1-99)tenabled_perf_eventssË
This is a performance event list which could be used as monitor. These events
will be passed to libvirt domain xml while creating a new instances.
Then event statistics data can be collected from libvirt.  The minimum
libvirt version is 2.0.0. For more information about `Performance monitoring
events`, refer https://libvirt.org/formatdomain.html#elementsPerf .

* Possible values:
    A string list.
    For example:
    ``enabled_perf_events = cmt, mbml, mbmt``

    The supported events list can be found in
    https://libvirt.org/html/libvirt-libvirt-domain.html , which
    you may need to search key words ``VIR_PERF_PARAM_*``

* Services that use this:

    ``nova-compute``

* Related options:
    None

timages_typetflattlvmtrbdtploops`VM Images format. If default is specified, then use_cow_images flag is used instead of this one.timages_volume_groupsNLVM Volume Group that is used for VM images, when you specify images_type=lvm.tsparse_logical_volumessMCreate sparse logical volumes (with virtualsize) if this flag is set to True.timages_rbd_pools.The RADOS pool in which rbd volumes are storedtimages_rbd_ceph_confs*Path to the ceph configuration file to usethw_disk_discardtignoretunmapseDiscard option for nova managed disks. Need Libvirt(1.0.6) Qemu1.5 (raw format) Qemu1.6(qcow2 format)timage_info_filename_patterns=$instances_path/$image_cache_subdirectory_name/%(image)s.infosEAllows image information files to be stored in non-standard locationss6Image info files are no longer used by the image cachet)remove_unused_resized_minimum_age_secondsis@Unused resized base images younger than this will not be removedtchecksum_base_imagess+Write a checksum for files in _base to disksThe image cache no longer periodically calculates checksums of stored images. Data integrity can be checked at the block or filesystem level.tchecksum_interval_secondss&How frequently to checksum base imagestvolume_cleartzerotshreds Method used to wipe old volumes.tvolume_clear_sizes5Size in MiB to wipe at start of old volumes. 0 => alltsnapshot_compressionsZCompress snapshot images when possible. This currently applies exclusively to qcow2 imagestuse_virtio_for_bridgess.Use virtio for bridge interfaces with KVM/QEMUtqemu_allowed_storage_driversscProtocols listed here will be accessed directly from QEMU. Currently supported protocols: [gluster]tvolume_use_multipaths2Use multipath connection of the iSCSI or FC volumetdeprecated_nametiscsi_use_multipathtnum_aoe_discover_triess7Number of times to rediscover AoE target to find volumetglusterfs_mount_point_basetmntsCDirectory where the glusterfs volume is mounted on the compute nodetnum_iscsi_scan_triesis5Number of times to rescan iSCSI target to find volumetiscsi_ifacetiscsi_transports®
The iSCSI transport iface to use to connect to target in case offload support is desired. Default format is of the form <transport_name>.<hwaddress> where <transport_name> is one of (be2iscsi, bnx2i, cxgb3i, cxgb4i, qla4xxx, ocs) and <hwaddress> is the MAC address of the interface and can be generated via the iscsiadm -m iface command. Do not confuse the iscsi_iface parameter to be provided here with the actual transport name.tnum_iser_scan_triess4Number of times to rescan iSER target to find volumetiser_use_multipaths+Use multipath connection of the iSER volumetrbd_users/The RADOS client name for accessing rbd volumestrbd_secret_uuids6The libvirt UUID of the secret for the rbd_uservolumestnfs_mount_point_bases=Directory where the NFS volume is mounted on the compute nodetnfs_mount_optionssSMount options passed to the NFS client. See section of the nfs man page for detailstquobyte_mount_point_basesADirectory where the Quobyte volume is mounted on the compute nodetquobyte_client_cfgs,Path to a Quobyte Client configuration file.tscality_sofs_configs.Path or URL to Scality SOFS configuration filetscality_sofs_mount_points$state_path/scalitys,Base dir where Scality SOFS shall be mountedtsmbfs_mount_point_bases@Directory where the SMBFS shares are mounted on the compute nodetsmbfs_mount_optionssˆMount options passed to the SMBFS client. See mount.cifs man page for details. Note that the libvirt-qemu uid and gid must be specified.tremote_filesystem_transporttsshtrsyncsTUse ssh or rsync transport for creating, copying, removing files on the remote host.tvzstorage_mount_point_bases

Directory where the Virtuozzo Storage clusters are mounted on the compute node.

This option defines non-standard mountpoint for Vzstorage cluster.

* Services that use this:

    ``nova-compute``

* Related options:

    vzstorage_mount_* group of parameters
tvzstorage_mount_usertstacksÍ
Mount owner user name.

This option defines the owner user of Vzstorage cluster mountpoint.

* Services that use this:

    ``nova-compute``

* Related options:

    vzstorage_mount_* group of parameters
tvzstorage_mount_groupsÏ
Mount owner group name.

This option defines the owner group of Vzstorage cluster mountpoint.

* Services that use this:

    ``nova-compute``

* Related options:

    vzstorage_mount_* group of parameters
tvzstorage_mount_permst0770sp

Mount access mode.

This option defines the access bits of Vzstorage cluster mountpoint,
in the format similar to one of chmod(1) utility, like this: 0770.
It consists of one to four digits ranging from 0 to 7, with missing
lead digits assumed to be 0's.

* Services that use this:

    ``nova-compute``

* Related options:

    vzstorage_mount_* group of parameters
tvzstorage_log_paths./var/log/pstorage/%(cluster_name)s/nova.log.gzs2

Path to vzstorage client log.

This option defines the log of cluster operations,
it should include "%(cluster_name)s" template to separate
logs from multiple shares.

* Services that use this:

    ``nova-compute``

* Related options:

    vzstorage_mount_opts may include more detailed logging options.
tvzstorage_cache_pathsz
Path to the SSD cache file.

You can attach an SSD drive to a client and configure the drive to store
a local cache of frequently accessed data. By having a local cache on a
client's SSD drive, you can increase the overall cluster performance by
up to 10 and more times.
WARNING! There is a lot of SSD models which are not server grade and
may loose arbitrary set of data changes on power loss.
Such SSDs should not be used in Vstorage and are dangerous as may lead
to data corruptions and inconsistencies. Please consult with the manual
on which SSD models are known to be safe or verify it using
vstorage-hwflush-check(1) utility.

This option defines the path which should include "%(cluster_name)s"
template to separate caches from multiple shares.

* Services that use this:

    ``nova-compute``

* Related options:

    vzstorage_mount_opts may include more detailed cache options.
tvzstorage_mount_optss¢

Extra mount options for pstorage-mount

For full description of them, see
https://static.openvz.org/vz-man/man1/pstorage-mount.1.gz.html
Format is a python string representation of arguments list, like:
"['-v', '-R', '500']"
Shouldn't include -c, -l, -C, -u, -g and -m as those have
explicit vzstorage_* options.

* Services that use this:

    ``nova-compute``

* Related options:

    All other vzstorage_* options
c

Cs$|jt
ƒ

|jtd
t
ƒ


dS(Ntgroup(tregister_groupt
libvirt_groupt
register_optstALL_OPTS(
tconf((sF/home/tvault/.virtenv/lib/python2.7/site-packages/nova/conf/libvirt.pyRz6s


cCsi
tt
6S(
N(R{Ry(((sF/home/tvault/.virtenv/lib/python2.7/site-packages/nova/conf/libvirt.pyt	list_opts;s
(R
slxcR
sumlRR(srawR(R)R*(s
host-modelshost-passthroughR.snone(snonesosR9R7(srawR@R(RARBRCR	(signoresunmap(snoneszeroRQ(ssshsrsync()t	itertoolstoslo_configRt	nova.confR
tLIVE_MIGRATION_DOWNTIME_MINt!LIVE_MIGRATION_DOWNTIME_STEPS_MINt!LIVE_MIGRATION_DOWNTIME_DELAY_MINtOptGroupRytStrOpttBoolOpttFalsetIntOpttTruetListOpttlibvirt_general_optstlibvirt_imagebackend_optstlibvirt_imagecache_optstlibvirt_lvm_optstlibvirt_utils_optstlibvirt_vif_optstlibvirt_volume_optstlibvirt_volume_aoe_optststate_path_deftlibvirt_volume_glusterfs_optstlibvirt_volume_iscsi_optstlibvirt_volume_iser_optstlibvirt_volume_net_optstlibvirt_volume_nfs_optstlibvirt_volume_quobyte_optstlibvirt_volume_scality_optstlibvirt_volume_smbfs_optstlibvirt_remotefs_optstNonetlibvirt_volume_vzstorage_optstlisttchainR{RzR}(((sF/home/tvault/.virtenv/lib/python2.7/site-packages/nova/conf/libvirt.pyt<module>s