diff --git a/etc/glance-api.conf b/etc/glance-api.conf index 04cc54699a..66ecdffd80 100644 --- a/etc/glance-api.conf +++ b/etc/glance-api.conf @@ -1930,523 +1930,6 @@ # Minimum value: 0 #store_capabilities_update_min_interval = 0 -# -# Directory to which the filesystem backend store writes images. -# -# Upon start up, Glance creates the directory if it doesn't already -# exist and verifies write access to the user under which -# ``glance-api`` runs. If the write access isn't available, a -# ``BadStoreConfiguration`` exception is raised and the filesystem -# store may not be available for adding new images. -# -# NOTE: This directory is used only when filesystem store is used as a -# storage backend. Either ``filesystem_store_datadir`` or -# ``filesystem_store_datadirs`` option must be specified in -# ``glance-api.conf``. If both options are specified, a -# ``BadStoreConfiguration`` will be raised and the filesystem store -# may not be available for adding new images. -# -# Possible values: -# * A valid path to a directory -# -# Related options: -# * ``filesystem_store_datadirs`` -# * ``filesystem_store_file_perm`` -# -# (string value) -#filesystem_store_datadir = /var/lib/glance/images - -# -# List of directories and their priorities to which the filesystem -# backend store writes images. -# -# The filesystem store can be configured to store images in multiple -# directories as opposed to using a single directory specified by the -# ``filesystem_store_datadir`` configuration option. When using -# multiple directories, each directory can be given an optional -# priority to specify the preference order in which they should -# be used. Priority is an integer that is concatenated to the -# directory path with a colon where a higher value indicates higher -# priority. When two directories have the same priority, the directory -# with most free space is used. When no priority is specified, it -# defaults to zero. -# -# More information on configuring filesystem store with multiple store -# directories can be found at -# http://docs.openstack.org/developer/glance/configuring.html -# -# NOTE: This directory is used only when filesystem store is used as a -# storage backend. Either ``filesystem_store_datadir`` or -# ``filesystem_store_datadirs`` option must be specified in -# ``glance-api.conf``. If both options are specified, a -# ``BadStoreConfiguration`` will be raised and the filesystem store -# may not be available for adding new images. -# -# Possible values: -# * List of strings of the following form: -# * ``:`` -# -# Related options: -# * ``filesystem_store_datadir`` -# * ``filesystem_store_file_perm`` -# -# (multi valued) -#filesystem_store_datadirs = - -# -# Filesystem store metadata file. -# -# The path to a file which contains the metadata to be returned with -# any location associated with the filesystem store. The file must -# contain a valid JSON object. The object should contain the keys -# ``id`` and ``mountpoint``. The value for both keys should be a -# string. -# -# Possible values: -# * A valid path to the store metadata file -# -# Related options: -# * None -# -# (string value) -#filesystem_store_metadata_file = - -# -# File access permissions for the image files. -# -# Set the intended file access permissions for image data. This provides -# a way to enable other services, e.g. Nova, to consume images directly -# from the filesystem store. The users running the services that are -# intended to be given access to could be made a member of the group -# that owns the files created. Assigning a value less then or equal to -# zero for this configuration option signifies that no changes be made -# to the default permissions. This value will be decoded as an octal -# digit. -# -# For more information, please refer the documentation at -# http://docs.openstack.org/developer/glance/configuring.html -# -# Possible values: -# * A valid file access permission -# * Zero -# * Any negative integer -# -# Related options: -# * None -# -# (integer value) -#filesystem_store_file_perm = 0 - -# -# Path to the CA bundle file. -# -# This configuration option enables the operator to use a custom -# Certificate Authority file to verify the remote server certificate. If -# this option is set, the ``https_insecure`` option will be ignored and -# the CA file specified will be used to authenticate the server -# certificate and establish a secure connection to the server. -# -# Possible values: -# * A valid path to a CA file -# -# Related options: -# * https_insecure -# -# (string value) -#https_ca_certificates_file = - -# -# Set verification of the remote server certificate. -# -# This configuration option takes in a boolean value to determine -# whether or not to verify the remote server certificate. If set to -# True, the remote server certificate is not verified. If the option is -# set to False, then the default CA truststore is used for verification. -# -# This option is ignored if ``https_ca_certificates_file`` is set. -# The remote server certificate will then be verified using the file -# specified using the ``https_ca_certificates_file`` option. -# -# Possible values: -# * True -# * False -# -# Related options: -# * https_ca_certificates_file -# -# (boolean value) -#https_insecure = true - -# -# The http/https proxy information to be used to connect to the remote -# server. -# -# This configuration option specifies the http/https proxy information -# that should be used to connect to the remote server. The proxy -# information should be a key value pair of the scheme and proxy, for -# example, http:10.0.0.1:3128. You can also specify proxies for multiple -# schemes by separating the key value pairs with a comma, for example, -# http:10.0.0.1:3128, https:10.0.0.1:1080. -# -# Possible values: -# * A comma separated list of scheme:proxy pairs as described above -# -# Related options: -# * None -# -# (dict value) -#http_proxy_information = - -# -# Address of the ESX/ESXi or vCenter Server target system. -# -# This configuration option sets the address of the ESX/ESXi or vCenter -# Server target system. This option is required when using the VMware -# storage backend. The address can contain an IP address (127.0.0.1) or -# a DNS name (www.my-domain.com). -# -# Possible Values: -# * A valid IPv4 or IPv6 address -# * A valid DNS name -# -# Related options: -# * vmware_server_username -# * vmware_server_password -# -# (string value) -#vmware_server_host = 127.0.0.1 - -# -# Server username. -# -# This configuration option takes the username for authenticating with -# the VMware ESX/ESXi or vCenter Server. This option is required when -# using the VMware storage backend. -# -# Possible Values: -# * Any string that is the username for a user with appropriate -# privileges -# -# Related options: -# * vmware_server_host -# * vmware_server_password -# -# (string value) -#vmware_server_username = root - -# -# Server password. -# -# This configuration option takes the password for authenticating with -# the VMware ESX/ESXi or vCenter Server. This option is required when -# using the VMware storage backend. -# -# Possible Values: -# * Any string that is a password corresponding to the username -# specified using the "vmware_server_username" option -# -# Related options: -# * vmware_server_host -# * vmware_server_username -# -# (string value) -#vmware_server_password = vmware - -# -# The number of VMware API retries. -# -# This configuration option specifies the number of times the VMware -# ESX/VC server API must be retried upon connection related issues or -# server API call overload. It is not possible to specify 'retry -# forever'. -# -# Possible Values: -# * Any positive integer value -# -# Related options: -# * None -# -# (integer value) -# Minimum value: 1 -#vmware_api_retry_count = 10 - -# -# Interval in seconds used for polling remote tasks invoked on VMware -# ESX/VC server. -# -# This configuration option takes in the sleep time in seconds for polling an -# on-going async task as part of the VMWare ESX/VC server API call. -# -# Possible Values: -# * Any positive integer value -# -# Related options: -# * None -# -# (integer value) -# Minimum value: 1 -#vmware_task_poll_interval = 5 - -# -# The directory where the glance images will be stored in the datastore. -# -# This configuration option specifies the path to the directory where the -# glance images will be stored in the VMware datastore. If this option -# is not set, the default directory where the glance images are stored -# is openstack_glance. -# -# Possible Values: -# * Any string that is a valid path to a directory -# -# Related options: -# * None -# -# (string value) -#vmware_store_image_dir = /openstack_glance - -# -# Set verification of the ESX/vCenter server certificate. -# -# This configuration option takes a boolean value to determine -# whether or not to verify the ESX/vCenter server certificate. If this -# option is set to True, the ESX/vCenter server certificate is not -# verified. If this option is set to False, then the default CA -# truststore is used for verification. -# -# This option is ignored if the "vmware_ca_file" option is set. In that -# case, the ESX/vCenter server certificate will then be verified using -# the file specified using the "vmware_ca_file" option . -# -# Possible Values: -# * True -# * False -# -# Related options: -# * vmware_ca_file -# -# (boolean value) -# Deprecated group/name - [glance_store]/vmware_api_insecure -#vmware_insecure = false - -# -# Absolute path to the CA bundle file. -# -# This configuration option enables the operator to use a custom -# Cerificate Authority File to verify the ESX/vCenter certificate. -# -# If this option is set, the "vmware_insecure" option will be ignored -# and the CA file specified will be used to authenticate the ESX/vCenter -# server certificate and establish a secure connection to the server. -# -# Possible Values: -# * Any string that is a valid absolute path to a CA file -# -# Related options: -# * vmware_insecure -# -# (string value) -#vmware_ca_file = /etc/ssl/certs/ca-certificates.crt - -# -# The datastores where the image can be stored. -# -# This configuration option specifies the datastores where the image can -# be stored in the VMWare store backend. This option may be specified -# multiple times for specifying multiple datastores. The datastore name -# should be specified after its datacenter path, separated by ":". An -# optional weight may be given after the datastore name, separated again -# by ":" to specify the priority. Thus, the required format becomes -# ::. -# -# When adding an image, the datastore with highest weight will be -# selected, unless there is not enough free space available in cases -# where the image size is already known. If no weight is given, it is -# assumed to be zero and the directory will be considered for selection -# last. If multiple datastores have the same weight, then the one with -# the most free space available is selected. -# -# Possible Values: -# * Any string of the format: -# :: -# -# Related options: -# * None -# -# (multi valued) -#vmware_datastores = - -# -# Chunk size for images to be stored in Sheepdog data store. -# -# Provide an integer value representing the size in mebibyte -# (1048576 bytes) to chunk Glance images into. The default -# chunk size is 64 mebibytes. -# -# When using Sheepdog distributed storage system, the images are -# chunked into objects of this size and then stored across the -# distributed data store to use for Glance. -# -# Chunk sizes, if a power of two, help avoid fragmentation and -# enable improved performance. -# -# Possible values: -# * Positive integer value representing size in mebibytes. -# -# Related Options: -# * None -# -# (integer value) -# Minimum value: 1 -#sheepdog_store_chunk_size = 64 - -# -# Port number on which the sheep daemon will listen. -# -# Provide an integer value representing a valid port number on -# which you want the Sheepdog daemon to listen on. The default -# port is 7000. -# -# The Sheepdog daemon, also called 'sheep', manages the storage -# in the distributed cluster by writing objects across the storage -# network. It identifies and acts on the messages it receives on -# the port number set using ``sheepdog_store_port`` option to store -# chunks of Glance images. -# -# Possible values: -# * A valid port number (0 to 65535) -# -# Related Options: -# * sheepdog_store_address -# -# (port value) -# Minimum value: 0 -# Maximum value: 65535 -#sheepdog_store_port = 7000 - -# -# Address to bind the Sheepdog daemon to. -# -# Provide a string value representing the address to bind the -# Sheepdog daemon to. The default address set for the 'sheep' -# is 127.0.0.1. -# -# The Sheepdog daemon, also called 'sheep', manages the storage -# in the distributed cluster by writing objects across the storage -# network. It identifies and acts on the messages directed to the -# address set using ``sheepdog_store_address`` option to store -# chunks of Glance images. -# -# Possible values: -# * A valid IPv4 address -# * A valid IPv6 address -# * A valid hostname -# -# Related Options: -# * sheepdog_store_port -# -# (string value) -#sheepdog_store_address = 127.0.0.1 - -# -# Size, in megabytes, to chunk RADOS images into. -# -# Provide an integer value representing the size in megabytes to chunk -# Glance images into. The default chunk size is 8 megabytes. For optimal -# performance, the value should be a power of two. -# -# When Ceph's RBD object storage system is used as the storage backend -# for storing Glance images, the images are chunked into objects of the -# size set using this option. These chunked objects are then stored -# across the distributed block data store to use for Glance. -# -# Possible Values: -# * Any positive integer value -# -# Related options: -# * None -# -# (integer value) -# Minimum value: 1 -#rbd_store_chunk_size = 8 - -# -# RADOS pool in which images are stored. -# -# When RBD is used as the storage backend for storing Glance images, the -# images are stored by means of logical grouping of the objects (chunks -# of images) into a ``pool``. Each pool is defined with the number of -# placement groups it can contain. The default pool that is used is -# 'images'. -# -# More information on the RBD storage backend can be found here: -# http://ceph.com/planet/how-data-is-stored-in-ceph-cluster/ -# -# Possible Values: -# * A valid pool name -# -# Related options: -# * None -# -# (string value) -#rbd_store_pool = images - -# -# RADOS user to authenticate as. -# -# This configuration option takes in the RADOS user to authenticate as. -# This is only needed when RADOS authentication is enabled and is -# applicable only if the user is using Cephx authentication. If the -# value for this option is not set by the user or is set to None, a -# default value will be chosen, which will be based on the client. -# section in rbd_store_ceph_conf. -# -# Possible Values: -# * A valid RADOS user -# -# Related options: -# * rbd_store_ceph_conf -# -# (string value) -#rbd_store_user = - -# -# Ceph configuration file path. -# -# This configuration option takes in the path to the Ceph configuration -# file to be used. If the value for this option is not set by the user -# or is set to None, librados will locate the default configuration file -# which is located at /etc/ceph/ceph.conf. If using Cephx -# authentication, this file should include a reference to the right -# keyring in a client. section -# -# Possible Values: -# * A valid path to a configuration file -# -# Related options: -# * rbd_store_user -# -# (string value) -#rbd_store_ceph_conf = /etc/ceph/ceph.conf - -# -# Timeout value for connecting to Ceph cluster. -# -# This configuration option takes in the timeout value in seconds used -# when connecting to the Ceph cluster i.e. it sets the time to wait for -# glance-api before closing the connection. This prevents glance-api -# hangups during the connection to RBD. If the value for this option -# is set to less than or equal to 0, no timeout is set and the default -# librados value is used. -# -# Possible Values: -# * Any integer value -# -# Related options: -# * None -# -# (integer value) -#rados_connect_timeout = 0 - # # Information to match when looking for cinder in the service catalog. # @@ -2686,6 +2169,345 @@ # (string value) #rootwrap_config = /etc/glance/rootwrap.conf +# +# Directory to which the filesystem backend store writes images. +# +# Upon start up, Glance creates the directory if it doesn't already +# exist and verifies write access to the user under which +# ``glance-api`` runs. If the write access isn't available, a +# ``BadStoreConfiguration`` exception is raised and the filesystem +# store may not be available for adding new images. +# +# NOTE: This directory is used only when filesystem store is used as a +# storage backend. Either ``filesystem_store_datadir`` or +# ``filesystem_store_datadirs`` option must be specified in +# ``glance-api.conf``. If both options are specified, a +# ``BadStoreConfiguration`` will be raised and the filesystem store +# may not be available for adding new images. +# +# Possible values: +# * A valid path to a directory +# +# Related options: +# * ``filesystem_store_datadirs`` +# * ``filesystem_store_file_perm`` +# +# (string value) +#filesystem_store_datadir = /var/lib/glance/images + +# +# List of directories and their priorities to which the filesystem +# backend store writes images. +# +# The filesystem store can be configured to store images in multiple +# directories as opposed to using a single directory specified by the +# ``filesystem_store_datadir`` configuration option. When using +# multiple directories, each directory can be given an optional +# priority to specify the preference order in which they should +# be used. Priority is an integer that is concatenated to the +# directory path with a colon where a higher value indicates higher +# priority. When two directories have the same priority, the directory +# with most free space is used. When no priority is specified, it +# defaults to zero. +# +# More information on configuring filesystem store with multiple store +# directories can be found at +# http://docs.openstack.org/developer/glance/configuring.html +# +# NOTE: This directory is used only when filesystem store is used as a +# storage backend. Either ``filesystem_store_datadir`` or +# ``filesystem_store_datadirs`` option must be specified in +# ``glance-api.conf``. If both options are specified, a +# ``BadStoreConfiguration`` will be raised and the filesystem store +# may not be available for adding new images. +# +# Possible values: +# * List of strings of the following form: +# * ``:`` +# +# Related options: +# * ``filesystem_store_datadir`` +# * ``filesystem_store_file_perm`` +# +# (multi valued) +#filesystem_store_datadirs = + +# +# Filesystem store metadata file. +# +# The path to a file which contains the metadata to be returned with +# any location associated with the filesystem store. The file must +# contain a valid JSON object. The object should contain the keys +# ``id`` and ``mountpoint``. The value for both keys should be a +# string. +# +# Possible values: +# * A valid path to the store metadata file +# +# Related options: +# * None +# +# (string value) +#filesystem_store_metadata_file = + +# +# File access permissions for the image files. +# +# Set the intended file access permissions for image data. This provides +# a way to enable other services, e.g. Nova, to consume images directly +# from the filesystem store. The users running the services that are +# intended to be given access to could be made a member of the group +# that owns the files created. Assigning a value less then or equal to +# zero for this configuration option signifies that no changes be made +# to the default permissions. This value will be decoded as an octal +# digit. +# +# For more information, please refer the documentation at +# http://docs.openstack.org/developer/glance/configuring.html +# +# Possible values: +# * A valid file access permission +# * Zero +# * Any negative integer +# +# Related options: +# * None +# +# (integer value) +#filesystem_store_file_perm = 0 + +# +# Path to the CA bundle file. +# +# This configuration option enables the operator to use a custom +# Certificate Authority file to verify the remote server certificate. If +# this option is set, the ``https_insecure`` option will be ignored and +# the CA file specified will be used to authenticate the server +# certificate and establish a secure connection to the server. +# +# Possible values: +# * A valid path to a CA file +# +# Related options: +# * https_insecure +# +# (string value) +#https_ca_certificates_file = + +# +# Set verification of the remote server certificate. +# +# This configuration option takes in a boolean value to determine +# whether or not to verify the remote server certificate. If set to +# True, the remote server certificate is not verified. If the option is +# set to False, then the default CA truststore is used for verification. +# +# This option is ignored if ``https_ca_certificates_file`` is set. +# The remote server certificate will then be verified using the file +# specified using the ``https_ca_certificates_file`` option. +# +# Possible values: +# * True +# * False +# +# Related options: +# * https_ca_certificates_file +# +# (boolean value) +#https_insecure = true + +# +# The http/https proxy information to be used to connect to the remote +# server. +# +# This configuration option specifies the http/https proxy information +# that should be used to connect to the remote server. The proxy +# information should be a key value pair of the scheme and proxy, for +# example, http:10.0.0.1:3128. You can also specify proxies for multiple +# schemes by separating the key value pairs with a comma, for example, +# http:10.0.0.1:3128, https:10.0.0.1:1080. +# +# Possible values: +# * A comma separated list of scheme:proxy pairs as described above +# +# Related options: +# * None +# +# (dict value) +#http_proxy_information = + +# +# Size, in megabytes, to chunk RADOS images into. +# +# Provide an integer value representing the size in megabytes to chunk +# Glance images into. The default chunk size is 8 megabytes. For optimal +# performance, the value should be a power of two. +# +# When Ceph's RBD object storage system is used as the storage backend +# for storing Glance images, the images are chunked into objects of the +# size set using this option. These chunked objects are then stored +# across the distributed block data store to use for Glance. +# +# Possible Values: +# * Any positive integer value +# +# Related options: +# * None +# +# (integer value) +# Minimum value: 1 +#rbd_store_chunk_size = 8 + +# +# RADOS pool in which images are stored. +# +# When RBD is used as the storage backend for storing Glance images, the +# images are stored by means of logical grouping of the objects (chunks +# of images) into a ``pool``. Each pool is defined with the number of +# placement groups it can contain. The default pool that is used is +# 'images'. +# +# More information on the RBD storage backend can be found here: +# http://ceph.com/planet/how-data-is-stored-in-ceph-cluster/ +# +# Possible Values: +# * A valid pool name +# +# Related options: +# * None +# +# (string value) +#rbd_store_pool = images + +# +# RADOS user to authenticate as. +# +# This configuration option takes in the RADOS user to authenticate as. +# This is only needed when RADOS authentication is enabled and is +# applicable only if the user is using Cephx authentication. If the +# value for this option is not set by the user or is set to None, a +# default value will be chosen, which will be based on the client. +# section in rbd_store_ceph_conf. +# +# Possible Values: +# * A valid RADOS user +# +# Related options: +# * rbd_store_ceph_conf +# +# (string value) +#rbd_store_user = + +# +# Ceph configuration file path. +# +# This configuration option takes in the path to the Ceph configuration +# file to be used. If the value for this option is not set by the user +# or is set to None, librados will locate the default configuration file +# which is located at /etc/ceph/ceph.conf. If using Cephx +# authentication, this file should include a reference to the right +# keyring in a client. section +# +# Possible Values: +# * A valid path to a configuration file +# +# Related options: +# * rbd_store_user +# +# (string value) +#rbd_store_ceph_conf = /etc/ceph/ceph.conf + +# +# Timeout value for connecting to Ceph cluster. +# +# This configuration option takes in the timeout value in seconds used +# when connecting to the Ceph cluster i.e. it sets the time to wait for +# glance-api before closing the connection. This prevents glance-api +# hangups during the connection to RBD. If the value for this option +# is set to less than or equal to 0, no timeout is set and the default +# librados value is used. +# +# Possible Values: +# * Any integer value +# +# Related options: +# * None +# +# (integer value) +#rados_connect_timeout = 0 + +# +# Chunk size for images to be stored in Sheepdog data store. +# +# Provide an integer value representing the size in mebibyte +# (1048576 bytes) to chunk Glance images into. The default +# chunk size is 64 mebibytes. +# +# When using Sheepdog distributed storage system, the images are +# chunked into objects of this size and then stored across the +# distributed data store to use for Glance. +# +# Chunk sizes, if a power of two, help avoid fragmentation and +# enable improved performance. +# +# Possible values: +# * Positive integer value representing size in mebibytes. +# +# Related Options: +# * None +# +# (integer value) +# Minimum value: 1 +#sheepdog_store_chunk_size = 64 + +# +# Port number on which the sheep daemon will listen. +# +# Provide an integer value representing a valid port number on +# which you want the Sheepdog daemon to listen on. The default +# port is 7000. +# +# The Sheepdog daemon, also called 'sheep', manages the storage +# in the distributed cluster by writing objects across the storage +# network. It identifies and acts on the messages it receives on +# the port number set using ``sheepdog_store_port`` option to store +# chunks of Glance images. +# +# Possible values: +# * A valid port number (0 to 65535) +# +# Related Options: +# * sheepdog_store_address +# +# (port value) +# Minimum value: 0 +# Maximum value: 65535 +#sheepdog_store_port = 7000 + +# +# Address to bind the Sheepdog daemon to. +# +# Provide a string value representing the address to bind the +# Sheepdog daemon to. The default address set for the 'sheep' +# is 127.0.0.1. +# +# The Sheepdog daemon, also called 'sheep', manages the storage +# in the distributed cluster by writing objects across the storage +# network. It identifies and acts on the messages directed to the +# address set using ``sheepdog_store_address`` option to store +# chunks of Glance images. +# +# Possible values: +# * A valid IPv4 address +# * A valid IPv6 address +# * A valid hostname +# +# Related Options: +# * sheepdog_store_port +# +# (string value) +#sheepdog_store_address = 127.0.0.1 + # # Set verification of the server certificate. # @@ -3159,6 +2981,184 @@ # (string value) #swift_store_config_file = +# +# Address of the ESX/ESXi or vCenter Server target system. +# +# This configuration option sets the address of the ESX/ESXi or vCenter +# Server target system. This option is required when using the VMware +# storage backend. The address can contain an IP address (127.0.0.1) or +# a DNS name (www.my-domain.com). +# +# Possible Values: +# * A valid IPv4 or IPv6 address +# * A valid DNS name +# +# Related options: +# * vmware_server_username +# * vmware_server_password +# +# (string value) +#vmware_server_host = 127.0.0.1 + +# +# Server username. +# +# This configuration option takes the username for authenticating with +# the VMware ESX/ESXi or vCenter Server. This option is required when +# using the VMware storage backend. +# +# Possible Values: +# * Any string that is the username for a user with appropriate +# privileges +# +# Related options: +# * vmware_server_host +# * vmware_server_password +# +# (string value) +#vmware_server_username = root + +# +# Server password. +# +# This configuration option takes the password for authenticating with +# the VMware ESX/ESXi or vCenter Server. This option is required when +# using the VMware storage backend. +# +# Possible Values: +# * Any string that is a password corresponding to the username +# specified using the "vmware_server_username" option +# +# Related options: +# * vmware_server_host +# * vmware_server_username +# +# (string value) +#vmware_server_password = vmware + +# +# The number of VMware API retries. +# +# This configuration option specifies the number of times the VMware +# ESX/VC server API must be retried upon connection related issues or +# server API call overload. It is not possible to specify 'retry +# forever'. +# +# Possible Values: +# * Any positive integer value +# +# Related options: +# * None +# +# (integer value) +# Minimum value: 1 +#vmware_api_retry_count = 10 + +# +# Interval in seconds used for polling remote tasks invoked on VMware +# ESX/VC server. +# +# This configuration option takes in the sleep time in seconds for polling an +# on-going async task as part of the VMWare ESX/VC server API call. +# +# Possible Values: +# * Any positive integer value +# +# Related options: +# * None +# +# (integer value) +# Minimum value: 1 +#vmware_task_poll_interval = 5 + +# +# The directory where the glance images will be stored in the datastore. +# +# This configuration option specifies the path to the directory where the +# glance images will be stored in the VMware datastore. If this option +# is not set, the default directory where the glance images are stored +# is openstack_glance. +# +# Possible Values: +# * Any string that is a valid path to a directory +# +# Related options: +# * None +# +# (string value) +#vmware_store_image_dir = /openstack_glance + +# +# Set verification of the ESX/vCenter server certificate. +# +# This configuration option takes a boolean value to determine +# whether or not to verify the ESX/vCenter server certificate. If this +# option is set to True, the ESX/vCenter server certificate is not +# verified. If this option is set to False, then the default CA +# truststore is used for verification. +# +# This option is ignored if the "vmware_ca_file" option is set. In that +# case, the ESX/vCenter server certificate will then be verified using +# the file specified using the "vmware_ca_file" option . +# +# Possible Values: +# * True +# * False +# +# Related options: +# * vmware_ca_file +# +# (boolean value) +# Deprecated group/name - [glance_store]/vmware_api_insecure +#vmware_insecure = false + +# +# Absolute path to the CA bundle file. +# +# This configuration option enables the operator to use a custom +# Cerificate Authority File to verify the ESX/vCenter certificate. +# +# If this option is set, the "vmware_insecure" option will be ignored +# and the CA file specified will be used to authenticate the ESX/vCenter +# server certificate and establish a secure connection to the server. +# +# Possible Values: +# * Any string that is a valid absolute path to a CA file +# +# Related options: +# * vmware_insecure +# +# (string value) +#vmware_ca_file = /etc/ssl/certs/ca-certificates.crt + +# +# The datastores where the image can be stored. +# +# This configuration option specifies the datastores where the image can +# be stored in the VMWare store backend. This option may be specified +# multiple times for specifying multiple datastores. The datastore name +# should be specified after its datacenter path, separated by ":". An +# optional weight may be given after the datastore name, separated again +# by ":" to specify the priority. Thus, the required format becomes +# ::. +# +# When adding an image, the datastore with highest weight will be +# selected, unless there is not enough free space available in cases +# where the image size is already known. If no weight is given, it is +# assumed to be zero and the directory will be considered for selection +# last. If multiple datastores have the same weight, then the one with +# the most free space available is selected. +# +# Possible Values: +# * Any string of the format: +# :: +# +# Related options: +# * None +# +# (multi valued) +#vmware_datastores = + [image_format] diff --git a/etc/glance-cache.conf b/etc/glance-cache.conf index 035c238e5c..3923028302 100644 --- a/etc/glance-cache.conf +++ b/etc/glance-cache.conf @@ -1043,523 +1043,6 @@ # Minimum value: 0 #store_capabilities_update_min_interval = 0 -# -# Directory to which the filesystem backend store writes images. -# -# Upon start up, Glance creates the directory if it doesn't already -# exist and verifies write access to the user under which -# ``glance-api`` runs. If the write access isn't available, a -# ``BadStoreConfiguration`` exception is raised and the filesystem -# store may not be available for adding new images. -# -# NOTE: This directory is used only when filesystem store is used as a -# storage backend. Either ``filesystem_store_datadir`` or -# ``filesystem_store_datadirs`` option must be specified in -# ``glance-api.conf``. If both options are specified, a -# ``BadStoreConfiguration`` will be raised and the filesystem store -# may not be available for adding new images. -# -# Possible values: -# * A valid path to a directory -# -# Related options: -# * ``filesystem_store_datadirs`` -# * ``filesystem_store_file_perm`` -# -# (string value) -#filesystem_store_datadir = /var/lib/glance/images - -# -# List of directories and their priorities to which the filesystem -# backend store writes images. -# -# The filesystem store can be configured to store images in multiple -# directories as opposed to using a single directory specified by the -# ``filesystem_store_datadir`` configuration option. When using -# multiple directories, each directory can be given an optional -# priority to specify the preference order in which they should -# be used. Priority is an integer that is concatenated to the -# directory path with a colon where a higher value indicates higher -# priority. When two directories have the same priority, the directory -# with most free space is used. When no priority is specified, it -# defaults to zero. -# -# More information on configuring filesystem store with multiple store -# directories can be found at -# http://docs.openstack.org/developer/glance/configuring.html -# -# NOTE: This directory is used only when filesystem store is used as a -# storage backend. Either ``filesystem_store_datadir`` or -# ``filesystem_store_datadirs`` option must be specified in -# ``glance-api.conf``. If both options are specified, a -# ``BadStoreConfiguration`` will be raised and the filesystem store -# may not be available for adding new images. -# -# Possible values: -# * List of strings of the following form: -# * ``:`` -# -# Related options: -# * ``filesystem_store_datadir`` -# * ``filesystem_store_file_perm`` -# -# (multi valued) -#filesystem_store_datadirs = - -# -# Filesystem store metadata file. -# -# The path to a file which contains the metadata to be returned with -# any location associated with the filesystem store. The file must -# contain a valid JSON object. The object should contain the keys -# ``id`` and ``mountpoint``. The value for both keys should be a -# string. -# -# Possible values: -# * A valid path to the store metadata file -# -# Related options: -# * None -# -# (string value) -#filesystem_store_metadata_file = - -# -# File access permissions for the image files. -# -# Set the intended file access permissions for image data. This provides -# a way to enable other services, e.g. Nova, to consume images directly -# from the filesystem store. The users running the services that are -# intended to be given access to could be made a member of the group -# that owns the files created. Assigning a value less then or equal to -# zero for this configuration option signifies that no changes be made -# to the default permissions. This value will be decoded as an octal -# digit. -# -# For more information, please refer the documentation at -# http://docs.openstack.org/developer/glance/configuring.html -# -# Possible values: -# * A valid file access permission -# * Zero -# * Any negative integer -# -# Related options: -# * None -# -# (integer value) -#filesystem_store_file_perm = 0 - -# -# Path to the CA bundle file. -# -# This configuration option enables the operator to use a custom -# Certificate Authority file to verify the remote server certificate. If -# this option is set, the ``https_insecure`` option will be ignored and -# the CA file specified will be used to authenticate the server -# certificate and establish a secure connection to the server. -# -# Possible values: -# * A valid path to a CA file -# -# Related options: -# * https_insecure -# -# (string value) -#https_ca_certificates_file = - -# -# Set verification of the remote server certificate. -# -# This configuration option takes in a boolean value to determine -# whether or not to verify the remote server certificate. If set to -# True, the remote server certificate is not verified. If the option is -# set to False, then the default CA truststore is used for verification. -# -# This option is ignored if ``https_ca_certificates_file`` is set. -# The remote server certificate will then be verified using the file -# specified using the ``https_ca_certificates_file`` option. -# -# Possible values: -# * True -# * False -# -# Related options: -# * https_ca_certificates_file -# -# (boolean value) -#https_insecure = true - -# -# The http/https proxy information to be used to connect to the remote -# server. -# -# This configuration option specifies the http/https proxy information -# that should be used to connect to the remote server. The proxy -# information should be a key value pair of the scheme and proxy, for -# example, http:10.0.0.1:3128. You can also specify proxies for multiple -# schemes by separating the key value pairs with a comma, for example, -# http:10.0.0.1:3128, https:10.0.0.1:1080. -# -# Possible values: -# * A comma separated list of scheme:proxy pairs as described above -# -# Related options: -# * None -# -# (dict value) -#http_proxy_information = - -# -# Address of the ESX/ESXi or vCenter Server target system. -# -# This configuration option sets the address of the ESX/ESXi or vCenter -# Server target system. This option is required when using the VMware -# storage backend. The address can contain an IP address (127.0.0.1) or -# a DNS name (www.my-domain.com). -# -# Possible Values: -# * A valid IPv4 or IPv6 address -# * A valid DNS name -# -# Related options: -# * vmware_server_username -# * vmware_server_password -# -# (string value) -#vmware_server_host = 127.0.0.1 - -# -# Server username. -# -# This configuration option takes the username for authenticating with -# the VMware ESX/ESXi or vCenter Server. This option is required when -# using the VMware storage backend. -# -# Possible Values: -# * Any string that is the username for a user with appropriate -# privileges -# -# Related options: -# * vmware_server_host -# * vmware_server_password -# -# (string value) -#vmware_server_username = root - -# -# Server password. -# -# This configuration option takes the password for authenticating with -# the VMware ESX/ESXi or vCenter Server. This option is required when -# using the VMware storage backend. -# -# Possible Values: -# * Any string that is a password corresponding to the username -# specified using the "vmware_server_username" option -# -# Related options: -# * vmware_server_host -# * vmware_server_username -# -# (string value) -#vmware_server_password = vmware - -# -# The number of VMware API retries. -# -# This configuration option specifies the number of times the VMware -# ESX/VC server API must be retried upon connection related issues or -# server API call overload. It is not possible to specify 'retry -# forever'. -# -# Possible Values: -# * Any positive integer value -# -# Related options: -# * None -# -# (integer value) -# Minimum value: 1 -#vmware_api_retry_count = 10 - -# -# Interval in seconds used for polling remote tasks invoked on VMware -# ESX/VC server. -# -# This configuration option takes in the sleep time in seconds for polling an -# on-going async task as part of the VMWare ESX/VC server API call. -# -# Possible Values: -# * Any positive integer value -# -# Related options: -# * None -# -# (integer value) -# Minimum value: 1 -#vmware_task_poll_interval = 5 - -# -# The directory where the glance images will be stored in the datastore. -# -# This configuration option specifies the path to the directory where the -# glance images will be stored in the VMware datastore. If this option -# is not set, the default directory where the glance images are stored -# is openstack_glance. -# -# Possible Values: -# * Any string that is a valid path to a directory -# -# Related options: -# * None -# -# (string value) -#vmware_store_image_dir = /openstack_glance - -# -# Set verification of the ESX/vCenter server certificate. -# -# This configuration option takes a boolean value to determine -# whether or not to verify the ESX/vCenter server certificate. If this -# option is set to True, the ESX/vCenter server certificate is not -# verified. If this option is set to False, then the default CA -# truststore is used for verification. -# -# This option is ignored if the "vmware_ca_file" option is set. In that -# case, the ESX/vCenter server certificate will then be verified using -# the file specified using the "vmware_ca_file" option . -# -# Possible Values: -# * True -# * False -# -# Related options: -# * vmware_ca_file -# -# (boolean value) -# Deprecated group/name - [glance_store]/vmware_api_insecure -#vmware_insecure = false - -# -# Absolute path to the CA bundle file. -# -# This configuration option enables the operator to use a custom -# Cerificate Authority File to verify the ESX/vCenter certificate. -# -# If this option is set, the "vmware_insecure" option will be ignored -# and the CA file specified will be used to authenticate the ESX/vCenter -# server certificate and establish a secure connection to the server. -# -# Possible Values: -# * Any string that is a valid absolute path to a CA file -# -# Related options: -# * vmware_insecure -# -# (string value) -#vmware_ca_file = /etc/ssl/certs/ca-certificates.crt - -# -# The datastores where the image can be stored. -# -# This configuration option specifies the datastores where the image can -# be stored in the VMWare store backend. This option may be specified -# multiple times for specifying multiple datastores. The datastore name -# should be specified after its datacenter path, separated by ":". An -# optional weight may be given after the datastore name, separated again -# by ":" to specify the priority. Thus, the required format becomes -# ::. -# -# When adding an image, the datastore with highest weight will be -# selected, unless there is not enough free space available in cases -# where the image size is already known. If no weight is given, it is -# assumed to be zero and the directory will be considered for selection -# last. If multiple datastores have the same weight, then the one with -# the most free space available is selected. -# -# Possible Values: -# * Any string of the format: -# :: -# -# Related options: -# * None -# -# (multi valued) -#vmware_datastores = - -# -# Chunk size for images to be stored in Sheepdog data store. -# -# Provide an integer value representing the size in mebibyte -# (1048576 bytes) to chunk Glance images into. The default -# chunk size is 64 mebibytes. -# -# When using Sheepdog distributed storage system, the images are -# chunked into objects of this size and then stored across the -# distributed data store to use for Glance. -# -# Chunk sizes, if a power of two, help avoid fragmentation and -# enable improved performance. -# -# Possible values: -# * Positive integer value representing size in mebibytes. -# -# Related Options: -# * None -# -# (integer value) -# Minimum value: 1 -#sheepdog_store_chunk_size = 64 - -# -# Port number on which the sheep daemon will listen. -# -# Provide an integer value representing a valid port number on -# which you want the Sheepdog daemon to listen on. The default -# port is 7000. -# -# The Sheepdog daemon, also called 'sheep', manages the storage -# in the distributed cluster by writing objects across the storage -# network. It identifies and acts on the messages it receives on -# the port number set using ``sheepdog_store_port`` option to store -# chunks of Glance images. -# -# Possible values: -# * A valid port number (0 to 65535) -# -# Related Options: -# * sheepdog_store_address -# -# (port value) -# Minimum value: 0 -# Maximum value: 65535 -#sheepdog_store_port = 7000 - -# -# Address to bind the Sheepdog daemon to. -# -# Provide a string value representing the address to bind the -# Sheepdog daemon to. The default address set for the 'sheep' -# is 127.0.0.1. -# -# The Sheepdog daemon, also called 'sheep', manages the storage -# in the distributed cluster by writing objects across the storage -# network. It identifies and acts on the messages directed to the -# address set using ``sheepdog_store_address`` option to store -# chunks of Glance images. -# -# Possible values: -# * A valid IPv4 address -# * A valid IPv6 address -# * A valid hostname -# -# Related Options: -# * sheepdog_store_port -# -# (string value) -#sheepdog_store_address = 127.0.0.1 - -# -# Size, in megabytes, to chunk RADOS images into. -# -# Provide an integer value representing the size in megabytes to chunk -# Glance images into. The default chunk size is 8 megabytes. For optimal -# performance, the value should be a power of two. -# -# When Ceph's RBD object storage system is used as the storage backend -# for storing Glance images, the images are chunked into objects of the -# size set using this option. These chunked objects are then stored -# across the distributed block data store to use for Glance. -# -# Possible Values: -# * Any positive integer value -# -# Related options: -# * None -# -# (integer value) -# Minimum value: 1 -#rbd_store_chunk_size = 8 - -# -# RADOS pool in which images are stored. -# -# When RBD is used as the storage backend for storing Glance images, the -# images are stored by means of logical grouping of the objects (chunks -# of images) into a ``pool``. Each pool is defined with the number of -# placement groups it can contain. The default pool that is used is -# 'images'. -# -# More information on the RBD storage backend can be found here: -# http://ceph.com/planet/how-data-is-stored-in-ceph-cluster/ -# -# Possible Values: -# * A valid pool name -# -# Related options: -# * None -# -# (string value) -#rbd_store_pool = images - -# -# RADOS user to authenticate as. -# -# This configuration option takes in the RADOS user to authenticate as. -# This is only needed when RADOS authentication is enabled and is -# applicable only if the user is using Cephx authentication. If the -# value for this option is not set by the user or is set to None, a -# default value will be chosen, which will be based on the client. -# section in rbd_store_ceph_conf. -# -# Possible Values: -# * A valid RADOS user -# -# Related options: -# * rbd_store_ceph_conf -# -# (string value) -#rbd_store_user = - -# -# Ceph configuration file path. -# -# This configuration option takes in the path to the Ceph configuration -# file to be used. If the value for this option is not set by the user -# or is set to None, librados will locate the default configuration file -# which is located at /etc/ceph/ceph.conf. If using Cephx -# authentication, this file should include a reference to the right -# keyring in a client. section -# -# Possible Values: -# * A valid path to a configuration file -# -# Related options: -# * rbd_store_user -# -# (string value) -#rbd_store_ceph_conf = /etc/ceph/ceph.conf - -# -# Timeout value for connecting to Ceph cluster. -# -# This configuration option takes in the timeout value in seconds used -# when connecting to the Ceph cluster i.e. it sets the time to wait for -# glance-api before closing the connection. This prevents glance-api -# hangups during the connection to RBD. If the value for this option -# is set to less than or equal to 0, no timeout is set and the default -# librados value is used. -# -# Possible Values: -# * Any integer value -# -# Related options: -# * None -# -# (integer value) -#rados_connect_timeout = 0 - # # Information to match when looking for cinder in the service catalog. # @@ -1799,6 +1282,345 @@ # (string value) #rootwrap_config = /etc/glance/rootwrap.conf +# +# Directory to which the filesystem backend store writes images. +# +# Upon start up, Glance creates the directory if it doesn't already +# exist and verifies write access to the user under which +# ``glance-api`` runs. If the write access isn't available, a +# ``BadStoreConfiguration`` exception is raised and the filesystem +# store may not be available for adding new images. +# +# NOTE: This directory is used only when filesystem store is used as a +# storage backend. Either ``filesystem_store_datadir`` or +# ``filesystem_store_datadirs`` option must be specified in +# ``glance-api.conf``. If both options are specified, a +# ``BadStoreConfiguration`` will be raised and the filesystem store +# may not be available for adding new images. +# +# Possible values: +# * A valid path to a directory +# +# Related options: +# * ``filesystem_store_datadirs`` +# * ``filesystem_store_file_perm`` +# +# (string value) +#filesystem_store_datadir = /var/lib/glance/images + +# +# List of directories and their priorities to which the filesystem +# backend store writes images. +# +# The filesystem store can be configured to store images in multiple +# directories as opposed to using a single directory specified by the +# ``filesystem_store_datadir`` configuration option. When using +# multiple directories, each directory can be given an optional +# priority to specify the preference order in which they should +# be used. Priority is an integer that is concatenated to the +# directory path with a colon where a higher value indicates higher +# priority. When two directories have the same priority, the directory +# with most free space is used. When no priority is specified, it +# defaults to zero. +# +# More information on configuring filesystem store with multiple store +# directories can be found at +# http://docs.openstack.org/developer/glance/configuring.html +# +# NOTE: This directory is used only when filesystem store is used as a +# storage backend. Either ``filesystem_store_datadir`` or +# ``filesystem_store_datadirs`` option must be specified in +# ``glance-api.conf``. If both options are specified, a +# ``BadStoreConfiguration`` will be raised and the filesystem store +# may not be available for adding new images. +# +# Possible values: +# * List of strings of the following form: +# * ``:`` +# +# Related options: +# * ``filesystem_store_datadir`` +# * ``filesystem_store_file_perm`` +# +# (multi valued) +#filesystem_store_datadirs = + +# +# Filesystem store metadata file. +# +# The path to a file which contains the metadata to be returned with +# any location associated with the filesystem store. The file must +# contain a valid JSON object. The object should contain the keys +# ``id`` and ``mountpoint``. The value for both keys should be a +# string. +# +# Possible values: +# * A valid path to the store metadata file +# +# Related options: +# * None +# +# (string value) +#filesystem_store_metadata_file = + +# +# File access permissions for the image files. +# +# Set the intended file access permissions for image data. This provides +# a way to enable other services, e.g. Nova, to consume images directly +# from the filesystem store. The users running the services that are +# intended to be given access to could be made a member of the group +# that owns the files created. Assigning a value less then or equal to +# zero for this configuration option signifies that no changes be made +# to the default permissions. This value will be decoded as an octal +# digit. +# +# For more information, please refer the documentation at +# http://docs.openstack.org/developer/glance/configuring.html +# +# Possible values: +# * A valid file access permission +# * Zero +# * Any negative integer +# +# Related options: +# * None +# +# (integer value) +#filesystem_store_file_perm = 0 + +# +# Path to the CA bundle file. +# +# This configuration option enables the operator to use a custom +# Certificate Authority file to verify the remote server certificate. If +# this option is set, the ``https_insecure`` option will be ignored and +# the CA file specified will be used to authenticate the server +# certificate and establish a secure connection to the server. +# +# Possible values: +# * A valid path to a CA file +# +# Related options: +# * https_insecure +# +# (string value) +#https_ca_certificates_file = + +# +# Set verification of the remote server certificate. +# +# This configuration option takes in a boolean value to determine +# whether or not to verify the remote server certificate. If set to +# True, the remote server certificate is not verified. If the option is +# set to False, then the default CA truststore is used for verification. +# +# This option is ignored if ``https_ca_certificates_file`` is set. +# The remote server certificate will then be verified using the file +# specified using the ``https_ca_certificates_file`` option. +# +# Possible values: +# * True +# * False +# +# Related options: +# * https_ca_certificates_file +# +# (boolean value) +#https_insecure = true + +# +# The http/https proxy information to be used to connect to the remote +# server. +# +# This configuration option specifies the http/https proxy information +# that should be used to connect to the remote server. The proxy +# information should be a key value pair of the scheme and proxy, for +# example, http:10.0.0.1:3128. You can also specify proxies for multiple +# schemes by separating the key value pairs with a comma, for example, +# http:10.0.0.1:3128, https:10.0.0.1:1080. +# +# Possible values: +# * A comma separated list of scheme:proxy pairs as described above +# +# Related options: +# * None +# +# (dict value) +#http_proxy_information = + +# +# Size, in megabytes, to chunk RADOS images into. +# +# Provide an integer value representing the size in megabytes to chunk +# Glance images into. The default chunk size is 8 megabytes. For optimal +# performance, the value should be a power of two. +# +# When Ceph's RBD object storage system is used as the storage backend +# for storing Glance images, the images are chunked into objects of the +# size set using this option. These chunked objects are then stored +# across the distributed block data store to use for Glance. +# +# Possible Values: +# * Any positive integer value +# +# Related options: +# * None +# +# (integer value) +# Minimum value: 1 +#rbd_store_chunk_size = 8 + +# +# RADOS pool in which images are stored. +# +# When RBD is used as the storage backend for storing Glance images, the +# images are stored by means of logical grouping of the objects (chunks +# of images) into a ``pool``. Each pool is defined with the number of +# placement groups it can contain. The default pool that is used is +# 'images'. +# +# More information on the RBD storage backend can be found here: +# http://ceph.com/planet/how-data-is-stored-in-ceph-cluster/ +# +# Possible Values: +# * A valid pool name +# +# Related options: +# * None +# +# (string value) +#rbd_store_pool = images + +# +# RADOS user to authenticate as. +# +# This configuration option takes in the RADOS user to authenticate as. +# This is only needed when RADOS authentication is enabled and is +# applicable only if the user is using Cephx authentication. If the +# value for this option is not set by the user or is set to None, a +# default value will be chosen, which will be based on the client. +# section in rbd_store_ceph_conf. +# +# Possible Values: +# * A valid RADOS user +# +# Related options: +# * rbd_store_ceph_conf +# +# (string value) +#rbd_store_user = + +# +# Ceph configuration file path. +# +# This configuration option takes in the path to the Ceph configuration +# file to be used. If the value for this option is not set by the user +# or is set to None, librados will locate the default configuration file +# which is located at /etc/ceph/ceph.conf. If using Cephx +# authentication, this file should include a reference to the right +# keyring in a client. section +# +# Possible Values: +# * A valid path to a configuration file +# +# Related options: +# * rbd_store_user +# +# (string value) +#rbd_store_ceph_conf = /etc/ceph/ceph.conf + +# +# Timeout value for connecting to Ceph cluster. +# +# This configuration option takes in the timeout value in seconds used +# when connecting to the Ceph cluster i.e. it sets the time to wait for +# glance-api before closing the connection. This prevents glance-api +# hangups during the connection to RBD. If the value for this option +# is set to less than or equal to 0, no timeout is set and the default +# librados value is used. +# +# Possible Values: +# * Any integer value +# +# Related options: +# * None +# +# (integer value) +#rados_connect_timeout = 0 + +# +# Chunk size for images to be stored in Sheepdog data store. +# +# Provide an integer value representing the size in mebibyte +# (1048576 bytes) to chunk Glance images into. The default +# chunk size is 64 mebibytes. +# +# When using Sheepdog distributed storage system, the images are +# chunked into objects of this size and then stored across the +# distributed data store to use for Glance. +# +# Chunk sizes, if a power of two, help avoid fragmentation and +# enable improved performance. +# +# Possible values: +# * Positive integer value representing size in mebibytes. +# +# Related Options: +# * None +# +# (integer value) +# Minimum value: 1 +#sheepdog_store_chunk_size = 64 + +# +# Port number on which the sheep daemon will listen. +# +# Provide an integer value representing a valid port number on +# which you want the Sheepdog daemon to listen on. The default +# port is 7000. +# +# The Sheepdog daemon, also called 'sheep', manages the storage +# in the distributed cluster by writing objects across the storage +# network. It identifies and acts on the messages it receives on +# the port number set using ``sheepdog_store_port`` option to store +# chunks of Glance images. +# +# Possible values: +# * A valid port number (0 to 65535) +# +# Related Options: +# * sheepdog_store_address +# +# (port value) +# Minimum value: 0 +# Maximum value: 65535 +#sheepdog_store_port = 7000 + +# +# Address to bind the Sheepdog daemon to. +# +# Provide a string value representing the address to bind the +# Sheepdog daemon to. The default address set for the 'sheep' +# is 127.0.0.1. +# +# The Sheepdog daemon, also called 'sheep', manages the storage +# in the distributed cluster by writing objects across the storage +# network. It identifies and acts on the messages directed to the +# address set using ``sheepdog_store_address`` option to store +# chunks of Glance images. +# +# Possible values: +# * A valid IPv4 address +# * A valid IPv6 address +# * A valid hostname +# +# Related Options: +# * sheepdog_store_port +# +# (string value) +#sheepdog_store_address = 127.0.0.1 + # # Set verification of the server certificate. # @@ -2272,6 +2094,184 @@ # (string value) #swift_store_config_file = +# +# Address of the ESX/ESXi or vCenter Server target system. +# +# This configuration option sets the address of the ESX/ESXi or vCenter +# Server target system. This option is required when using the VMware +# storage backend. The address can contain an IP address (127.0.0.1) or +# a DNS name (www.my-domain.com). +# +# Possible Values: +# * A valid IPv4 or IPv6 address +# * A valid DNS name +# +# Related options: +# * vmware_server_username +# * vmware_server_password +# +# (string value) +#vmware_server_host = 127.0.0.1 + +# +# Server username. +# +# This configuration option takes the username for authenticating with +# the VMware ESX/ESXi or vCenter Server. This option is required when +# using the VMware storage backend. +# +# Possible Values: +# * Any string that is the username for a user with appropriate +# privileges +# +# Related options: +# * vmware_server_host +# * vmware_server_password +# +# (string value) +#vmware_server_username = root + +# +# Server password. +# +# This configuration option takes the password for authenticating with +# the VMware ESX/ESXi or vCenter Server. This option is required when +# using the VMware storage backend. +# +# Possible Values: +# * Any string that is a password corresponding to the username +# specified using the "vmware_server_username" option +# +# Related options: +# * vmware_server_host +# * vmware_server_username +# +# (string value) +#vmware_server_password = vmware + +# +# The number of VMware API retries. +# +# This configuration option specifies the number of times the VMware +# ESX/VC server API must be retried upon connection related issues or +# server API call overload. It is not possible to specify 'retry +# forever'. +# +# Possible Values: +# * Any positive integer value +# +# Related options: +# * None +# +# (integer value) +# Minimum value: 1 +#vmware_api_retry_count = 10 + +# +# Interval in seconds used for polling remote tasks invoked on VMware +# ESX/VC server. +# +# This configuration option takes in the sleep time in seconds for polling an +# on-going async task as part of the VMWare ESX/VC server API call. +# +# Possible Values: +# * Any positive integer value +# +# Related options: +# * None +# +# (integer value) +# Minimum value: 1 +#vmware_task_poll_interval = 5 + +# +# The directory where the glance images will be stored in the datastore. +# +# This configuration option specifies the path to the directory where the +# glance images will be stored in the VMware datastore. If this option +# is not set, the default directory where the glance images are stored +# is openstack_glance. +# +# Possible Values: +# * Any string that is a valid path to a directory +# +# Related options: +# * None +# +# (string value) +#vmware_store_image_dir = /openstack_glance + +# +# Set verification of the ESX/vCenter server certificate. +# +# This configuration option takes a boolean value to determine +# whether or not to verify the ESX/vCenter server certificate. If this +# option is set to True, the ESX/vCenter server certificate is not +# verified. If this option is set to False, then the default CA +# truststore is used for verification. +# +# This option is ignored if the "vmware_ca_file" option is set. In that +# case, the ESX/vCenter server certificate will then be verified using +# the file specified using the "vmware_ca_file" option . +# +# Possible Values: +# * True +# * False +# +# Related options: +# * vmware_ca_file +# +# (boolean value) +# Deprecated group/name - [glance_store]/vmware_api_insecure +#vmware_insecure = false + +# +# Absolute path to the CA bundle file. +# +# This configuration option enables the operator to use a custom +# Cerificate Authority File to verify the ESX/vCenter certificate. +# +# If this option is set, the "vmware_insecure" option will be ignored +# and the CA file specified will be used to authenticate the ESX/vCenter +# server certificate and establish a secure connection to the server. +# +# Possible Values: +# * Any string that is a valid absolute path to a CA file +# +# Related options: +# * vmware_insecure +# +# (string value) +#vmware_ca_file = /etc/ssl/certs/ca-certificates.crt + +# +# The datastores where the image can be stored. +# +# This configuration option specifies the datastores where the image can +# be stored in the VMWare store backend. This option may be specified +# multiple times for specifying multiple datastores. The datastore name +# should be specified after its datacenter path, separated by ":". An +# optional weight may be given after the datastore name, separated again +# by ":" to specify the priority. Thus, the required format becomes +# ::. +# +# When adding an image, the datastore with highest weight will be +# selected, unless there is not enough free space available in cases +# where the image size is already known. If no weight is given, it is +# assumed to be zero and the directory will be considered for selection +# last. If multiple datastores have the same weight, then the one with +# the most free space available is selected. +# +# Possible Values: +# * Any string of the format: +# :: +# +# Related options: +# * None +# +# (multi valued) +#vmware_datastores = + [oslo_policy] diff --git a/etc/glance-glare.conf b/etc/glance-glare.conf index 0e91ce933c..a083129cc4 100644 --- a/etc/glance-glare.conf +++ b/etc/glance-glare.conf @@ -744,523 +744,6 @@ # Minimum value: 0 #store_capabilities_update_min_interval = 0 -# -# Directory to which the filesystem backend store writes images. -# -# Upon start up, Glance creates the directory if it doesn't already -# exist and verifies write access to the user under which -# ``glance-api`` runs. If the write access isn't available, a -# ``BadStoreConfiguration`` exception is raised and the filesystem -# store may not be available for adding new images. -# -# NOTE: This directory is used only when filesystem store is used as a -# storage backend. Either ``filesystem_store_datadir`` or -# ``filesystem_store_datadirs`` option must be specified in -# ``glance-api.conf``. If both options are specified, a -# ``BadStoreConfiguration`` will be raised and the filesystem store -# may not be available for adding new images. -# -# Possible values: -# * A valid path to a directory -# -# Related options: -# * ``filesystem_store_datadirs`` -# * ``filesystem_store_file_perm`` -# -# (string value) -#filesystem_store_datadir = /var/lib/glance/images - -# -# List of directories and their priorities to which the filesystem -# backend store writes images. -# -# The filesystem store can be configured to store images in multiple -# directories as opposed to using a single directory specified by the -# ``filesystem_store_datadir`` configuration option. When using -# multiple directories, each directory can be given an optional -# priority to specify the preference order in which they should -# be used. Priority is an integer that is concatenated to the -# directory path with a colon where a higher value indicates higher -# priority. When two directories have the same priority, the directory -# with most free space is used. When no priority is specified, it -# defaults to zero. -# -# More information on configuring filesystem store with multiple store -# directories can be found at -# http://docs.openstack.org/developer/glance/configuring.html -# -# NOTE: This directory is used only when filesystem store is used as a -# storage backend. Either ``filesystem_store_datadir`` or -# ``filesystem_store_datadirs`` option must be specified in -# ``glance-api.conf``. If both options are specified, a -# ``BadStoreConfiguration`` will be raised and the filesystem store -# may not be available for adding new images. -# -# Possible values: -# * List of strings of the following form: -# * ``:`` -# -# Related options: -# * ``filesystem_store_datadir`` -# * ``filesystem_store_file_perm`` -# -# (multi valued) -#filesystem_store_datadirs = - -# -# Filesystem store metadata file. -# -# The path to a file which contains the metadata to be returned with -# any location associated with the filesystem store. The file must -# contain a valid JSON object. The object should contain the keys -# ``id`` and ``mountpoint``. The value for both keys should be a -# string. -# -# Possible values: -# * A valid path to the store metadata file -# -# Related options: -# * None -# -# (string value) -#filesystem_store_metadata_file = - -# -# File access permissions for the image files. -# -# Set the intended file access permissions for image data. This provides -# a way to enable other services, e.g. Nova, to consume images directly -# from the filesystem store. The users running the services that are -# intended to be given access to could be made a member of the group -# that owns the files created. Assigning a value less then or equal to -# zero for this configuration option signifies that no changes be made -# to the default permissions. This value will be decoded as an octal -# digit. -# -# For more information, please refer the documentation at -# http://docs.openstack.org/developer/glance/configuring.html -# -# Possible values: -# * A valid file access permission -# * Zero -# * Any negative integer -# -# Related options: -# * None -# -# (integer value) -#filesystem_store_file_perm = 0 - -# -# Path to the CA bundle file. -# -# This configuration option enables the operator to use a custom -# Certificate Authority file to verify the remote server certificate. If -# this option is set, the ``https_insecure`` option will be ignored and -# the CA file specified will be used to authenticate the server -# certificate and establish a secure connection to the server. -# -# Possible values: -# * A valid path to a CA file -# -# Related options: -# * https_insecure -# -# (string value) -#https_ca_certificates_file = - -# -# Set verification of the remote server certificate. -# -# This configuration option takes in a boolean value to determine -# whether or not to verify the remote server certificate. If set to -# True, the remote server certificate is not verified. If the option is -# set to False, then the default CA truststore is used for verification. -# -# This option is ignored if ``https_ca_certificates_file`` is set. -# The remote server certificate will then be verified using the file -# specified using the ``https_ca_certificates_file`` option. -# -# Possible values: -# * True -# * False -# -# Related options: -# * https_ca_certificates_file -# -# (boolean value) -#https_insecure = true - -# -# The http/https proxy information to be used to connect to the remote -# server. -# -# This configuration option specifies the http/https proxy information -# that should be used to connect to the remote server. The proxy -# information should be a key value pair of the scheme and proxy, for -# example, http:10.0.0.1:3128. You can also specify proxies for multiple -# schemes by separating the key value pairs with a comma, for example, -# http:10.0.0.1:3128, https:10.0.0.1:1080. -# -# Possible values: -# * A comma separated list of scheme:proxy pairs as described above -# -# Related options: -# * None -# -# (dict value) -#http_proxy_information = - -# -# Address of the ESX/ESXi or vCenter Server target system. -# -# This configuration option sets the address of the ESX/ESXi or vCenter -# Server target system. This option is required when using the VMware -# storage backend. The address can contain an IP address (127.0.0.1) or -# a DNS name (www.my-domain.com). -# -# Possible Values: -# * A valid IPv4 or IPv6 address -# * A valid DNS name -# -# Related options: -# * vmware_server_username -# * vmware_server_password -# -# (string value) -#vmware_server_host = 127.0.0.1 - -# -# Server username. -# -# This configuration option takes the username for authenticating with -# the VMware ESX/ESXi or vCenter Server. This option is required when -# using the VMware storage backend. -# -# Possible Values: -# * Any string that is the username for a user with appropriate -# privileges -# -# Related options: -# * vmware_server_host -# * vmware_server_password -# -# (string value) -#vmware_server_username = root - -# -# Server password. -# -# This configuration option takes the password for authenticating with -# the VMware ESX/ESXi or vCenter Server. This option is required when -# using the VMware storage backend. -# -# Possible Values: -# * Any string that is a password corresponding to the username -# specified using the "vmware_server_username" option -# -# Related options: -# * vmware_server_host -# * vmware_server_username -# -# (string value) -#vmware_server_password = vmware - -# -# The number of VMware API retries. -# -# This configuration option specifies the number of times the VMware -# ESX/VC server API must be retried upon connection related issues or -# server API call overload. It is not possible to specify 'retry -# forever'. -# -# Possible Values: -# * Any positive integer value -# -# Related options: -# * None -# -# (integer value) -# Minimum value: 1 -#vmware_api_retry_count = 10 - -# -# Interval in seconds used for polling remote tasks invoked on VMware -# ESX/VC server. -# -# This configuration option takes in the sleep time in seconds for polling an -# on-going async task as part of the VMWare ESX/VC server API call. -# -# Possible Values: -# * Any positive integer value -# -# Related options: -# * None -# -# (integer value) -# Minimum value: 1 -#vmware_task_poll_interval = 5 - -# -# The directory where the glance images will be stored in the datastore. -# -# This configuration option specifies the path to the directory where the -# glance images will be stored in the VMware datastore. If this option -# is not set, the default directory where the glance images are stored -# is openstack_glance. -# -# Possible Values: -# * Any string that is a valid path to a directory -# -# Related options: -# * None -# -# (string value) -#vmware_store_image_dir = /openstack_glance - -# -# Set verification of the ESX/vCenter server certificate. -# -# This configuration option takes a boolean value to determine -# whether or not to verify the ESX/vCenter server certificate. If this -# option is set to True, the ESX/vCenter server certificate is not -# verified. If this option is set to False, then the default CA -# truststore is used for verification. -# -# This option is ignored if the "vmware_ca_file" option is set. In that -# case, the ESX/vCenter server certificate will then be verified using -# the file specified using the "vmware_ca_file" option . -# -# Possible Values: -# * True -# * False -# -# Related options: -# * vmware_ca_file -# -# (boolean value) -# Deprecated group/name - [glance_store]/vmware_api_insecure -#vmware_insecure = false - -# -# Absolute path to the CA bundle file. -# -# This configuration option enables the operator to use a custom -# Cerificate Authority File to verify the ESX/vCenter certificate. -# -# If this option is set, the "vmware_insecure" option will be ignored -# and the CA file specified will be used to authenticate the ESX/vCenter -# server certificate and establish a secure connection to the server. -# -# Possible Values: -# * Any string that is a valid absolute path to a CA file -# -# Related options: -# * vmware_insecure -# -# (string value) -#vmware_ca_file = /etc/ssl/certs/ca-certificates.crt - -# -# The datastores where the image can be stored. -# -# This configuration option specifies the datastores where the image can -# be stored in the VMWare store backend. This option may be specified -# multiple times for specifying multiple datastores. The datastore name -# should be specified after its datacenter path, separated by ":". An -# optional weight may be given after the datastore name, separated again -# by ":" to specify the priority. Thus, the required format becomes -# ::. -# -# When adding an image, the datastore with highest weight will be -# selected, unless there is not enough free space available in cases -# where the image size is already known. If no weight is given, it is -# assumed to be zero and the directory will be considered for selection -# last. If multiple datastores have the same weight, then the one with -# the most free space available is selected. -# -# Possible Values: -# * Any string of the format: -# :: -# -# Related options: -# * None -# -# (multi valued) -#vmware_datastores = - -# -# Chunk size for images to be stored in Sheepdog data store. -# -# Provide an integer value representing the size in mebibyte -# (1048576 bytes) to chunk Glance images into. The default -# chunk size is 64 mebibytes. -# -# When using Sheepdog distributed storage system, the images are -# chunked into objects of this size and then stored across the -# distributed data store to use for Glance. -# -# Chunk sizes, if a power of two, help avoid fragmentation and -# enable improved performance. -# -# Possible values: -# * Positive integer value representing size in mebibytes. -# -# Related Options: -# * None -# -# (integer value) -# Minimum value: 1 -#sheepdog_store_chunk_size = 64 - -# -# Port number on which the sheep daemon will listen. -# -# Provide an integer value representing a valid port number on -# which you want the Sheepdog daemon to listen on. The default -# port is 7000. -# -# The Sheepdog daemon, also called 'sheep', manages the storage -# in the distributed cluster by writing objects across the storage -# network. It identifies and acts on the messages it receives on -# the port number set using ``sheepdog_store_port`` option to store -# chunks of Glance images. -# -# Possible values: -# * A valid port number (0 to 65535) -# -# Related Options: -# * sheepdog_store_address -# -# (port value) -# Minimum value: 0 -# Maximum value: 65535 -#sheepdog_store_port = 7000 - -# -# Address to bind the Sheepdog daemon to. -# -# Provide a string value representing the address to bind the -# Sheepdog daemon to. The default address set for the 'sheep' -# is 127.0.0.1. -# -# The Sheepdog daemon, also called 'sheep', manages the storage -# in the distributed cluster by writing objects across the storage -# network. It identifies and acts on the messages directed to the -# address set using ``sheepdog_store_address`` option to store -# chunks of Glance images. -# -# Possible values: -# * A valid IPv4 address -# * A valid IPv6 address -# * A valid hostname -# -# Related Options: -# * sheepdog_store_port -# -# (string value) -#sheepdog_store_address = 127.0.0.1 - -# -# Size, in megabytes, to chunk RADOS images into. -# -# Provide an integer value representing the size in megabytes to chunk -# Glance images into. The default chunk size is 8 megabytes. For optimal -# performance, the value should be a power of two. -# -# When Ceph's RBD object storage system is used as the storage backend -# for storing Glance images, the images are chunked into objects of the -# size set using this option. These chunked objects are then stored -# across the distributed block data store to use for Glance. -# -# Possible Values: -# * Any positive integer value -# -# Related options: -# * None -# -# (integer value) -# Minimum value: 1 -#rbd_store_chunk_size = 8 - -# -# RADOS pool in which images are stored. -# -# When RBD is used as the storage backend for storing Glance images, the -# images are stored by means of logical grouping of the objects (chunks -# of images) into a ``pool``. Each pool is defined with the number of -# placement groups it can contain. The default pool that is used is -# 'images'. -# -# More information on the RBD storage backend can be found here: -# http://ceph.com/planet/how-data-is-stored-in-ceph-cluster/ -# -# Possible Values: -# * A valid pool name -# -# Related options: -# * None -# -# (string value) -#rbd_store_pool = images - -# -# RADOS user to authenticate as. -# -# This configuration option takes in the RADOS user to authenticate as. -# This is only needed when RADOS authentication is enabled and is -# applicable only if the user is using Cephx authentication. If the -# value for this option is not set by the user or is set to None, a -# default value will be chosen, which will be based on the client. -# section in rbd_store_ceph_conf. -# -# Possible Values: -# * A valid RADOS user -# -# Related options: -# * rbd_store_ceph_conf -# -# (string value) -#rbd_store_user = - -# -# Ceph configuration file path. -# -# This configuration option takes in the path to the Ceph configuration -# file to be used. If the value for this option is not set by the user -# or is set to None, librados will locate the default configuration file -# which is located at /etc/ceph/ceph.conf. If using Cephx -# authentication, this file should include a reference to the right -# keyring in a client. section -# -# Possible Values: -# * A valid path to a configuration file -# -# Related options: -# * rbd_store_user -# -# (string value) -#rbd_store_ceph_conf = /etc/ceph/ceph.conf - -# -# Timeout value for connecting to Ceph cluster. -# -# This configuration option takes in the timeout value in seconds used -# when connecting to the Ceph cluster i.e. it sets the time to wait for -# glance-api before closing the connection. This prevents glance-api -# hangups during the connection to RBD. If the value for this option -# is set to less than or equal to 0, no timeout is set and the default -# librados value is used. -# -# Possible Values: -# * Any integer value -# -# Related options: -# * None -# -# (integer value) -#rados_connect_timeout = 0 - # # Information to match when looking for cinder in the service catalog. # @@ -1500,6 +983,345 @@ # (string value) #rootwrap_config = /etc/glance/rootwrap.conf +# +# Directory to which the filesystem backend store writes images. +# +# Upon start up, Glance creates the directory if it doesn't already +# exist and verifies write access to the user under which +# ``glance-api`` runs. If the write access isn't available, a +# ``BadStoreConfiguration`` exception is raised and the filesystem +# store may not be available for adding new images. +# +# NOTE: This directory is used only when filesystem store is used as a +# storage backend. Either ``filesystem_store_datadir`` or +# ``filesystem_store_datadirs`` option must be specified in +# ``glance-api.conf``. If both options are specified, a +# ``BadStoreConfiguration`` will be raised and the filesystem store +# may not be available for adding new images. +# +# Possible values: +# * A valid path to a directory +# +# Related options: +# * ``filesystem_store_datadirs`` +# * ``filesystem_store_file_perm`` +# +# (string value) +#filesystem_store_datadir = /var/lib/glance/images + +# +# List of directories and their priorities to which the filesystem +# backend store writes images. +# +# The filesystem store can be configured to store images in multiple +# directories as opposed to using a single directory specified by the +# ``filesystem_store_datadir`` configuration option. When using +# multiple directories, each directory can be given an optional +# priority to specify the preference order in which they should +# be used. Priority is an integer that is concatenated to the +# directory path with a colon where a higher value indicates higher +# priority. When two directories have the same priority, the directory +# with most free space is used. When no priority is specified, it +# defaults to zero. +# +# More information on configuring filesystem store with multiple store +# directories can be found at +# http://docs.openstack.org/developer/glance/configuring.html +# +# NOTE: This directory is used only when filesystem store is used as a +# storage backend. Either ``filesystem_store_datadir`` or +# ``filesystem_store_datadirs`` option must be specified in +# ``glance-api.conf``. If both options are specified, a +# ``BadStoreConfiguration`` will be raised and the filesystem store +# may not be available for adding new images. +# +# Possible values: +# * List of strings of the following form: +# * ``:`` +# +# Related options: +# * ``filesystem_store_datadir`` +# * ``filesystem_store_file_perm`` +# +# (multi valued) +#filesystem_store_datadirs = + +# +# Filesystem store metadata file. +# +# The path to a file which contains the metadata to be returned with +# any location associated with the filesystem store. The file must +# contain a valid JSON object. The object should contain the keys +# ``id`` and ``mountpoint``. The value for both keys should be a +# string. +# +# Possible values: +# * A valid path to the store metadata file +# +# Related options: +# * None +# +# (string value) +#filesystem_store_metadata_file = + +# +# File access permissions for the image files. +# +# Set the intended file access permissions for image data. This provides +# a way to enable other services, e.g. Nova, to consume images directly +# from the filesystem store. The users running the services that are +# intended to be given access to could be made a member of the group +# that owns the files created. Assigning a value less then or equal to +# zero for this configuration option signifies that no changes be made +# to the default permissions. This value will be decoded as an octal +# digit. +# +# For more information, please refer the documentation at +# http://docs.openstack.org/developer/glance/configuring.html +# +# Possible values: +# * A valid file access permission +# * Zero +# * Any negative integer +# +# Related options: +# * None +# +# (integer value) +#filesystem_store_file_perm = 0 + +# +# Path to the CA bundle file. +# +# This configuration option enables the operator to use a custom +# Certificate Authority file to verify the remote server certificate. If +# this option is set, the ``https_insecure`` option will be ignored and +# the CA file specified will be used to authenticate the server +# certificate and establish a secure connection to the server. +# +# Possible values: +# * A valid path to a CA file +# +# Related options: +# * https_insecure +# +# (string value) +#https_ca_certificates_file = + +# +# Set verification of the remote server certificate. +# +# This configuration option takes in a boolean value to determine +# whether or not to verify the remote server certificate. If set to +# True, the remote server certificate is not verified. If the option is +# set to False, then the default CA truststore is used for verification. +# +# This option is ignored if ``https_ca_certificates_file`` is set. +# The remote server certificate will then be verified using the file +# specified using the ``https_ca_certificates_file`` option. +# +# Possible values: +# * True +# * False +# +# Related options: +# * https_ca_certificates_file +# +# (boolean value) +#https_insecure = true + +# +# The http/https proxy information to be used to connect to the remote +# server. +# +# This configuration option specifies the http/https proxy information +# that should be used to connect to the remote server. The proxy +# information should be a key value pair of the scheme and proxy, for +# example, http:10.0.0.1:3128. You can also specify proxies for multiple +# schemes by separating the key value pairs with a comma, for example, +# http:10.0.0.1:3128, https:10.0.0.1:1080. +# +# Possible values: +# * A comma separated list of scheme:proxy pairs as described above +# +# Related options: +# * None +# +# (dict value) +#http_proxy_information = + +# +# Size, in megabytes, to chunk RADOS images into. +# +# Provide an integer value representing the size in megabytes to chunk +# Glance images into. The default chunk size is 8 megabytes. For optimal +# performance, the value should be a power of two. +# +# When Ceph's RBD object storage system is used as the storage backend +# for storing Glance images, the images are chunked into objects of the +# size set using this option. These chunked objects are then stored +# across the distributed block data store to use for Glance. +# +# Possible Values: +# * Any positive integer value +# +# Related options: +# * None +# +# (integer value) +# Minimum value: 1 +#rbd_store_chunk_size = 8 + +# +# RADOS pool in which images are stored. +# +# When RBD is used as the storage backend for storing Glance images, the +# images are stored by means of logical grouping of the objects (chunks +# of images) into a ``pool``. Each pool is defined with the number of +# placement groups it can contain. The default pool that is used is +# 'images'. +# +# More information on the RBD storage backend can be found here: +# http://ceph.com/planet/how-data-is-stored-in-ceph-cluster/ +# +# Possible Values: +# * A valid pool name +# +# Related options: +# * None +# +# (string value) +#rbd_store_pool = images + +# +# RADOS user to authenticate as. +# +# This configuration option takes in the RADOS user to authenticate as. +# This is only needed when RADOS authentication is enabled and is +# applicable only if the user is using Cephx authentication. If the +# value for this option is not set by the user or is set to None, a +# default value will be chosen, which will be based on the client. +# section in rbd_store_ceph_conf. +# +# Possible Values: +# * A valid RADOS user +# +# Related options: +# * rbd_store_ceph_conf +# +# (string value) +#rbd_store_user = + +# +# Ceph configuration file path. +# +# This configuration option takes in the path to the Ceph configuration +# file to be used. If the value for this option is not set by the user +# or is set to None, librados will locate the default configuration file +# which is located at /etc/ceph/ceph.conf. If using Cephx +# authentication, this file should include a reference to the right +# keyring in a client. section +# +# Possible Values: +# * A valid path to a configuration file +# +# Related options: +# * rbd_store_user +# +# (string value) +#rbd_store_ceph_conf = /etc/ceph/ceph.conf + +# +# Timeout value for connecting to Ceph cluster. +# +# This configuration option takes in the timeout value in seconds used +# when connecting to the Ceph cluster i.e. it sets the time to wait for +# glance-api before closing the connection. This prevents glance-api +# hangups during the connection to RBD. If the value for this option +# is set to less than or equal to 0, no timeout is set and the default +# librados value is used. +# +# Possible Values: +# * Any integer value +# +# Related options: +# * None +# +# (integer value) +#rados_connect_timeout = 0 + +# +# Chunk size for images to be stored in Sheepdog data store. +# +# Provide an integer value representing the size in mebibyte +# (1048576 bytes) to chunk Glance images into. The default +# chunk size is 64 mebibytes. +# +# When using Sheepdog distributed storage system, the images are +# chunked into objects of this size and then stored across the +# distributed data store to use for Glance. +# +# Chunk sizes, if a power of two, help avoid fragmentation and +# enable improved performance. +# +# Possible values: +# * Positive integer value representing size in mebibytes. +# +# Related Options: +# * None +# +# (integer value) +# Minimum value: 1 +#sheepdog_store_chunk_size = 64 + +# +# Port number on which the sheep daemon will listen. +# +# Provide an integer value representing a valid port number on +# which you want the Sheepdog daemon to listen on. The default +# port is 7000. +# +# The Sheepdog daemon, also called 'sheep', manages the storage +# in the distributed cluster by writing objects across the storage +# network. It identifies and acts on the messages it receives on +# the port number set using ``sheepdog_store_port`` option to store +# chunks of Glance images. +# +# Possible values: +# * A valid port number (0 to 65535) +# +# Related Options: +# * sheepdog_store_address +# +# (port value) +# Minimum value: 0 +# Maximum value: 65535 +#sheepdog_store_port = 7000 + +# +# Address to bind the Sheepdog daemon to. +# +# Provide a string value representing the address to bind the +# Sheepdog daemon to. The default address set for the 'sheep' +# is 127.0.0.1. +# +# The Sheepdog daemon, also called 'sheep', manages the storage +# in the distributed cluster by writing objects across the storage +# network. It identifies and acts on the messages directed to the +# address set using ``sheepdog_store_address`` option to store +# chunks of Glance images. +# +# Possible values: +# * A valid IPv4 address +# * A valid IPv6 address +# * A valid hostname +# +# Related Options: +# * sheepdog_store_port +# +# (string value) +#sheepdog_store_address = 127.0.0.1 + # # Set verification of the server certificate. # @@ -1973,6 +1795,184 @@ # (string value) #swift_store_config_file = +# +# Address of the ESX/ESXi or vCenter Server target system. +# +# This configuration option sets the address of the ESX/ESXi or vCenter +# Server target system. This option is required when using the VMware +# storage backend. The address can contain an IP address (127.0.0.1) or +# a DNS name (www.my-domain.com). +# +# Possible Values: +# * A valid IPv4 or IPv6 address +# * A valid DNS name +# +# Related options: +# * vmware_server_username +# * vmware_server_password +# +# (string value) +#vmware_server_host = 127.0.0.1 + +# +# Server username. +# +# This configuration option takes the username for authenticating with +# the VMware ESX/ESXi or vCenter Server. This option is required when +# using the VMware storage backend. +# +# Possible Values: +# * Any string that is the username for a user with appropriate +# privileges +# +# Related options: +# * vmware_server_host +# * vmware_server_password +# +# (string value) +#vmware_server_username = root + +# +# Server password. +# +# This configuration option takes the password for authenticating with +# the VMware ESX/ESXi or vCenter Server. This option is required when +# using the VMware storage backend. +# +# Possible Values: +# * Any string that is a password corresponding to the username +# specified using the "vmware_server_username" option +# +# Related options: +# * vmware_server_host +# * vmware_server_username +# +# (string value) +#vmware_server_password = vmware + +# +# The number of VMware API retries. +# +# This configuration option specifies the number of times the VMware +# ESX/VC server API must be retried upon connection related issues or +# server API call overload. It is not possible to specify 'retry +# forever'. +# +# Possible Values: +# * Any positive integer value +# +# Related options: +# * None +# +# (integer value) +# Minimum value: 1 +#vmware_api_retry_count = 10 + +# +# Interval in seconds used for polling remote tasks invoked on VMware +# ESX/VC server. +# +# This configuration option takes in the sleep time in seconds for polling an +# on-going async task as part of the VMWare ESX/VC server API call. +# +# Possible Values: +# * Any positive integer value +# +# Related options: +# * None +# +# (integer value) +# Minimum value: 1 +#vmware_task_poll_interval = 5 + +# +# The directory where the glance images will be stored in the datastore. +# +# This configuration option specifies the path to the directory where the +# glance images will be stored in the VMware datastore. If this option +# is not set, the default directory where the glance images are stored +# is openstack_glance. +# +# Possible Values: +# * Any string that is a valid path to a directory +# +# Related options: +# * None +# +# (string value) +#vmware_store_image_dir = /openstack_glance + +# +# Set verification of the ESX/vCenter server certificate. +# +# This configuration option takes a boolean value to determine +# whether or not to verify the ESX/vCenter server certificate. If this +# option is set to True, the ESX/vCenter server certificate is not +# verified. If this option is set to False, then the default CA +# truststore is used for verification. +# +# This option is ignored if the "vmware_ca_file" option is set. In that +# case, the ESX/vCenter server certificate will then be verified using +# the file specified using the "vmware_ca_file" option . +# +# Possible Values: +# * True +# * False +# +# Related options: +# * vmware_ca_file +# +# (boolean value) +# Deprecated group/name - [glance_store]/vmware_api_insecure +#vmware_insecure = false + +# +# Absolute path to the CA bundle file. +# +# This configuration option enables the operator to use a custom +# Cerificate Authority File to verify the ESX/vCenter certificate. +# +# If this option is set, the "vmware_insecure" option will be ignored +# and the CA file specified will be used to authenticate the ESX/vCenter +# server certificate and establish a secure connection to the server. +# +# Possible Values: +# * Any string that is a valid absolute path to a CA file +# +# Related options: +# * vmware_insecure +# +# (string value) +#vmware_ca_file = /etc/ssl/certs/ca-certificates.crt + +# +# The datastores where the image can be stored. +# +# This configuration option specifies the datastores where the image can +# be stored in the VMWare store backend. This option may be specified +# multiple times for specifying multiple datastores. The datastore name +# should be specified after its datacenter path, separated by ":". An +# optional weight may be given after the datastore name, separated again +# by ":" to specify the priority. Thus, the required format becomes +# ::. +# +# When adding an image, the datastore with highest weight will be +# selected, unless there is not enough free space available in cases +# where the image size is already known. If no weight is given, it is +# assumed to be zero and the directory will be considered for selection +# last. If multiple datastores have the same weight, then the one with +# the most free space available is selected. +# +# Possible Values: +# * Any string of the format: +# :: +# +# Related options: +# * None +# +# (multi valued) +#vmware_datastores = + [keystone_authtoken] diff --git a/etc/glance-scrubber.conf b/etc/glance-scrubber.conf index 9440b7ac65..e51aedc143 100644 --- a/etc/glance-scrubber.conf +++ b/etc/glance-scrubber.conf @@ -1191,523 +1191,6 @@ # Minimum value: 0 #store_capabilities_update_min_interval = 0 -# -# Directory to which the filesystem backend store writes images. -# -# Upon start up, Glance creates the directory if it doesn't already -# exist and verifies write access to the user under which -# ``glance-api`` runs. If the write access isn't available, a -# ``BadStoreConfiguration`` exception is raised and the filesystem -# store may not be available for adding new images. -# -# NOTE: This directory is used only when filesystem store is used as a -# storage backend. Either ``filesystem_store_datadir`` or -# ``filesystem_store_datadirs`` option must be specified in -# ``glance-api.conf``. If both options are specified, a -# ``BadStoreConfiguration`` will be raised and the filesystem store -# may not be available for adding new images. -# -# Possible values: -# * A valid path to a directory -# -# Related options: -# * ``filesystem_store_datadirs`` -# * ``filesystem_store_file_perm`` -# -# (string value) -#filesystem_store_datadir = /var/lib/glance/images - -# -# List of directories and their priorities to which the filesystem -# backend store writes images. -# -# The filesystem store can be configured to store images in multiple -# directories as opposed to using a single directory specified by the -# ``filesystem_store_datadir`` configuration option. When using -# multiple directories, each directory can be given an optional -# priority to specify the preference order in which they should -# be used. Priority is an integer that is concatenated to the -# directory path with a colon where a higher value indicates higher -# priority. When two directories have the same priority, the directory -# with most free space is used. When no priority is specified, it -# defaults to zero. -# -# More information on configuring filesystem store with multiple store -# directories can be found at -# http://docs.openstack.org/developer/glance/configuring.html -# -# NOTE: This directory is used only when filesystem store is used as a -# storage backend. Either ``filesystem_store_datadir`` or -# ``filesystem_store_datadirs`` option must be specified in -# ``glance-api.conf``. If both options are specified, a -# ``BadStoreConfiguration`` will be raised and the filesystem store -# may not be available for adding new images. -# -# Possible values: -# * List of strings of the following form: -# * ``:`` -# -# Related options: -# * ``filesystem_store_datadir`` -# * ``filesystem_store_file_perm`` -# -# (multi valued) -#filesystem_store_datadirs = - -# -# Filesystem store metadata file. -# -# The path to a file which contains the metadata to be returned with -# any location associated with the filesystem store. The file must -# contain a valid JSON object. The object should contain the keys -# ``id`` and ``mountpoint``. The value for both keys should be a -# string. -# -# Possible values: -# * A valid path to the store metadata file -# -# Related options: -# * None -# -# (string value) -#filesystem_store_metadata_file = - -# -# File access permissions for the image files. -# -# Set the intended file access permissions for image data. This provides -# a way to enable other services, e.g. Nova, to consume images directly -# from the filesystem store. The users running the services that are -# intended to be given access to could be made a member of the group -# that owns the files created. Assigning a value less then or equal to -# zero for this configuration option signifies that no changes be made -# to the default permissions. This value will be decoded as an octal -# digit. -# -# For more information, please refer the documentation at -# http://docs.openstack.org/developer/glance/configuring.html -# -# Possible values: -# * A valid file access permission -# * Zero -# * Any negative integer -# -# Related options: -# * None -# -# (integer value) -#filesystem_store_file_perm = 0 - -# -# Path to the CA bundle file. -# -# This configuration option enables the operator to use a custom -# Certificate Authority file to verify the remote server certificate. If -# this option is set, the ``https_insecure`` option will be ignored and -# the CA file specified will be used to authenticate the server -# certificate and establish a secure connection to the server. -# -# Possible values: -# * A valid path to a CA file -# -# Related options: -# * https_insecure -# -# (string value) -#https_ca_certificates_file = - -# -# Set verification of the remote server certificate. -# -# This configuration option takes in a boolean value to determine -# whether or not to verify the remote server certificate. If set to -# True, the remote server certificate is not verified. If the option is -# set to False, then the default CA truststore is used for verification. -# -# This option is ignored if ``https_ca_certificates_file`` is set. -# The remote server certificate will then be verified using the file -# specified using the ``https_ca_certificates_file`` option. -# -# Possible values: -# * True -# * False -# -# Related options: -# * https_ca_certificates_file -# -# (boolean value) -#https_insecure = true - -# -# The http/https proxy information to be used to connect to the remote -# server. -# -# This configuration option specifies the http/https proxy information -# that should be used to connect to the remote server. The proxy -# information should be a key value pair of the scheme and proxy, for -# example, http:10.0.0.1:3128. You can also specify proxies for multiple -# schemes by separating the key value pairs with a comma, for example, -# http:10.0.0.1:3128, https:10.0.0.1:1080. -# -# Possible values: -# * A comma separated list of scheme:proxy pairs as described above -# -# Related options: -# * None -# -# (dict value) -#http_proxy_information = - -# -# Address of the ESX/ESXi or vCenter Server target system. -# -# This configuration option sets the address of the ESX/ESXi or vCenter -# Server target system. This option is required when using the VMware -# storage backend. The address can contain an IP address (127.0.0.1) or -# a DNS name (www.my-domain.com). -# -# Possible Values: -# * A valid IPv4 or IPv6 address -# * A valid DNS name -# -# Related options: -# * vmware_server_username -# * vmware_server_password -# -# (string value) -#vmware_server_host = 127.0.0.1 - -# -# Server username. -# -# This configuration option takes the username for authenticating with -# the VMware ESX/ESXi or vCenter Server. This option is required when -# using the VMware storage backend. -# -# Possible Values: -# * Any string that is the username for a user with appropriate -# privileges -# -# Related options: -# * vmware_server_host -# * vmware_server_password -# -# (string value) -#vmware_server_username = root - -# -# Server password. -# -# This configuration option takes the password for authenticating with -# the VMware ESX/ESXi or vCenter Server. This option is required when -# using the VMware storage backend. -# -# Possible Values: -# * Any string that is a password corresponding to the username -# specified using the "vmware_server_username" option -# -# Related options: -# * vmware_server_host -# * vmware_server_username -# -# (string value) -#vmware_server_password = vmware - -# -# The number of VMware API retries. -# -# This configuration option specifies the number of times the VMware -# ESX/VC server API must be retried upon connection related issues or -# server API call overload. It is not possible to specify 'retry -# forever'. -# -# Possible Values: -# * Any positive integer value -# -# Related options: -# * None -# -# (integer value) -# Minimum value: 1 -#vmware_api_retry_count = 10 - -# -# Interval in seconds used for polling remote tasks invoked on VMware -# ESX/VC server. -# -# This configuration option takes in the sleep time in seconds for polling an -# on-going async task as part of the VMWare ESX/VC server API call. -# -# Possible Values: -# * Any positive integer value -# -# Related options: -# * None -# -# (integer value) -# Minimum value: 1 -#vmware_task_poll_interval = 5 - -# -# The directory where the glance images will be stored in the datastore. -# -# This configuration option specifies the path to the directory where the -# glance images will be stored in the VMware datastore. If this option -# is not set, the default directory where the glance images are stored -# is openstack_glance. -# -# Possible Values: -# * Any string that is a valid path to a directory -# -# Related options: -# * None -# -# (string value) -#vmware_store_image_dir = /openstack_glance - -# -# Set verification of the ESX/vCenter server certificate. -# -# This configuration option takes a boolean value to determine -# whether or not to verify the ESX/vCenter server certificate. If this -# option is set to True, the ESX/vCenter server certificate is not -# verified. If this option is set to False, then the default CA -# truststore is used for verification. -# -# This option is ignored if the "vmware_ca_file" option is set. In that -# case, the ESX/vCenter server certificate will then be verified using -# the file specified using the "vmware_ca_file" option . -# -# Possible Values: -# * True -# * False -# -# Related options: -# * vmware_ca_file -# -# (boolean value) -# Deprecated group/name - [glance_store]/vmware_api_insecure -#vmware_insecure = false - -# -# Absolute path to the CA bundle file. -# -# This configuration option enables the operator to use a custom -# Cerificate Authority File to verify the ESX/vCenter certificate. -# -# If this option is set, the "vmware_insecure" option will be ignored -# and the CA file specified will be used to authenticate the ESX/vCenter -# server certificate and establish a secure connection to the server. -# -# Possible Values: -# * Any string that is a valid absolute path to a CA file -# -# Related options: -# * vmware_insecure -# -# (string value) -#vmware_ca_file = /etc/ssl/certs/ca-certificates.crt - -# -# The datastores where the image can be stored. -# -# This configuration option specifies the datastores where the image can -# be stored in the VMWare store backend. This option may be specified -# multiple times for specifying multiple datastores. The datastore name -# should be specified after its datacenter path, separated by ":". An -# optional weight may be given after the datastore name, separated again -# by ":" to specify the priority. Thus, the required format becomes -# ::. -# -# When adding an image, the datastore with highest weight will be -# selected, unless there is not enough free space available in cases -# where the image size is already known. If no weight is given, it is -# assumed to be zero and the directory will be considered for selection -# last. If multiple datastores have the same weight, then the one with -# the most free space available is selected. -# -# Possible Values: -# * Any string of the format: -# :: -# -# Related options: -# * None -# -# (multi valued) -#vmware_datastores = - -# -# Chunk size for images to be stored in Sheepdog data store. -# -# Provide an integer value representing the size in mebibyte -# (1048576 bytes) to chunk Glance images into. The default -# chunk size is 64 mebibytes. -# -# When using Sheepdog distributed storage system, the images are -# chunked into objects of this size and then stored across the -# distributed data store to use for Glance. -# -# Chunk sizes, if a power of two, help avoid fragmentation and -# enable improved performance. -# -# Possible values: -# * Positive integer value representing size in mebibytes. -# -# Related Options: -# * None -# -# (integer value) -# Minimum value: 1 -#sheepdog_store_chunk_size = 64 - -# -# Port number on which the sheep daemon will listen. -# -# Provide an integer value representing a valid port number on -# which you want the Sheepdog daemon to listen on. The default -# port is 7000. -# -# The Sheepdog daemon, also called 'sheep', manages the storage -# in the distributed cluster by writing objects across the storage -# network. It identifies and acts on the messages it receives on -# the port number set using ``sheepdog_store_port`` option to store -# chunks of Glance images. -# -# Possible values: -# * A valid port number (0 to 65535) -# -# Related Options: -# * sheepdog_store_address -# -# (port value) -# Minimum value: 0 -# Maximum value: 65535 -#sheepdog_store_port = 7000 - -# -# Address to bind the Sheepdog daemon to. -# -# Provide a string value representing the address to bind the -# Sheepdog daemon to. The default address set for the 'sheep' -# is 127.0.0.1. -# -# The Sheepdog daemon, also called 'sheep', manages the storage -# in the distributed cluster by writing objects across the storage -# network. It identifies and acts on the messages directed to the -# address set using ``sheepdog_store_address`` option to store -# chunks of Glance images. -# -# Possible values: -# * A valid IPv4 address -# * A valid IPv6 address -# * A valid hostname -# -# Related Options: -# * sheepdog_store_port -# -# (string value) -#sheepdog_store_address = 127.0.0.1 - -# -# Size, in megabytes, to chunk RADOS images into. -# -# Provide an integer value representing the size in megabytes to chunk -# Glance images into. The default chunk size is 8 megabytes. For optimal -# performance, the value should be a power of two. -# -# When Ceph's RBD object storage system is used as the storage backend -# for storing Glance images, the images are chunked into objects of the -# size set using this option. These chunked objects are then stored -# across the distributed block data store to use for Glance. -# -# Possible Values: -# * Any positive integer value -# -# Related options: -# * None -# -# (integer value) -# Minimum value: 1 -#rbd_store_chunk_size = 8 - -# -# RADOS pool in which images are stored. -# -# When RBD is used as the storage backend for storing Glance images, the -# images are stored by means of logical grouping of the objects (chunks -# of images) into a ``pool``. Each pool is defined with the number of -# placement groups it can contain. The default pool that is used is -# 'images'. -# -# More information on the RBD storage backend can be found here: -# http://ceph.com/planet/how-data-is-stored-in-ceph-cluster/ -# -# Possible Values: -# * A valid pool name -# -# Related options: -# * None -# -# (string value) -#rbd_store_pool = images - -# -# RADOS user to authenticate as. -# -# This configuration option takes in the RADOS user to authenticate as. -# This is only needed when RADOS authentication is enabled and is -# applicable only if the user is using Cephx authentication. If the -# value for this option is not set by the user or is set to None, a -# default value will be chosen, which will be based on the client. -# section in rbd_store_ceph_conf. -# -# Possible Values: -# * A valid RADOS user -# -# Related options: -# * rbd_store_ceph_conf -# -# (string value) -#rbd_store_user = - -# -# Ceph configuration file path. -# -# This configuration option takes in the path to the Ceph configuration -# file to be used. If the value for this option is not set by the user -# or is set to None, librados will locate the default configuration file -# which is located at /etc/ceph/ceph.conf. If using Cephx -# authentication, this file should include a reference to the right -# keyring in a client. section -# -# Possible Values: -# * A valid path to a configuration file -# -# Related options: -# * rbd_store_user -# -# (string value) -#rbd_store_ceph_conf = /etc/ceph/ceph.conf - -# -# Timeout value for connecting to Ceph cluster. -# -# This configuration option takes in the timeout value in seconds used -# when connecting to the Ceph cluster i.e. it sets the time to wait for -# glance-api before closing the connection. This prevents glance-api -# hangups during the connection to RBD. If the value for this option -# is set to less than or equal to 0, no timeout is set and the default -# librados value is used. -# -# Possible Values: -# * Any integer value -# -# Related options: -# * None -# -# (integer value) -#rados_connect_timeout = 0 - # # Information to match when looking for cinder in the service catalog. # @@ -1947,6 +1430,345 @@ # (string value) #rootwrap_config = /etc/glance/rootwrap.conf +# +# Directory to which the filesystem backend store writes images. +# +# Upon start up, Glance creates the directory if it doesn't already +# exist and verifies write access to the user under which +# ``glance-api`` runs. If the write access isn't available, a +# ``BadStoreConfiguration`` exception is raised and the filesystem +# store may not be available for adding new images. +# +# NOTE: This directory is used only when filesystem store is used as a +# storage backend. Either ``filesystem_store_datadir`` or +# ``filesystem_store_datadirs`` option must be specified in +# ``glance-api.conf``. If both options are specified, a +# ``BadStoreConfiguration`` will be raised and the filesystem store +# may not be available for adding new images. +# +# Possible values: +# * A valid path to a directory +# +# Related options: +# * ``filesystem_store_datadirs`` +# * ``filesystem_store_file_perm`` +# +# (string value) +#filesystem_store_datadir = /var/lib/glance/images + +# +# List of directories and their priorities to which the filesystem +# backend store writes images. +# +# The filesystem store can be configured to store images in multiple +# directories as opposed to using a single directory specified by the +# ``filesystem_store_datadir`` configuration option. When using +# multiple directories, each directory can be given an optional +# priority to specify the preference order in which they should +# be used. Priority is an integer that is concatenated to the +# directory path with a colon where a higher value indicates higher +# priority. When two directories have the same priority, the directory +# with most free space is used. When no priority is specified, it +# defaults to zero. +# +# More information on configuring filesystem store with multiple store +# directories can be found at +# http://docs.openstack.org/developer/glance/configuring.html +# +# NOTE: This directory is used only when filesystem store is used as a +# storage backend. Either ``filesystem_store_datadir`` or +# ``filesystem_store_datadirs`` option must be specified in +# ``glance-api.conf``. If both options are specified, a +# ``BadStoreConfiguration`` will be raised and the filesystem store +# may not be available for adding new images. +# +# Possible values: +# * List of strings of the following form: +# * ``:`` +# +# Related options: +# * ``filesystem_store_datadir`` +# * ``filesystem_store_file_perm`` +# +# (multi valued) +#filesystem_store_datadirs = + +# +# Filesystem store metadata file. +# +# The path to a file which contains the metadata to be returned with +# any location associated with the filesystem store. The file must +# contain a valid JSON object. The object should contain the keys +# ``id`` and ``mountpoint``. The value for both keys should be a +# string. +# +# Possible values: +# * A valid path to the store metadata file +# +# Related options: +# * None +# +# (string value) +#filesystem_store_metadata_file = + +# +# File access permissions for the image files. +# +# Set the intended file access permissions for image data. This provides +# a way to enable other services, e.g. Nova, to consume images directly +# from the filesystem store. The users running the services that are +# intended to be given access to could be made a member of the group +# that owns the files created. Assigning a value less then or equal to +# zero for this configuration option signifies that no changes be made +# to the default permissions. This value will be decoded as an octal +# digit. +# +# For more information, please refer the documentation at +# http://docs.openstack.org/developer/glance/configuring.html +# +# Possible values: +# * A valid file access permission +# * Zero +# * Any negative integer +# +# Related options: +# * None +# +# (integer value) +#filesystem_store_file_perm = 0 + +# +# Path to the CA bundle file. +# +# This configuration option enables the operator to use a custom +# Certificate Authority file to verify the remote server certificate. If +# this option is set, the ``https_insecure`` option will be ignored and +# the CA file specified will be used to authenticate the server +# certificate and establish a secure connection to the server. +# +# Possible values: +# * A valid path to a CA file +# +# Related options: +# * https_insecure +# +# (string value) +#https_ca_certificates_file = + +# +# Set verification of the remote server certificate. +# +# This configuration option takes in a boolean value to determine +# whether or not to verify the remote server certificate. If set to +# True, the remote server certificate is not verified. If the option is +# set to False, then the default CA truststore is used for verification. +# +# This option is ignored if ``https_ca_certificates_file`` is set. +# The remote server certificate will then be verified using the file +# specified using the ``https_ca_certificates_file`` option. +# +# Possible values: +# * True +# * False +# +# Related options: +# * https_ca_certificates_file +# +# (boolean value) +#https_insecure = true + +# +# The http/https proxy information to be used to connect to the remote +# server. +# +# This configuration option specifies the http/https proxy information +# that should be used to connect to the remote server. The proxy +# information should be a key value pair of the scheme and proxy, for +# example, http:10.0.0.1:3128. You can also specify proxies for multiple +# schemes by separating the key value pairs with a comma, for example, +# http:10.0.0.1:3128, https:10.0.0.1:1080. +# +# Possible values: +# * A comma separated list of scheme:proxy pairs as described above +# +# Related options: +# * None +# +# (dict value) +#http_proxy_information = + +# +# Size, in megabytes, to chunk RADOS images into. +# +# Provide an integer value representing the size in megabytes to chunk +# Glance images into. The default chunk size is 8 megabytes. For optimal +# performance, the value should be a power of two. +# +# When Ceph's RBD object storage system is used as the storage backend +# for storing Glance images, the images are chunked into objects of the +# size set using this option. These chunked objects are then stored +# across the distributed block data store to use for Glance. +# +# Possible Values: +# * Any positive integer value +# +# Related options: +# * None +# +# (integer value) +# Minimum value: 1 +#rbd_store_chunk_size = 8 + +# +# RADOS pool in which images are stored. +# +# When RBD is used as the storage backend for storing Glance images, the +# images are stored by means of logical grouping of the objects (chunks +# of images) into a ``pool``. Each pool is defined with the number of +# placement groups it can contain. The default pool that is used is +# 'images'. +# +# More information on the RBD storage backend can be found here: +# http://ceph.com/planet/how-data-is-stored-in-ceph-cluster/ +# +# Possible Values: +# * A valid pool name +# +# Related options: +# * None +# +# (string value) +#rbd_store_pool = images + +# +# RADOS user to authenticate as. +# +# This configuration option takes in the RADOS user to authenticate as. +# This is only needed when RADOS authentication is enabled and is +# applicable only if the user is using Cephx authentication. If the +# value for this option is not set by the user or is set to None, a +# default value will be chosen, which will be based on the client. +# section in rbd_store_ceph_conf. +# +# Possible Values: +# * A valid RADOS user +# +# Related options: +# * rbd_store_ceph_conf +# +# (string value) +#rbd_store_user = + +# +# Ceph configuration file path. +# +# This configuration option takes in the path to the Ceph configuration +# file to be used. If the value for this option is not set by the user +# or is set to None, librados will locate the default configuration file +# which is located at /etc/ceph/ceph.conf. If using Cephx +# authentication, this file should include a reference to the right +# keyring in a client. section +# +# Possible Values: +# * A valid path to a configuration file +# +# Related options: +# * rbd_store_user +# +# (string value) +#rbd_store_ceph_conf = /etc/ceph/ceph.conf + +# +# Timeout value for connecting to Ceph cluster. +# +# This configuration option takes in the timeout value in seconds used +# when connecting to the Ceph cluster i.e. it sets the time to wait for +# glance-api before closing the connection. This prevents glance-api +# hangups during the connection to RBD. If the value for this option +# is set to less than or equal to 0, no timeout is set and the default +# librados value is used. +# +# Possible Values: +# * Any integer value +# +# Related options: +# * None +# +# (integer value) +#rados_connect_timeout = 0 + +# +# Chunk size for images to be stored in Sheepdog data store. +# +# Provide an integer value representing the size in mebibyte +# (1048576 bytes) to chunk Glance images into. The default +# chunk size is 64 mebibytes. +# +# When using Sheepdog distributed storage system, the images are +# chunked into objects of this size and then stored across the +# distributed data store to use for Glance. +# +# Chunk sizes, if a power of two, help avoid fragmentation and +# enable improved performance. +# +# Possible values: +# * Positive integer value representing size in mebibytes. +# +# Related Options: +# * None +# +# (integer value) +# Minimum value: 1 +#sheepdog_store_chunk_size = 64 + +# +# Port number on which the sheep daemon will listen. +# +# Provide an integer value representing a valid port number on +# which you want the Sheepdog daemon to listen on. The default +# port is 7000. +# +# The Sheepdog daemon, also called 'sheep', manages the storage +# in the distributed cluster by writing objects across the storage +# network. It identifies and acts on the messages it receives on +# the port number set using ``sheepdog_store_port`` option to store +# chunks of Glance images. +# +# Possible values: +# * A valid port number (0 to 65535) +# +# Related Options: +# * sheepdog_store_address +# +# (port value) +# Minimum value: 0 +# Maximum value: 65535 +#sheepdog_store_port = 7000 + +# +# Address to bind the Sheepdog daemon to. +# +# Provide a string value representing the address to bind the +# Sheepdog daemon to. The default address set for the 'sheep' +# is 127.0.0.1. +# +# The Sheepdog daemon, also called 'sheep', manages the storage +# in the distributed cluster by writing objects across the storage +# network. It identifies and acts on the messages directed to the +# address set using ``sheepdog_store_address`` option to store +# chunks of Glance images. +# +# Possible values: +# * A valid IPv4 address +# * A valid IPv6 address +# * A valid hostname +# +# Related Options: +# * sheepdog_store_port +# +# (string value) +#sheepdog_store_address = 127.0.0.1 + # # Set verification of the server certificate. # @@ -2420,6 +2242,184 @@ # (string value) #swift_store_config_file = +# +# Address of the ESX/ESXi or vCenter Server target system. +# +# This configuration option sets the address of the ESX/ESXi or vCenter +# Server target system. This option is required when using the VMware +# storage backend. The address can contain an IP address (127.0.0.1) or +# a DNS name (www.my-domain.com). +# +# Possible Values: +# * A valid IPv4 or IPv6 address +# * A valid DNS name +# +# Related options: +# * vmware_server_username +# * vmware_server_password +# +# (string value) +#vmware_server_host = 127.0.0.1 + +# +# Server username. +# +# This configuration option takes the username for authenticating with +# the VMware ESX/ESXi or vCenter Server. This option is required when +# using the VMware storage backend. +# +# Possible Values: +# * Any string that is the username for a user with appropriate +# privileges +# +# Related options: +# * vmware_server_host +# * vmware_server_password +# +# (string value) +#vmware_server_username = root + +# +# Server password. +# +# This configuration option takes the password for authenticating with +# the VMware ESX/ESXi or vCenter Server. This option is required when +# using the VMware storage backend. +# +# Possible Values: +# * Any string that is a password corresponding to the username +# specified using the "vmware_server_username" option +# +# Related options: +# * vmware_server_host +# * vmware_server_username +# +# (string value) +#vmware_server_password = vmware + +# +# The number of VMware API retries. +# +# This configuration option specifies the number of times the VMware +# ESX/VC server API must be retried upon connection related issues or +# server API call overload. It is not possible to specify 'retry +# forever'. +# +# Possible Values: +# * Any positive integer value +# +# Related options: +# * None +# +# (integer value) +# Minimum value: 1 +#vmware_api_retry_count = 10 + +# +# Interval in seconds used for polling remote tasks invoked on VMware +# ESX/VC server. +# +# This configuration option takes in the sleep time in seconds for polling an +# on-going async task as part of the VMWare ESX/VC server API call. +# +# Possible Values: +# * Any positive integer value +# +# Related options: +# * None +# +# (integer value) +# Minimum value: 1 +#vmware_task_poll_interval = 5 + +# +# The directory where the glance images will be stored in the datastore. +# +# This configuration option specifies the path to the directory where the +# glance images will be stored in the VMware datastore. If this option +# is not set, the default directory where the glance images are stored +# is openstack_glance. +# +# Possible Values: +# * Any string that is a valid path to a directory +# +# Related options: +# * None +# +# (string value) +#vmware_store_image_dir = /openstack_glance + +# +# Set verification of the ESX/vCenter server certificate. +# +# This configuration option takes a boolean value to determine +# whether or not to verify the ESX/vCenter server certificate. If this +# option is set to True, the ESX/vCenter server certificate is not +# verified. If this option is set to False, then the default CA +# truststore is used for verification. +# +# This option is ignored if the "vmware_ca_file" option is set. In that +# case, the ESX/vCenter server certificate will then be verified using +# the file specified using the "vmware_ca_file" option . +# +# Possible Values: +# * True +# * False +# +# Related options: +# * vmware_ca_file +# +# (boolean value) +# Deprecated group/name - [glance_store]/vmware_api_insecure +#vmware_insecure = false + +# +# Absolute path to the CA bundle file. +# +# This configuration option enables the operator to use a custom +# Cerificate Authority File to verify the ESX/vCenter certificate. +# +# If this option is set, the "vmware_insecure" option will be ignored +# and the CA file specified will be used to authenticate the ESX/vCenter +# server certificate and establish a secure connection to the server. +# +# Possible Values: +# * Any string that is a valid absolute path to a CA file +# +# Related options: +# * vmware_insecure +# +# (string value) +#vmware_ca_file = /etc/ssl/certs/ca-certificates.crt + +# +# The datastores where the image can be stored. +# +# This configuration option specifies the datastores where the image can +# be stored in the VMWare store backend. This option may be specified +# multiple times for specifying multiple datastores. The datastore name +# should be specified after its datacenter path, separated by ":". An +# optional weight may be given after the datastore name, separated again +# by ":" to specify the priority. Thus, the required format becomes +# ::. +# +# When adding an image, the datastore with highest weight will be +# selected, unless there is not enough free space available in cases +# where the image size is already known. If no weight is given, it is +# assumed to be zero and the directory will be considered for selection +# last. If multiple datastores have the same weight, then the one with +# the most free space available is selected. +# +# Possible Values: +# * Any string of the format: +# :: +# +# Related options: +# * None +# +# (multi valued) +#vmware_datastores = + [oslo_concurrency]