87a59ae52b
Change-Id: Ied1902018ded20b35bfa69200a1faee34fb3a4d6
4747 lines
156 KiB
Plaintext
4747 lines
156 KiB
Plaintext
[DEFAULT]
|
|
|
|
#
|
|
# From glance.api
|
|
#
|
|
|
|
# DEPRECATED:
|
|
# Set the image owner to tenant or the authenticated user.
|
|
#
|
|
# Assign a boolean value to determine the owner of an image. When set to
|
|
# True, the owner of the image is the tenant. When set to False, the
|
|
# owner of the image will be the authenticated user issuing the request.
|
|
# Setting it to False makes the image private to the associated user and
|
|
# sharing with other users within the same tenant (or "project")
|
|
# requires explicit image sharing via image membership.
|
|
#
|
|
# Possible values:
|
|
# * True
|
|
# * False
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (boolean value)
|
|
# This option is deprecated for removal since Rocky.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason:
|
|
# The non-default setting for this option misaligns Glance with other
|
|
# OpenStack services with respect to resource ownership. Further, surveys
|
|
# indicate that this option is not used by operators. The option will be
|
|
# removed early in the 'S' development cycle following the standard OpenStack
|
|
# deprecation policy. As the option is not in wide use, no migration path is
|
|
# proposed.
|
|
#owner_is_tenant = true
|
|
|
|
#
|
|
# Role used to identify an authenticated user as administrator.
|
|
#
|
|
# Provide a string value representing a Keystone role to identify an
|
|
# administrative user. Users with this role will be granted
|
|
# administrative privileges. The default value for this option is
|
|
# 'admin'.
|
|
#
|
|
# Possible values:
|
|
# * A string value which is a valid Keystone role
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
#admin_role = admin
|
|
|
|
#
|
|
# Allow limited access to unauthenticated users.
|
|
#
|
|
# Assign a boolean to determine API access for unathenticated
|
|
# users. When set to False, the API cannot be accessed by
|
|
# unauthenticated users. When set to True, unauthenticated users can
|
|
# access the API with read-only privileges. This however only applies
|
|
# when using ContextMiddleware.
|
|
#
|
|
# Possible values:
|
|
# * True
|
|
# * False
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (boolean value)
|
|
#allow_anonymous_access = false
|
|
|
|
#
|
|
# Limit the request ID length.
|
|
#
|
|
# Provide an integer value to limit the length of the request ID to
|
|
# the specified length. The default value is 64. Users can change this
|
|
# to any ineteger value between 0 and 16384 however keeping in mind that
|
|
# a larger value may flood the logs.
|
|
#
|
|
# Possible values:
|
|
# * Integer value between 0 and 16384
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 0
|
|
#max_request_id_length = 64
|
|
|
|
#
|
|
# Public url endpoint to use for Glance versions response.
|
|
#
|
|
# This is the public url endpoint that will appear in the Glance
|
|
# "versions" response. If no value is specified, the endpoint that is
|
|
# displayed in the version's response is that of the host running the
|
|
# API service. Change the endpoint to represent the proxy URL if the
|
|
# API service is running behind a proxy. If the service is running
|
|
# behind a load balancer, add the load balancer's URL for this value.
|
|
#
|
|
# Possible values:
|
|
# * None
|
|
# * Proxy URL
|
|
# * Load balancer URL
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
#public_endpoint = <None>
|
|
|
|
#
|
|
# Allow users to add additional/custom properties to images.
|
|
#
|
|
# Glance defines a standard set of properties (in its schema) that
|
|
# appear on every image. These properties are also known as
|
|
# ``base properties``. In addition to these properties, Glance
|
|
# allows users to add custom properties to images. These are known
|
|
# as ``additional properties``.
|
|
#
|
|
# By default, this configuration option is set to ``True`` and users
|
|
# are allowed to add additional properties. The number of additional
|
|
# properties that can be added to an image can be controlled via
|
|
# ``image_property_quota`` configuration option.
|
|
#
|
|
# Possible values:
|
|
# * True
|
|
# * False
|
|
#
|
|
# Related options:
|
|
# * image_property_quota
|
|
#
|
|
# (boolean value)
|
|
#allow_additional_image_properties = true
|
|
|
|
# "
|
|
# Secure hashing algorithm used for computing the 'os_hash_value' property.
|
|
#
|
|
# This option configures the Glance "multihash", which consists of two
|
|
# image properties: the 'os_hash_algo' and the 'os_hash_value'. The
|
|
# 'os_hash_algo' will be populated by the value of this configuration
|
|
# option, and the 'os_hash_value' will be populated by the hexdigest computed
|
|
# when the algorithm is applied to the uploaded or imported image data.
|
|
#
|
|
# The value must be a valid secure hash algorithm name recognized by the
|
|
# python 'hashlib' library. You can determine what these are by examining
|
|
# the 'hashlib.algorithms_available' data member of the version of the
|
|
# library being used in your Glance installation. For interoperability
|
|
# purposes, however, we recommend that you use the set of secure hash
|
|
# names supplied by the 'hashlib.algorithms_guaranteed' data member because
|
|
# those algorithms are guaranteed to be supported by the 'hashlib' library
|
|
# on all platforms. Thus, any image consumer using 'hashlib' locally should
|
|
# be able to verify the 'os_hash_value' of the image.
|
|
#
|
|
# The default value of 'sha512' is a performant secure hash algorithm.
|
|
#
|
|
# If this option is misconfigured, any attempts to store image data will fail.
|
|
# For that reason, we recommend using the default value.
|
|
#
|
|
# Possible values:
|
|
# * Any secure hash algorithm name recognized by the Python 'hashlib'
|
|
# library
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
#hashing_algorithm = sha512
|
|
|
|
#
|
|
# Maximum number of image members per image.
|
|
#
|
|
# This limits the maximum of users an image can be shared with. Any negative
|
|
# value is interpreted as unlimited.
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (integer value)
|
|
#image_member_quota = 128
|
|
|
|
#
|
|
# Maximum number of properties allowed on an image.
|
|
#
|
|
# This enforces an upper limit on the number of additional properties an image
|
|
# can have. Any negative value is interpreted as unlimited.
|
|
#
|
|
# NOTE: This won't have any impact if additional properties are disabled. Please
|
|
# refer to ``allow_additional_image_properties``.
|
|
#
|
|
# Related options:
|
|
# * ``allow_additional_image_properties``
|
|
#
|
|
# (integer value)
|
|
#image_property_quota = 128
|
|
|
|
#
|
|
# Maximum number of tags allowed on an image.
|
|
#
|
|
# Any negative value is interpreted as unlimited.
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (integer value)
|
|
#image_tag_quota = 128
|
|
|
|
#
|
|
# Maximum number of locations allowed on an image.
|
|
#
|
|
# Any negative value is interpreted as unlimited.
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (integer value)
|
|
#image_location_quota = 10
|
|
|
|
# DEPRECATED:
|
|
# Python module path of data access API.
|
|
#
|
|
# Specifies the path to the API to use for accessing the data model.
|
|
# This option determines how the image catalog data will be accessed.
|
|
#
|
|
# Possible values:
|
|
# * glance.db.sqlalchemy.api
|
|
# * glance.db.registry.api
|
|
# * glance.db.simple.api
|
|
#
|
|
# If this option is set to ``glance.db.sqlalchemy.api`` then the image
|
|
# catalog data is stored in and read from the database via the
|
|
# SQLAlchemy Core and ORM APIs.
|
|
#
|
|
# Setting this option to ``glance.db.registry.api`` will force all
|
|
# database access requests to be routed through the Registry service.
|
|
# This avoids data access from the Glance API nodes for an added layer
|
|
# of security, scalability and manageability.
|
|
#
|
|
# NOTE: In v2 OpenStack Images API, the registry service is optional.
|
|
# In order to use the Registry API in v2, the option
|
|
# ``enable_v2_registry`` must be set to ``True``.
|
|
#
|
|
# Finally, when this configuration option is set to
|
|
# ``glance.db.simple.api``, image catalog data is stored in and read
|
|
# from an in-memory data structure. This is primarily used for testing.
|
|
#
|
|
# Related options:
|
|
# * enable_v2_api
|
|
# * enable_v2_registry
|
|
#
|
|
# (string value)
|
|
# This option is deprecated for removal since Queens.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason:
|
|
# Glance registry service is deprecated for removal.
|
|
#
|
|
# More information can be found from the spec:
|
|
# http://specs.openstack.org/openstack/glance-specs/specs/queens/approved/glance
|
|
# /deprecate-registry.html
|
|
#data_api = glance.db.sqlalchemy.api
|
|
|
|
#
|
|
# The default number of results to return for a request.
|
|
#
|
|
# Responses to certain API requests, like list images, may return
|
|
# multiple items. The number of results returned can be explicitly
|
|
# controlled by specifying the ``limit`` parameter in the API request.
|
|
# However, if a ``limit`` parameter is not specified, this
|
|
# configuration value will be used as the default number of results to
|
|
# be returned for any API request.
|
|
#
|
|
# NOTES:
|
|
# * The value of this configuration option may not be greater than
|
|
# the value specified by ``api_limit_max``.
|
|
# * Setting this to a very large value may slow down database
|
|
# queries and increase response times. Setting this to a
|
|
# very low value may result in poor user experience.
|
|
#
|
|
# Possible values:
|
|
# * Any positive integer
|
|
#
|
|
# Related options:
|
|
# * api_limit_max
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 1
|
|
#limit_param_default = 25
|
|
|
|
#
|
|
# Maximum number of results that could be returned by a request.
|
|
#
|
|
# As described in the help text of ``limit_param_default``, some
|
|
# requests may return multiple results. The number of results to be
|
|
# returned are governed either by the ``limit`` parameter in the
|
|
# request or the ``limit_param_default`` configuration option.
|
|
# The value in either case, can't be greater than the absolute maximum
|
|
# defined by this configuration option. Anything greater than this
|
|
# value is trimmed down to the maximum value defined here.
|
|
#
|
|
# NOTE: Setting this to a very large value may slow down database
|
|
# queries and increase response times. Setting this to a
|
|
# very low value may result in poor user experience.
|
|
#
|
|
# Possible values:
|
|
# * Any positive integer
|
|
#
|
|
# Related options:
|
|
# * limit_param_default
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 1
|
|
#api_limit_max = 1000
|
|
|
|
#
|
|
# Show direct image location when returning an image.
|
|
#
|
|
# This configuration option indicates whether to show the direct image
|
|
# location when returning image details to the user. The direct image
|
|
# location is where the image data is stored in backend storage. This
|
|
# image location is shown under the image property ``direct_url``.
|
|
#
|
|
# When multiple image locations exist for an image, the best location
|
|
# is displayed based on the location strategy indicated by the
|
|
# configuration option ``location_strategy``.
|
|
#
|
|
# NOTES:
|
|
# * Revealing image locations can present a GRAVE SECURITY RISK as
|
|
# image locations can sometimes include credentials. Hence, this
|
|
# is set to ``False`` by default. Set this to ``True`` with
|
|
# EXTREME CAUTION and ONLY IF you know what you are doing!
|
|
# * If an operator wishes to avoid showing any image location(s)
|
|
# to the user, then both this option and
|
|
# ``show_multiple_locations`` MUST be set to ``False``.
|
|
#
|
|
# Possible values:
|
|
# * True
|
|
# * False
|
|
#
|
|
# Related options:
|
|
# * show_multiple_locations
|
|
# * location_strategy
|
|
#
|
|
# (boolean value)
|
|
#show_image_direct_url = false
|
|
|
|
# DEPRECATED:
|
|
# Show all image locations when returning an image.
|
|
#
|
|
# This configuration option indicates whether to show all the image
|
|
# locations when returning image details to the user. When multiple
|
|
# image locations exist for an image, the locations are ordered based
|
|
# on the location strategy indicated by the configuration opt
|
|
# ``location_strategy``. The image locations are shown under the
|
|
# image property ``locations``.
|
|
#
|
|
# NOTES:
|
|
# * Revealing image locations can present a GRAVE SECURITY RISK as
|
|
# image locations can sometimes include credentials. Hence, this
|
|
# is set to ``False`` by default. Set this to ``True`` with
|
|
# EXTREME CAUTION and ONLY IF you know what you are doing!
|
|
# * If an operator wishes to avoid showing any image location(s)
|
|
# to the user, then both this option and
|
|
# ``show_image_direct_url`` MUST be set to ``False``.
|
|
#
|
|
# Possible values:
|
|
# * True
|
|
# * False
|
|
#
|
|
# Related options:
|
|
# * show_image_direct_url
|
|
# * location_strategy
|
|
#
|
|
# (boolean value)
|
|
# This option is deprecated for removal since Newton.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: This option will be removed in the Pike release or later because the
|
|
# same functionality can be achieved with greater granularity by using policies.
|
|
# Please see the Newton release notes for more information.
|
|
#show_multiple_locations = false
|
|
|
|
#
|
|
# Maximum size of image a user can upload in bytes.
|
|
#
|
|
# An image upload greater than the size mentioned here would result
|
|
# in an image creation failure. This configuration option defaults to
|
|
# 1099511627776 bytes (1 TiB).
|
|
#
|
|
# NOTES:
|
|
# * This value should only be increased after careful
|
|
# consideration and must be set less than or equal to
|
|
# 8 EiB (9223372036854775808).
|
|
# * This value must be set with careful consideration of the
|
|
# backend storage capacity. Setting this to a very low value
|
|
# may result in a large number of image failures. And, setting
|
|
# this to a very large value may result in faster consumption
|
|
# of storage. Hence, this must be set according to the nature of
|
|
# images created and storage capacity available.
|
|
#
|
|
# Possible values:
|
|
# * Any positive number less than or equal to 9223372036854775808
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 1
|
|
# Maximum value: 9223372036854775808
|
|
#image_size_cap = 1099511627776
|
|
|
|
#
|
|
# Maximum amount of image storage per tenant.
|
|
#
|
|
# This enforces an upper limit on the cumulative storage consumed by all images
|
|
# of a tenant across all stores. This is a per-tenant limit.
|
|
#
|
|
# The default unit for this configuration option is Bytes. However, storage
|
|
# units can be specified using case-sensitive literals ``B``, ``KB``, ``MB``,
|
|
# ``GB`` and ``TB`` representing Bytes, KiloBytes, MegaBytes, GigaBytes and
|
|
# TeraBytes respectively. Note that there should not be any space between the
|
|
# value and unit. Value ``0`` signifies no quota enforcement. Negative values
|
|
# are invalid and result in errors.
|
|
#
|
|
# Possible values:
|
|
# * A string that is a valid concatenation of a non-negative integer
|
|
# representing the storage value and an optional string literal
|
|
# representing storage units as mentioned above.
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
#user_storage_quota = 0
|
|
|
|
#
|
|
# Deploy the v2 OpenStack Images API.
|
|
#
|
|
# When this option is set to ``True``, Glance service will respond
|
|
# to requests on registered endpoints conforming to the v2 OpenStack
|
|
# Images API.
|
|
#
|
|
# NOTES:
|
|
# * If this option is disabled, then the ``enable_v2_registry``
|
|
# option, which is enabled by default, is also recommended
|
|
# to be disabled.
|
|
#
|
|
# Possible values:
|
|
# * True
|
|
# * False
|
|
#
|
|
# Related options:
|
|
# * enable_v2_registry
|
|
#
|
|
# (boolean value)
|
|
#enable_v2_api = true
|
|
|
|
#
|
|
# DEPRECATED FOR REMOVAL
|
|
# (boolean value)
|
|
#enable_v1_registry = true
|
|
|
|
# DEPRECATED:
|
|
# Deploy the v2 API Registry service.
|
|
#
|
|
# When this option is set to ``True``, the Registry service
|
|
# will be enabled in Glance for v2 API requests.
|
|
#
|
|
# NOTES:
|
|
# * Use of Registry is optional in v2 API, so this option
|
|
# must only be enabled if both ``enable_v2_api`` is set to
|
|
# ``True`` and the ``data_api`` option is set to
|
|
# ``glance.db.registry.api``.
|
|
#
|
|
# * If deploying only the v1 OpenStack Images API, this option,
|
|
# which is enabled by default, should be disabled.
|
|
#
|
|
# Possible values:
|
|
# * True
|
|
# * False
|
|
#
|
|
# Related options:
|
|
# * enable_v2_api
|
|
# * data_api
|
|
#
|
|
# (boolean value)
|
|
# This option is deprecated for removal since Queens.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason:
|
|
# Glance registry service is deprecated for removal.
|
|
#
|
|
# More information can be found from the spec:
|
|
# http://specs.openstack.org/openstack/glance-specs/specs/queens/approved/glance
|
|
# /deprecate-registry.html
|
|
#enable_v2_registry = true
|
|
|
|
#
|
|
# Host address of the pydev server.
|
|
#
|
|
# Provide a string value representing the hostname or IP of the
|
|
# pydev server to use for debugging. The pydev server listens for
|
|
# debug connections on this address, facilitating remote debugging
|
|
# in Glance.
|
|
#
|
|
# Possible values:
|
|
# * Valid hostname
|
|
# * Valid IP address
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (host address value)
|
|
#pydev_worker_debug_host = localhost
|
|
|
|
#
|
|
# Port number that the pydev server will listen on.
|
|
#
|
|
# Provide a port number to bind the pydev server to. The pydev
|
|
# process accepts debug connections on this port and facilitates
|
|
# remote debugging in Glance.
|
|
#
|
|
# Possible values:
|
|
# * A valid port number
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (port value)
|
|
# Minimum value: 0
|
|
# Maximum value: 65535
|
|
#pydev_worker_debug_port = 5678
|
|
|
|
#
|
|
# AES key for encrypting store location metadata.
|
|
#
|
|
# Provide a string value representing the AES cipher to use for
|
|
# encrypting Glance store metadata.
|
|
#
|
|
# NOTE: The AES key to use must be set to a random string of length
|
|
# 16, 24 or 32 bytes.
|
|
#
|
|
# Possible values:
|
|
# * String value representing a valid AES key
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
#metadata_encryption_key = <None>
|
|
|
|
#
|
|
# Digest algorithm to use for digital signature.
|
|
#
|
|
# Provide a string value representing the digest algorithm to
|
|
# use for generating digital signatures. By default, ``sha256``
|
|
# is used.
|
|
#
|
|
# To get a list of the available algorithms supported by the version
|
|
# of OpenSSL on your platform, run the command:
|
|
# ``openssl list-message-digest-algorithms``.
|
|
# Examples are 'sha1', 'sha256', and 'sha512'.
|
|
#
|
|
# NOTE: ``digest_algorithm`` is not related to Glance's image signing
|
|
# and verification. It is only used to sign the universally unique
|
|
# identifier (UUID) as a part of the certificate file and key file
|
|
# validation.
|
|
#
|
|
# Possible values:
|
|
# * An OpenSSL message digest algorithm identifier
|
|
#
|
|
# Relation options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
#digest_algorithm = sha256
|
|
|
|
#
|
|
# The URL provides location where the temporary data will be stored
|
|
#
|
|
# This option is for Glance internal use only. Glance will save the
|
|
# image data uploaded by the user to 'staging' endpoint during the
|
|
# image import process.
|
|
#
|
|
# This option does not change the 'staging' API endpoint by any means.
|
|
#
|
|
# NOTE: It is discouraged to use same path as [task]/work_dir
|
|
#
|
|
# NOTE: 'file://<absolute-directory-path>' is the only option
|
|
# api_image_import flow will support for now.
|
|
#
|
|
# NOTE: The staging path must be on shared filesystem available to all
|
|
# Glance API nodes.
|
|
#
|
|
# Possible values:
|
|
# * String starting with 'file://' followed by absolute FS path
|
|
#
|
|
# Related options:
|
|
# * [task]/work_dir
|
|
#
|
|
# (string value)
|
|
#node_staging_uri = file:///tmp/staging/
|
|
|
|
#
|
|
# List of enabled Image Import Methods
|
|
#
|
|
# Both 'glance-direct' and 'web-download' are enabled by default.
|
|
#
|
|
# Related options:
|
|
# * [DEFAULT]/node_staging_uri (list value)
|
|
#enabled_import_methods = [glance-direct,web-download]
|
|
|
|
#
|
|
# Strategy to determine the preference order of image locations.
|
|
#
|
|
# This configuration option indicates the strategy to determine
|
|
# the order in which an image's locations must be accessed to
|
|
# serve the image's data. Glance then retrieves the image data
|
|
# from the first responsive active location it finds in this list.
|
|
#
|
|
# This option takes one of two possible values ``location_order``
|
|
# and ``store_type``. The default value is ``location_order``,
|
|
# which suggests that image data be served by using locations in
|
|
# the order they are stored in Glance. The ``store_type`` value
|
|
# sets the image location preference based on the order in which
|
|
# the storage backends are listed as a comma separated list for
|
|
# the configuration option ``store_type_preference``.
|
|
#
|
|
# Possible values:
|
|
# * location_order
|
|
# * store_type
|
|
#
|
|
# Related options:
|
|
# * store_type_preference
|
|
#
|
|
# (string value)
|
|
# Possible values:
|
|
# location_order - <No description provided>
|
|
# store_type - <No description provided>
|
|
#location_strategy = location_order
|
|
|
|
#
|
|
# The location of the property protection file.
|
|
#
|
|
# Provide a valid path to the property protection file which contains
|
|
# the rules for property protections and the roles/policies associated
|
|
# with them.
|
|
#
|
|
# A property protection file, when set, restricts the Glance image
|
|
# properties to be created, read, updated and/or deleted by a specific
|
|
# set of users that are identified by either roles or policies.
|
|
# If this configuration option is not set, by default, property
|
|
# protections won't be enforced. If a value is specified and the file
|
|
# is not found, the glance-api service will fail to start.
|
|
# More information on property protections can be found at:
|
|
# https://docs.openstack.org/glance/latest/admin/property-protections.html
|
|
#
|
|
# Possible values:
|
|
# * Empty string
|
|
# * Valid path to the property protection configuration file
|
|
#
|
|
# Related options:
|
|
# * property_protection_rule_format
|
|
#
|
|
# (string value)
|
|
#property_protection_file = <None>
|
|
|
|
#
|
|
# Rule format for property protection.
|
|
#
|
|
# Provide the desired way to set property protection on Glance
|
|
# image properties. The two permissible values are ``roles``
|
|
# and ``policies``. The default value is ``roles``.
|
|
#
|
|
# If the value is ``roles``, the property protection file must
|
|
# contain a comma separated list of user roles indicating
|
|
# permissions for each of the CRUD operations on each property
|
|
# being protected. If set to ``policies``, a policy defined in
|
|
# policy.json is used to express property protections for each
|
|
# of the CRUD operations. Examples of how property protections
|
|
# are enforced based on ``roles`` or ``policies`` can be found at:
|
|
# https://docs.openstack.org/glance/latest/admin/property-
|
|
# protections.html#examples
|
|
#
|
|
# Possible values:
|
|
# * roles
|
|
# * policies
|
|
#
|
|
# Related options:
|
|
# * property_protection_file
|
|
#
|
|
# (string value)
|
|
# Possible values:
|
|
# roles - <No description provided>
|
|
# policies - <No description provided>
|
|
#property_protection_rule_format = roles
|
|
|
|
#
|
|
# List of allowed exception modules to handle RPC exceptions.
|
|
#
|
|
# Provide a comma separated list of modules whose exceptions are
|
|
# permitted to be recreated upon receiving exception data via an RPC
|
|
# call made to Glance. The default list includes
|
|
# ``glance.common.exception``, ``builtins``, and ``exceptions``.
|
|
#
|
|
# The RPC protocol permits interaction with Glance via calls across a
|
|
# network or within the same system. Including a list of exception
|
|
# namespaces with this option enables RPC to propagate the exceptions
|
|
# back to the users.
|
|
#
|
|
# Possible values:
|
|
# * A comma separated list of valid exception modules
|
|
#
|
|
# Related options:
|
|
# * None
|
|
# (list value)
|
|
#allowed_rpc_exception_modules = glance.common.exception,builtins,exceptions
|
|
|
|
#
|
|
# IP address to bind the glance servers to.
|
|
#
|
|
# Provide an IP address to bind the glance server to. The default
|
|
# value is ``0.0.0.0``.
|
|
#
|
|
# Edit this option to enable the server to listen on one particular
|
|
# IP address on the network card. This facilitates selection of a
|
|
# particular network interface for the server.
|
|
#
|
|
# Possible values:
|
|
# * A valid IPv4 address
|
|
# * A valid IPv6 address
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (host address value)
|
|
#bind_host = 0.0.0.0
|
|
|
|
#
|
|
# Port number on which the server will listen.
|
|
#
|
|
# Provide a valid port number to bind the server's socket to. This
|
|
# port is then set to identify processes and forward network messages
|
|
# that arrive at the server. The default bind_port value for the API
|
|
# server is 9292 and for the registry server is 9191.
|
|
#
|
|
# Possible values:
|
|
# * A valid port number (0 to 65535)
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (port value)
|
|
# Minimum value: 0
|
|
# Maximum value: 65535
|
|
#bind_port = <None>
|
|
|
|
#
|
|
# Number of Glance worker processes to start.
|
|
#
|
|
# Provide a non-negative integer value to set the number of child
|
|
# process workers to service requests. By default, the number of CPUs
|
|
# available is set as the value for ``workers`` limited to 8. For
|
|
# example if the processor count is 6, 6 workers will be used, if the
|
|
# processor count is 24 only 8 workers will be used. The limit will only
|
|
# apply to the default value, if 24 workers is configured, 24 is used.
|
|
#
|
|
# Each worker process is made to listen on the port set in the
|
|
# configuration file and contains a greenthread pool of size 1000.
|
|
#
|
|
# NOTE: Setting the number of workers to zero, triggers the creation
|
|
# of a single API process with a greenthread pool of size 1000.
|
|
#
|
|
# Possible values:
|
|
# * 0
|
|
# * Positive integer value (typically equal to the number of CPUs)
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 0
|
|
#workers = <None>
|
|
|
|
#
|
|
# Maximum line size of message headers.
|
|
#
|
|
# Provide an integer value representing a length to limit the size of
|
|
# message headers. The default value is 16384.
|
|
#
|
|
# NOTE: ``max_header_line`` may need to be increased when using large
|
|
# tokens (typically those generated by the Keystone v3 API with big
|
|
# service catalogs). However, it is to be kept in mind that larger
|
|
# values for ``max_header_line`` would flood the logs.
|
|
#
|
|
# Setting ``max_header_line`` to 0 sets no limit for the line size of
|
|
# message headers.
|
|
#
|
|
# Possible values:
|
|
# * 0
|
|
# * Positive integer
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 0
|
|
#max_header_line = 16384
|
|
|
|
#
|
|
# Set keep alive option for HTTP over TCP.
|
|
#
|
|
# Provide a boolean value to determine sending of keep alive packets.
|
|
# If set to ``False``, the server returns the header
|
|
# "Connection: close". If set to ``True``, the server returns a
|
|
# "Connection: Keep-Alive" in its responses. This enables retention of
|
|
# the same TCP connection for HTTP conversations instead of opening a
|
|
# new one with each new request.
|
|
#
|
|
# This option must be set to ``False`` if the client socket connection
|
|
# needs to be closed explicitly after the response is received and
|
|
# read successfully by the client.
|
|
#
|
|
# Possible values:
|
|
# * True
|
|
# * False
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (boolean value)
|
|
#http_keepalive = true
|
|
|
|
#
|
|
# Timeout for client connections' socket operations.
|
|
#
|
|
# Provide a valid integer value representing time in seconds to set
|
|
# the period of wait before an incoming connection can be closed. The
|
|
# default value is 900 seconds.
|
|
#
|
|
# The value zero implies wait forever.
|
|
#
|
|
# Possible values:
|
|
# * Zero
|
|
# * Positive integer
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 0
|
|
#client_socket_timeout = 900
|
|
|
|
#
|
|
# Set the number of incoming connection requests.
|
|
#
|
|
# Provide a positive integer value to limit the number of requests in
|
|
# the backlog queue. The default queue size is 4096.
|
|
#
|
|
# An incoming connection to a TCP listener socket is queued before a
|
|
# connection can be established with the server. Setting the backlog
|
|
# for a TCP socket ensures a limited queue size for incoming traffic.
|
|
#
|
|
# Possible values:
|
|
# * Positive integer
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 1
|
|
#backlog = 4096
|
|
|
|
#
|
|
# Set the wait time before a connection recheck.
|
|
#
|
|
# Provide a positive integer value representing time in seconds which
|
|
# is set as the idle wait time before a TCP keep alive packet can be
|
|
# sent to the host. The default value is 600 seconds.
|
|
#
|
|
# Setting ``tcp_keepidle`` helps verify at regular intervals that a
|
|
# connection is intact and prevents frequent TCP connection
|
|
# reestablishment.
|
|
#
|
|
# Possible values:
|
|
# * Positive integer value representing time in seconds
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 1
|
|
#tcp_keepidle = 600
|
|
|
|
#
|
|
# Absolute path to the CA file.
|
|
#
|
|
# Provide a string value representing a valid absolute path to
|
|
# the Certificate Authority file to use for client authentication.
|
|
#
|
|
# A CA file typically contains necessary trusted certificates to
|
|
# use for the client authentication. This is essential to ensure
|
|
# that a secure connection is established to the server via the
|
|
# internet.
|
|
#
|
|
# Possible values:
|
|
# * Valid absolute path to the CA file
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
#ca_file = /etc/ssl/cafile
|
|
|
|
#
|
|
# Absolute path to the certificate file.
|
|
#
|
|
# Provide a string value representing a valid absolute path to the
|
|
# certificate file which is required to start the API service
|
|
# securely.
|
|
#
|
|
# A certificate file typically is a public key container and includes
|
|
# the server's public key, server name, server information and the
|
|
# signature which was a result of the verification process using the
|
|
# CA certificate. This is required for a secure connection
|
|
# establishment.
|
|
#
|
|
# Possible values:
|
|
# * Valid absolute path to the certificate file
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
#cert_file = /etc/ssl/certs
|
|
|
|
#
|
|
# Absolute path to a private key file.
|
|
#
|
|
# Provide a string value representing a valid absolute path to a
|
|
# private key file which is required to establish the client-server
|
|
# connection.
|
|
#
|
|
# Possible values:
|
|
# * Absolute path to the private key file
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
#key_file = /etc/ssl/key/key-file.pem
|
|
|
|
# DEPRECATED: The HTTP header used to determine the scheme for the original
|
|
# request, even if it was removed by an SSL terminating proxy. Typical value is
|
|
# "HTTP_X_FORWARDED_PROTO". (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Use the http_proxy_to_wsgi middleware instead.
|
|
#secure_proxy_ssl_header = <None>
|
|
|
|
#
|
|
# The relative path to sqlite file database that will be used for image cache
|
|
# management.
|
|
#
|
|
# This is a relative path to the sqlite file database that tracks the age and
|
|
# usage statistics of image cache. The path is relative to image cache base
|
|
# directory, specified by the configuration option ``image_cache_dir``.
|
|
#
|
|
# This is a lightweight database with just one table.
|
|
#
|
|
# Possible values:
|
|
# * A valid relative path to sqlite file database
|
|
#
|
|
# Related options:
|
|
# * ``image_cache_dir``
|
|
#
|
|
# (string value)
|
|
#image_cache_sqlite_db = cache.db
|
|
|
|
#
|
|
# The driver to use for image cache management.
|
|
#
|
|
# This configuration option provides the flexibility to choose between the
|
|
# different image-cache drivers available. An image-cache driver is responsible
|
|
# for providing the essential functions of image-cache like write images to/read
|
|
# images from cache, track age and usage of cached images, provide a list of
|
|
# cached images, fetch size of the cache, queue images for caching and clean up
|
|
# the cache, etc.
|
|
#
|
|
# The essential functions of a driver are defined in the base class
|
|
# ``glance.image_cache.drivers.base.Driver``. All image-cache drivers (existing
|
|
# and prospective) must implement this interface. Currently available drivers
|
|
# are ``sqlite`` and ``xattr``. These drivers primarily differ in the way they
|
|
# store the information about cached images:
|
|
# * The ``sqlite`` driver uses a sqlite database (which sits on every glance
|
|
# node locally) to track the usage of cached images.
|
|
# * The ``xattr`` driver uses the extended attributes of files to store this
|
|
# information. It also requires a filesystem that sets ``atime`` on the
|
|
# files
|
|
# when accessed.
|
|
#
|
|
# Possible values:
|
|
# * sqlite
|
|
# * xattr
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
# Possible values:
|
|
# sqlite - <No description provided>
|
|
# xattr - <No description provided>
|
|
#image_cache_driver = sqlite
|
|
|
|
#
|
|
# The upper limit on cache size, in bytes, after which the cache-pruner cleans
|
|
# up the image cache.
|
|
#
|
|
# NOTE: This is just a threshold for cache-pruner to act upon. It is NOT a
|
|
# hard limit beyond which the image cache would never grow. In fact, depending
|
|
# on how often the cache-pruner runs and how quickly the cache fills, the image
|
|
# cache can far exceed the size specified here very easily. Hence, care must be
|
|
# taken to appropriately schedule the cache-pruner and in setting this limit.
|
|
#
|
|
# Glance caches an image when it is downloaded. Consequently, the size of the
|
|
# image cache grows over time as the number of downloads increases. To keep the
|
|
# cache size from becoming unmanageable, it is recommended to run the
|
|
# cache-pruner as a periodic task. When the cache pruner is kicked off, it
|
|
# compares the current size of image cache and triggers a cleanup if the image
|
|
# cache grew beyond the size specified here. After the cleanup, the size of
|
|
# cache is less than or equal to size specified here.
|
|
#
|
|
# Possible values:
|
|
# * Any non-negative integer
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 0
|
|
#image_cache_max_size = 10737418240
|
|
|
|
#
|
|
# The amount of time, in seconds, an incomplete image remains in the cache.
|
|
#
|
|
# Incomplete images are images for which download is in progress. Please see the
|
|
# description of configuration option ``image_cache_dir`` for more detail.
|
|
# Sometimes, due to various reasons, it is possible the download may hang and
|
|
# the incompletely downloaded image remains in the ``incomplete`` directory.
|
|
# This configuration option sets a time limit on how long the incomplete images
|
|
# should remain in the ``incomplete`` directory before they are cleaned up.
|
|
# Once an incomplete image spends more time than is specified here, it'll be
|
|
# removed by cache-cleaner on its next run.
|
|
#
|
|
# It is recommended to run cache-cleaner as a periodic task on the Glance API
|
|
# nodes to keep the incomplete images from occupying disk space.
|
|
#
|
|
# Possible values:
|
|
# * Any non-negative integer
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 0
|
|
#image_cache_stall_time = 86400
|
|
|
|
#
|
|
# Base directory for image cache.
|
|
#
|
|
# This is the location where image data is cached and served out of. All cached
|
|
# images are stored directly under this directory. This directory also contains
|
|
# three subdirectories, namely, ``incomplete``, ``invalid`` and ``queue``.
|
|
#
|
|
# The ``incomplete`` subdirectory is the staging area for downloading images. An
|
|
# image is first downloaded to this directory. When the image download is
|
|
# successful it is moved to the base directory. However, if the download fails,
|
|
# the partially downloaded image file is moved to the ``invalid`` subdirectory.
|
|
#
|
|
# The ``queue``subdirectory is used for queuing images for download. This is
|
|
# used primarily by the cache-prefetcher, which can be scheduled as a periodic
|
|
# task like cache-pruner and cache-cleaner, to cache images ahead of their
|
|
# usage.
|
|
# Upon receiving the request to cache an image, Glance touches a file in the
|
|
# ``queue`` directory with the image id as the file name. The cache-prefetcher,
|
|
# when running, polls for the files in ``queue`` directory and starts
|
|
# downloading them in the order they were created. When the download is
|
|
# successful, the zero-sized file is deleted from the ``queue`` directory.
|
|
# If the download fails, the zero-sized file remains and it'll be retried the
|
|
# next time cache-prefetcher runs.
|
|
#
|
|
# Possible values:
|
|
# * A valid path
|
|
#
|
|
# Related options:
|
|
# * ``image_cache_sqlite_db``
|
|
#
|
|
# (string value)
|
|
#image_cache_dir = <None>
|
|
|
|
#
|
|
# Default publisher_id for outgoing Glance notifications.
|
|
#
|
|
# This is the value that the notification driver will use to identify
|
|
# messages for events originating from the Glance service. Typically,
|
|
# this is the hostname of the instance that generated the message.
|
|
#
|
|
# Possible values:
|
|
# * Any reasonable instance identifier, for example: image.host1
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
#default_publisher_id = image.localhost
|
|
|
|
#
|
|
# List of notifications to be disabled.
|
|
#
|
|
# Specify a list of notifications that should not be emitted.
|
|
# A notification can be given either as a notification type to
|
|
# disable a single event notification, or as a notification group
|
|
# prefix to disable all event notifications within a group.
|
|
#
|
|
# Possible values:
|
|
# A comma-separated list of individual notification types or
|
|
# notification groups to be disabled. Currently supported groups:
|
|
# * image
|
|
# * image.member
|
|
# * task
|
|
# * metadef_namespace
|
|
# * metadef_object
|
|
# * metadef_property
|
|
# * metadef_resource_type
|
|
# * metadef_tag
|
|
# For a complete listing and description of each event refer to:
|
|
# http://docs.openstack.org/developer/glance/notifications.html
|
|
#
|
|
# The values must be specified as: <group_name>.<event_name>
|
|
# For example: image.create,task.success,metadef_tag
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (list value)
|
|
#disabled_notifications =
|
|
|
|
# DEPRECATED:
|
|
# Address the registry server is hosted on.
|
|
#
|
|
# Possible values:
|
|
# * A valid IP or hostname
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (host address value)
|
|
# This option is deprecated for removal since Queens.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason:
|
|
# Glance registry service is deprecated for removal.
|
|
#
|
|
# More information can be found from the spec:
|
|
# http://specs.openstack.org/openstack/glance-specs/specs/queens/approved/glance
|
|
# /deprecate-registry.html
|
|
#registry_host = 0.0.0.0
|
|
|
|
# DEPRECATED:
|
|
# Port the registry server is listening on.
|
|
#
|
|
# Possible values:
|
|
# * A valid port number
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (port value)
|
|
# Minimum value: 0
|
|
# Maximum value: 65535
|
|
# This option is deprecated for removal since Queens.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason:
|
|
# Glance registry service is deprecated for removal.
|
|
#
|
|
# More information can be found from the spec:
|
|
# http://specs.openstack.org/openstack/glance-specs/specs/queens/approved/glance
|
|
# /deprecate-registry.html
|
|
#registry_port = 9191
|
|
|
|
# DEPRECATED: Whether to pass through the user token when making requests to the
|
|
# registry. To prevent failures with token expiration during big files upload,
|
|
# it is recommended to set this parameter to False.If "use_user_token" is not in
|
|
# effect, then admin credentials can be specified. (boolean value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: This option was considered harmful and has been deprecated in M
|
|
# release. It will be removed in O release. For more information read OSSN-0060.
|
|
# Related functionality with uploading big images has been implemented with
|
|
# Keystone trusts support.
|
|
#use_user_token = true
|
|
|
|
# DEPRECATED: The administrators user name. If "use_user_token" is not in
|
|
# effect, then admin credentials can be specified. (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: This option was considered harmful and has been deprecated in M
|
|
# release. It will be removed in O release. For more information read OSSN-0060.
|
|
# Related functionality with uploading big images has been implemented with
|
|
# Keystone trusts support.
|
|
#admin_user = <None>
|
|
|
|
# DEPRECATED: The administrators password. If "use_user_token" is not in effect,
|
|
# then admin credentials can be specified. (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: This option was considered harmful and has been deprecated in M
|
|
# release. It will be removed in O release. For more information read OSSN-0060.
|
|
# Related functionality with uploading big images has been implemented with
|
|
# Keystone trusts support.
|
|
#admin_password = <None>
|
|
|
|
# DEPRECATED: The tenant name of the administrative user. If "use_user_token" is
|
|
# not in effect, then admin tenant name can be specified. (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: This option was considered harmful and has been deprecated in M
|
|
# release. It will be removed in O release. For more information read OSSN-0060.
|
|
# Related functionality with uploading big images has been implemented with
|
|
# Keystone trusts support.
|
|
#admin_tenant_name = <None>
|
|
|
|
# DEPRECATED: The URL to the keystone service. If "use_user_token" is not in
|
|
# effect and using keystone auth, then URL of keystone can be specified. (string
|
|
# value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: This option was considered harmful and has been deprecated in M
|
|
# release. It will be removed in O release. For more information read OSSN-0060.
|
|
# Related functionality with uploading big images has been implemented with
|
|
# Keystone trusts support.
|
|
#auth_url = <None>
|
|
|
|
# DEPRECATED: The strategy to use for authentication. If "use_user_token" is not
|
|
# in effect, then auth strategy can be specified. (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: This option was considered harmful and has been deprecated in M
|
|
# release. It will be removed in O release. For more information read OSSN-0060.
|
|
# Related functionality with uploading big images has been implemented with
|
|
# Keystone trusts support.
|
|
#auth_strategy = noauth
|
|
|
|
# DEPRECATED: The region for the authentication service. If "use_user_token" is
|
|
# not in effect and using keystone auth, then region name can be specified.
|
|
# (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: This option was considered harmful and has been deprecated in M
|
|
# release. It will be removed in O release. For more information read OSSN-0060.
|
|
# Related functionality with uploading big images has been implemented with
|
|
# Keystone trusts support.
|
|
#auth_region = <None>
|
|
|
|
# DEPRECATED:
|
|
# Protocol to use for communication with the registry server.
|
|
#
|
|
# Provide a string value representing the protocol to use for
|
|
# communication with the registry server. By default, this option is
|
|
# set to ``http`` and the connection is not secure.
|
|
#
|
|
# This option can be set to ``https`` to establish a secure connection
|
|
# to the registry server. In this case, provide a key to use for the
|
|
# SSL connection using the ``registry_client_key_file`` option. Also
|
|
# include the CA file and cert file using the options
|
|
# ``registry_client_ca_file`` and ``registry_client_cert_file``
|
|
# respectively.
|
|
#
|
|
# Possible values:
|
|
# * http
|
|
# * https
|
|
#
|
|
# Related options:
|
|
# * registry_client_key_file
|
|
# * registry_client_cert_file
|
|
# * registry_client_ca_file
|
|
#
|
|
# (string value)
|
|
# Possible values:
|
|
# http - <No description provided>
|
|
# https - <No description provided>
|
|
# This option is deprecated for removal since Queens.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason:
|
|
# Glance registry service is deprecated for removal.
|
|
#
|
|
# More information can be found from the spec:
|
|
# http://specs.openstack.org/openstack/glance-specs/specs/queens/approved/glance
|
|
# /deprecate-registry.html
|
|
#registry_client_protocol = http
|
|
|
|
# DEPRECATED:
|
|
# Absolute path to the private key file.
|
|
#
|
|
# Provide a string value representing a valid absolute path to the
|
|
# private key file to use for establishing a secure connection to
|
|
# the registry server.
|
|
#
|
|
# NOTE: This option must be set if ``registry_client_protocol`` is
|
|
# set to ``https``. Alternatively, the GLANCE_CLIENT_KEY_FILE
|
|
# environment variable may be set to a filepath of the key file.
|
|
#
|
|
# Possible values:
|
|
# * String value representing a valid absolute path to the key
|
|
# file.
|
|
#
|
|
# Related options:
|
|
# * registry_client_protocol
|
|
#
|
|
# (string value)
|
|
# This option is deprecated for removal since Queens.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason:
|
|
# Glance registry service is deprecated for removal.
|
|
#
|
|
# More information can be found from the spec:
|
|
# http://specs.openstack.org/openstack/glance-specs/specs/queens/approved/glance
|
|
# /deprecate-registry.html
|
|
#registry_client_key_file = /etc/ssl/key/key-file.pem
|
|
|
|
# DEPRECATED:
|
|
# Absolute path to the certificate file.
|
|
#
|
|
# Provide a string value representing a valid absolute path to the
|
|
# certificate file to use for establishing a secure connection to
|
|
# the registry server.
|
|
#
|
|
# NOTE: This option must be set if ``registry_client_protocol`` is
|
|
# set to ``https``. Alternatively, the GLANCE_CLIENT_CERT_FILE
|
|
# environment variable may be set to a filepath of the certificate
|
|
# file.
|
|
#
|
|
# Possible values:
|
|
# * String value representing a valid absolute path to the
|
|
# certificate file.
|
|
#
|
|
# Related options:
|
|
# * registry_client_protocol
|
|
#
|
|
# (string value)
|
|
# This option is deprecated for removal since Queens.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason:
|
|
# Glance registry service is deprecated for removal.
|
|
#
|
|
# More information can be found from the spec:
|
|
# http://specs.openstack.org/openstack/glance-specs/specs/queens/approved/glance
|
|
# /deprecate-registry.html
|
|
#registry_client_cert_file = /etc/ssl/certs/file.crt
|
|
|
|
# DEPRECATED:
|
|
# Absolute path to the Certificate Authority file.
|
|
#
|
|
# Provide a string value representing a valid absolute path to the
|
|
# certificate authority file to use for establishing a secure
|
|
# connection to the registry server.
|
|
#
|
|
# NOTE: This option must be set if ``registry_client_protocol`` is
|
|
# set to ``https``. Alternatively, the GLANCE_CLIENT_CA_FILE
|
|
# environment variable may be set to a filepath of the CA file.
|
|
# This option is ignored if the ``registry_client_insecure`` option
|
|
# is set to ``True``.
|
|
#
|
|
# Possible values:
|
|
# * String value representing a valid absolute path to the CA
|
|
# file.
|
|
#
|
|
# Related options:
|
|
# * registry_client_protocol
|
|
# * registry_client_insecure
|
|
#
|
|
# (string value)
|
|
# This option is deprecated for removal since Queens.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason:
|
|
# Glance registry service is deprecated for removal.
|
|
#
|
|
# More information can be found from the spec:
|
|
# http://specs.openstack.org/openstack/glance-specs/specs/queens/approved/glance
|
|
# /deprecate-registry.html
|
|
#registry_client_ca_file = /etc/ssl/cafile/file.ca
|
|
|
|
# DEPRECATED:
|
|
# Set verification of the registry server certificate.
|
|
#
|
|
# Provide a boolean value to determine whether or not to validate
|
|
# SSL connections to the registry server. By default, this option
|
|
# is set to ``False`` and the SSL connections are validated.
|
|
#
|
|
# If set to ``True``, the connection to the registry server is not
|
|
# validated via a certifying authority and the
|
|
# ``registry_client_ca_file`` option is ignored. This is the
|
|
# registry's equivalent of specifying --insecure on the command line
|
|
# using glanceclient for the API.
|
|
#
|
|
# Possible values:
|
|
# * True
|
|
# * False
|
|
#
|
|
# Related options:
|
|
# * registry_client_protocol
|
|
# * registry_client_ca_file
|
|
#
|
|
# (boolean value)
|
|
# This option is deprecated for removal since Queens.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason:
|
|
# Glance registry service is deprecated for removal.
|
|
#
|
|
# More information can be found from the spec:
|
|
# http://specs.openstack.org/openstack/glance-specs/specs/queens/approved/glance
|
|
# /deprecate-registry.html
|
|
#registry_client_insecure = false
|
|
|
|
# DEPRECATED:
|
|
# Timeout value for registry requests.
|
|
#
|
|
# Provide an integer value representing the period of time in seconds
|
|
# that the API server will wait for a registry request to complete.
|
|
# The default value is 600 seconds.
|
|
#
|
|
# A value of 0 implies that a request will never timeout.
|
|
#
|
|
# Possible values:
|
|
# * Zero
|
|
# * Positive integer
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 0
|
|
# This option is deprecated for removal since Queens.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason:
|
|
# Glance registry service is deprecated for removal.
|
|
#
|
|
# More information can be found from the spec:
|
|
# http://specs.openstack.org/openstack/glance-specs/specs/queens/approved/glance
|
|
# /deprecate-registry.html
|
|
#registry_client_timeout = 600
|
|
|
|
#
|
|
# Send headers received from identity when making requests to
|
|
# registry.
|
|
#
|
|
# Typically, Glance registry can be deployed in multiple flavors,
|
|
# which may or may not include authentication. For example,
|
|
# ``trusted-auth`` is a flavor that does not require the registry
|
|
# service to authenticate the requests it receives. However, the
|
|
# registry service may still need a user context to be populated to
|
|
# serve the requests. This can be achieved by the caller
|
|
# (the Glance API usually) passing through the headers it received
|
|
# from authenticating with identity for the same request. The typical
|
|
# headers sent are ``X-User-Id``, ``X-Tenant-Id``, ``X-Roles``,
|
|
# ``X-Identity-Status`` and ``X-Service-Catalog``.
|
|
#
|
|
# Provide a boolean value to determine whether to send the identity
|
|
# headers to provide tenant and user information along with the
|
|
# requests to registry service. By default, this option is set to
|
|
# ``False``, which means that user and tenant information is not
|
|
# available readily. It must be obtained by authenticating. Hence, if
|
|
# this is set to ``False``, ``flavor`` must be set to value that
|
|
# either includes authentication or authenticated user context.
|
|
#
|
|
# Possible values:
|
|
# * True
|
|
# * False
|
|
#
|
|
# Related options:
|
|
# * flavor
|
|
#
|
|
# (boolean value)
|
|
#send_identity_headers = false
|
|
|
|
#
|
|
# The amount of time, in seconds, to delay image scrubbing.
|
|
#
|
|
# When delayed delete is turned on, an image is put into ``pending_delete``
|
|
# state upon deletion until the scrubber deletes its image data. Typically, soon
|
|
# after the image is put into ``pending_delete`` state, it is available for
|
|
# scrubbing. However, scrubbing can be delayed until a later point using this
|
|
# configuration option. This option denotes the time period an image spends in
|
|
# ``pending_delete`` state before it is available for scrubbing.
|
|
#
|
|
# It is important to realize that this has storage implications. The larger the
|
|
# ``scrub_time``, the longer the time to reclaim backend storage from deleted
|
|
# images.
|
|
#
|
|
# Possible values:
|
|
# * Any non-negative integer
|
|
#
|
|
# Related options:
|
|
# * ``delayed_delete``
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 0
|
|
#scrub_time = 0
|
|
|
|
#
|
|
# The size of thread pool to be used for scrubbing images.
|
|
#
|
|
# When there are a large number of images to scrub, it is beneficial to scrub
|
|
# images in parallel so that the scrub queue stays in control and the backend
|
|
# storage is reclaimed in a timely fashion. This configuration option denotes
|
|
# the maximum number of images to be scrubbed in parallel. The default value is
|
|
# one, which signifies serial scrubbing. Any value above one indicates parallel
|
|
# scrubbing.
|
|
#
|
|
# Possible values:
|
|
# * Any non-zero positive integer
|
|
#
|
|
# Related options:
|
|
# * ``delayed_delete``
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 1
|
|
#scrub_pool_size = 1
|
|
|
|
#
|
|
# Turn on/off delayed delete.
|
|
#
|
|
# Typically when an image is deleted, the ``glance-api`` service puts the image
|
|
# into ``deleted`` state and deletes its data at the same time. Delayed delete
|
|
# is a feature in Glance that delays the actual deletion of image data until a
|
|
# later point in time (as determined by the configuration option
|
|
# ``scrub_time``).
|
|
# When delayed delete is turned on, the ``glance-api`` service puts the image
|
|
# into ``pending_delete`` state upon deletion and leaves the image data in the
|
|
# storage backend for the image scrubber to delete at a later time. The image
|
|
# scrubber will move the image into ``deleted`` state upon successful deletion
|
|
# of image data.
|
|
#
|
|
# NOTE: When delayed delete is turned on, image scrubber MUST be running as a
|
|
# periodic task to prevent the backend storage from filling up with undesired
|
|
# usage.
|
|
#
|
|
# Possible values:
|
|
# * True
|
|
# * False
|
|
#
|
|
# Related options:
|
|
# * ``scrub_time``
|
|
# * ``wakeup_time``
|
|
# * ``scrub_pool_size``
|
|
#
|
|
# (boolean value)
|
|
#delayed_delete = false
|
|
|
|
#
|
|
# From oslo.log
|
|
#
|
|
|
|
# If set to true, the logging level will be set to DEBUG instead of the default
|
|
# INFO level. (boolean value)
|
|
# Note: This option can be changed without restarting.
|
|
#debug = false
|
|
|
|
# The name of a logging configuration file. This file is appended to any
|
|
# existing logging configuration files. For details about logging configuration
|
|
# files, see the Python logging module documentation. Note that when logging
|
|
# configuration files are used then all logging configuration is set in the
|
|
# configuration file and other logging configuration options are ignored (for
|
|
# example, logging_context_format_string). (string value)
|
|
# Note: This option can be changed without restarting.
|
|
# Deprecated group/name - [DEFAULT]/log_config
|
|
#log_config_append = <None>
|
|
|
|
# Defines the format string for %%(asctime)s in log records. Default:
|
|
# %(default)s . This option is ignored if log_config_append is set. (string
|
|
# value)
|
|
#log_date_format = %Y-%m-%d %H:%M:%S
|
|
|
|
# (Optional) Name of log file to send logging output to. If no default is set,
|
|
# logging will go to stderr as defined by use_stderr. This option is ignored if
|
|
# log_config_append is set. (string value)
|
|
# Deprecated group/name - [DEFAULT]/logfile
|
|
#log_file = <None>
|
|
|
|
# (Optional) The base directory used for relative log_file paths. This option
|
|
# is ignored if log_config_append is set. (string value)
|
|
# Deprecated group/name - [DEFAULT]/logdir
|
|
#log_dir = <None>
|
|
|
|
# Uses logging handler designed to watch file system. When log file is moved or
|
|
# removed this handler will open a new log file with specified path
|
|
# instantaneously. It makes sense only if log_file option is specified and Linux
|
|
# platform is used. This option is ignored if log_config_append is set. (boolean
|
|
# value)
|
|
#watch_log_file = false
|
|
|
|
# Use syslog for logging. Existing syslog format is DEPRECATED and will be
|
|
# changed later to honor RFC5424. This option is ignored if log_config_append is
|
|
# set. (boolean value)
|
|
#use_syslog = false
|
|
|
|
# Enable journald for logging. If running in a systemd environment you may wish
|
|
# to enable journal support. Doing so will use the journal native protocol which
|
|
# includes structured metadata in addition to log messages.This option is
|
|
# ignored if log_config_append is set. (boolean value)
|
|
#use_journal = false
|
|
|
|
# Syslog facility to receive log lines. This option is ignored if
|
|
# log_config_append is set. (string value)
|
|
#syslog_log_facility = LOG_USER
|
|
|
|
# Use JSON formatting for logging. This option is ignored if log_config_append
|
|
# is set. (boolean value)
|
|
#use_json = false
|
|
|
|
# Log output to standard error. This option is ignored if log_config_append is
|
|
# set. (boolean value)
|
|
#use_stderr = false
|
|
|
|
# Format string to use for log messages with context. (string value)
|
|
#logging_context_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [%(request_id)s %(user_identity)s] %(instance)s%(message)s
|
|
|
|
# Format string to use for log messages when context is undefined. (string
|
|
# value)
|
|
#logging_default_format_string = %(asctime)s.%(msecs)03d %(process)d %(levelname)s %(name)s [-] %(instance)s%(message)s
|
|
|
|
# Additional data to append to log message when logging level for the message is
|
|
# DEBUG. (string value)
|
|
#logging_debug_format_suffix = %(funcName)s %(pathname)s:%(lineno)d
|
|
|
|
# Prefix each line of exception output with this format. (string value)
|
|
#logging_exception_prefix = %(asctime)s.%(msecs)03d %(process)d ERROR %(name)s %(instance)s
|
|
|
|
# Defines the format string for %(user_identity)s that is used in
|
|
# logging_context_format_string. (string value)
|
|
#logging_user_identity_format = %(user)s %(tenant)s %(domain)s %(user_domain)s %(project_domain)s
|
|
|
|
# List of package logging levels in logger=LEVEL pairs. This option is ignored
|
|
# if log_config_append is set. (list value)
|
|
#default_log_levels = amqp=WARN,amqplib=WARN,boto=WARN,qpid=WARN,sqlalchemy=WARN,suds=INFO,oslo.messaging=INFO,oslo_messaging=INFO,iso8601=WARN,requests.packages.urllib3.connectionpool=WARN,urllib3.connectionpool=WARN,websocket=WARN,requests.packages.urllib3.util.retry=WARN,urllib3.util.retry=WARN,keystonemiddleware=WARN,routes.middleware=WARN,stevedore=WARN,taskflow=WARN,keystoneauth=WARN,oslo.cache=INFO,dogpile.core.dogpile=INFO
|
|
|
|
# Enables or disables publication of error events. (boolean value)
|
|
#publish_errors = false
|
|
|
|
# The format for an instance that is passed with the log message. (string value)
|
|
#instance_format = "[instance: %(uuid)s] "
|
|
|
|
# The format for an instance UUID that is passed with the log message. (string
|
|
# value)
|
|
#instance_uuid_format = "[instance: %(uuid)s] "
|
|
|
|
# Interval, number of seconds, of log rate limiting. (integer value)
|
|
#rate_limit_interval = 0
|
|
|
|
# Maximum number of logged messages per rate_limit_interval. (integer value)
|
|
#rate_limit_burst = 0
|
|
|
|
# Log level name used by rate limiting: CRITICAL, ERROR, INFO, WARNING, DEBUG or
|
|
# empty string. Logs with level greater or equal to rate_limit_except_level are
|
|
# not filtered. An empty string means that all levels are filtered. (string
|
|
# value)
|
|
#rate_limit_except_level = CRITICAL
|
|
|
|
# Enables or disables fatal status of deprecations. (boolean value)
|
|
#fatal_deprecations = false
|
|
|
|
#
|
|
# From oslo.messaging
|
|
#
|
|
|
|
# Size of RPC connection pool. (integer value)
|
|
#rpc_conn_pool_size = 30
|
|
|
|
# The pool size limit for connections expiration policy (integer value)
|
|
#conn_pool_min_size = 2
|
|
|
|
# The time-to-live in sec of idle connections in the pool (integer value)
|
|
#conn_pool_ttl = 1200
|
|
|
|
# ZeroMQ bind address. Should be a wildcard (*), an ethernet interface, or IP.
|
|
# The "host" option should point or resolve to this address. (string value)
|
|
#rpc_zmq_bind_address = *
|
|
|
|
# MatchMaker driver. (string value)
|
|
# Possible values:
|
|
# redis - <No description provided>
|
|
# sentinel - <No description provided>
|
|
# dummy - <No description provided>
|
|
#rpc_zmq_matchmaker = redis
|
|
|
|
# Number of ZeroMQ contexts, defaults to 1. (integer value)
|
|
#rpc_zmq_contexts = 1
|
|
|
|
# Maximum number of ingress messages to locally buffer per topic. Default is
|
|
# unlimited. (integer value)
|
|
#rpc_zmq_topic_backlog = <None>
|
|
|
|
# Directory for holding IPC sockets. (string value)
|
|
#rpc_zmq_ipc_dir = /var/run/openstack
|
|
|
|
# Name of this node. Must be a valid hostname, FQDN, or IP address. Must match
|
|
# "host" option, if running Nova. (string value)
|
|
#rpc_zmq_host = localhost
|
|
|
|
# Number of seconds to wait before all pending messages will be sent after
|
|
# closing a socket. The default value of -1 specifies an infinite linger period.
|
|
# The value of 0 specifies no linger period. Pending messages shall be discarded
|
|
# immediately when the socket is closed. Positive values specify an upper bound
|
|
# for the linger period. (integer value)
|
|
# Deprecated group/name - [DEFAULT]/rpc_cast_timeout
|
|
#zmq_linger = -1
|
|
|
|
# The default number of seconds that poll should wait. Poll raises timeout
|
|
# exception when timeout expired. (integer value)
|
|
#rpc_poll_timeout = 1
|
|
|
|
# Expiration timeout in seconds of a name service record about existing target (
|
|
# < 0 means no timeout). (integer value)
|
|
#zmq_target_expire = 300
|
|
|
|
# Update period in seconds of a name service record about existing target.
|
|
# (integer value)
|
|
#zmq_target_update = 180
|
|
|
|
# Use PUB/SUB pattern for fanout methods. PUB/SUB always uses proxy. (boolean
|
|
# value)
|
|
#use_pub_sub = false
|
|
|
|
# Use ROUTER remote proxy. (boolean value)
|
|
#use_router_proxy = false
|
|
|
|
# This option makes direct connections dynamic or static. It makes sense only
|
|
# with use_router_proxy=False which means to use direct connections for direct
|
|
# message types (ignored otherwise). (boolean value)
|
|
#use_dynamic_connections = false
|
|
|
|
# How many additional connections to a host will be made for failover reasons.
|
|
# This option is actual only in dynamic connections mode. (integer value)
|
|
#zmq_failover_connections = 2
|
|
|
|
# Minimal port number for random ports range. (port value)
|
|
# Minimum value: 0
|
|
# Maximum value: 65535
|
|
#rpc_zmq_min_port = 49153
|
|
|
|
# Maximal port number for random ports range. (integer value)
|
|
# Minimum value: 1
|
|
# Maximum value: 65536
|
|
#rpc_zmq_max_port = 65536
|
|
|
|
# Number of retries to find free port number before fail with ZMQBindError.
|
|
# (integer value)
|
|
#rpc_zmq_bind_port_retries = 100
|
|
|
|
# Default serialization mechanism for serializing/deserializing
|
|
# outgoing/incoming messages (string value)
|
|
# Possible values:
|
|
# json - <No description provided>
|
|
# msgpack - <No description provided>
|
|
#rpc_zmq_serialization = json
|
|
|
|
# This option configures round-robin mode in zmq socket. True means not keeping
|
|
# a queue when server side disconnects. False means to keep queue and messages
|
|
# even if server is disconnected, when the server appears we send all
|
|
# accumulated messages to it. (boolean value)
|
|
#zmq_immediate = true
|
|
|
|
# Enable/disable TCP keepalive (KA) mechanism. The default value of -1 (or any
|
|
# other negative value) means to skip any overrides and leave it to OS default;
|
|
# 0 and 1 (or any other positive value) mean to disable and enable the option
|
|
# respectively. (integer value)
|
|
#zmq_tcp_keepalive = -1
|
|
|
|
# The duration between two keepalive transmissions in idle condition. The unit
|
|
# is platform dependent, for example, seconds in Linux, milliseconds in Windows
|
|
# etc. The default value of -1 (or any other negative value and 0) means to skip
|
|
# any overrides and leave it to OS default. (integer value)
|
|
#zmq_tcp_keepalive_idle = -1
|
|
|
|
# The number of retransmissions to be carried out before declaring that remote
|
|
# end is not available. The default value of -1 (or any other negative value and
|
|
# 0) means to skip any overrides and leave it to OS default. (integer value)
|
|
#zmq_tcp_keepalive_cnt = -1
|
|
|
|
# The duration between two successive keepalive retransmissions, if
|
|
# acknowledgement to the previous keepalive transmission is not received. The
|
|
# unit is platform dependent, for example, seconds in Linux, milliseconds in
|
|
# Windows etc. The default value of -1 (or any other negative value and 0) means
|
|
# to skip any overrides and leave it to OS default. (integer value)
|
|
#zmq_tcp_keepalive_intvl = -1
|
|
|
|
# Maximum number of (green) threads to work concurrently. (integer value)
|
|
#rpc_thread_pool_size = 100
|
|
|
|
# Expiration timeout in seconds of a sent/received message after which it is not
|
|
# tracked anymore by a client/server. (integer value)
|
|
#rpc_message_ttl = 300
|
|
|
|
# Wait for message acknowledgements from receivers. This mechanism works only
|
|
# via proxy without PUB/SUB. (boolean value)
|
|
#rpc_use_acks = false
|
|
|
|
# Number of seconds to wait for an ack from a cast/call. After each retry
|
|
# attempt this timeout is multiplied by some specified multiplier. (integer
|
|
# value)
|
|
#rpc_ack_timeout_base = 15
|
|
|
|
# Number to multiply base ack timeout by after each retry attempt. (integer
|
|
# value)
|
|
#rpc_ack_timeout_multiplier = 2
|
|
|
|
# Default number of message sending attempts in case of any problems occurred:
|
|
# positive value N means at most N retries, 0 means no retries, None or -1 (or
|
|
# any other negative values) mean to retry forever. This option is used only if
|
|
# acknowledgments are enabled. (integer value)
|
|
#rpc_retry_attempts = 3
|
|
|
|
# List of publisher hosts SubConsumer can subscribe on. This option has higher
|
|
# priority then the default publishers list taken from the matchmaker. (list
|
|
# value)
|
|
#subscribe_on =
|
|
|
|
# Size of executor thread pool when executor is threading or eventlet. (integer
|
|
# value)
|
|
# Deprecated group/name - [DEFAULT]/rpc_thread_pool_size
|
|
#executor_thread_pool_size = 64
|
|
|
|
# Seconds to wait for a response from a call. (integer value)
|
|
#rpc_response_timeout = 60
|
|
|
|
# The network address and optional user credentials for connecting to the
|
|
# messaging backend, in URL format. The expected format is:
|
|
#
|
|
# driver://[user:pass@]host:port[,[userN:passN@]hostN:portN]/virtual_host?query
|
|
#
|
|
# Example: rabbit://rabbitmq:password@127.0.0.1:5672//
|
|
#
|
|
# For full details on the fields in the URL see the documentation of
|
|
# oslo_messaging.TransportURL at
|
|
# https://docs.openstack.org/oslo.messaging/latest/reference/transport.html
|
|
# (string value)
|
|
#transport_url = <None>
|
|
|
|
# DEPRECATED: The messaging driver to use, defaults to rabbit. Other drivers
|
|
# include amqp and zmq. (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Replaced by [DEFAULT]/transport_url
|
|
#rpc_backend = rabbit
|
|
|
|
# The default exchange under which topics are scoped. May be overridden by an
|
|
# exchange name specified in the transport_url option. (string value)
|
|
#control_exchange = openstack
|
|
|
|
|
|
[cors]
|
|
|
|
#
|
|
# From oslo.middleware.cors
|
|
#
|
|
|
|
# Indicate whether this resource may be shared with the domain received in the
|
|
# requests "origin" header. Format: "<protocol>://<host>[:<port>]", no trailing
|
|
# slash. Example: https://horizon.example.com (list value)
|
|
#allowed_origin = <None>
|
|
|
|
# Indicate that the actual request can include user credentials (boolean value)
|
|
#allow_credentials = true
|
|
|
|
# Indicate which headers are safe to expose to the API. Defaults to HTTP Simple
|
|
# Headers. (list value)
|
|
#expose_headers = X-Image-Meta-Checksum,X-Auth-Token,X-Subject-Token,X-Service-Token,X-OpenStack-Request-ID
|
|
|
|
# Maximum cache age of CORS preflight requests. (integer value)
|
|
#max_age = 3600
|
|
|
|
# Indicate which methods can be used during the actual request. (list value)
|
|
#allow_methods = GET,PUT,POST,DELETE,PATCH
|
|
|
|
# Indicate which header field names may be used during the actual request. (list
|
|
# value)
|
|
#allow_headers = Content-MD5,X-Image-Meta-Checksum,X-Storage-Token,Accept-Encoding,X-Auth-Token,X-Identity-Status,X-Roles,X-Service-Catalog,X-User-Id,X-Tenant-Id,X-OpenStack-Request-ID
|
|
|
|
|
|
[database]
|
|
|
|
#
|
|
# From oslo.db
|
|
#
|
|
|
|
# If True, SQLite uses synchronous mode. (boolean value)
|
|
#sqlite_synchronous = true
|
|
|
|
# The back end to use for the database. (string value)
|
|
# Deprecated group/name - [DEFAULT]/db_backend
|
|
#backend = sqlalchemy
|
|
|
|
# The SQLAlchemy connection string to use to connect to the database. (string
|
|
# value)
|
|
# Deprecated group/name - [DEFAULT]/sql_connection
|
|
# Deprecated group/name - [DATABASE]/sql_connection
|
|
# Deprecated group/name - [sql]/connection
|
|
#connection = <None>
|
|
|
|
# The SQLAlchemy connection string to use to connect to the slave database.
|
|
# (string value)
|
|
#slave_connection = <None>
|
|
|
|
# The SQL mode to be used for MySQL sessions. This option, including the
|
|
# default, overrides any server-set SQL mode. To use whatever SQL mode is set by
|
|
# the server configuration, set this to no value. Example: mysql_sql_mode=
|
|
# (string value)
|
|
#mysql_sql_mode = TRADITIONAL
|
|
|
|
# If True, transparently enables support for handling MySQL Cluster (NDB).
|
|
# (boolean value)
|
|
#mysql_enable_ndb = false
|
|
|
|
# Connections which have been present in the connection pool longer than this
|
|
# number of seconds will be replaced with a new one the next time they are
|
|
# checked out from the pool. (integer value)
|
|
# Deprecated group/name - [DATABASE]/idle_timeout
|
|
# Deprecated group/name - [database]/idle_timeout
|
|
# Deprecated group/name - [DEFAULT]/sql_idle_timeout
|
|
# Deprecated group/name - [DATABASE]/sql_idle_timeout
|
|
# Deprecated group/name - [sql]/idle_timeout
|
|
#connection_recycle_time = 3600
|
|
|
|
# DEPRECATED: Minimum number of SQL connections to keep open in a pool. (integer
|
|
# value)
|
|
# Deprecated group/name - [DEFAULT]/sql_min_pool_size
|
|
# Deprecated group/name - [DATABASE]/sql_min_pool_size
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: The option to set the minimum pool size is not supported by
|
|
# sqlalchemy.
|
|
#min_pool_size = 1
|
|
|
|
# Maximum number of SQL connections to keep open in a pool. Setting a value of 0
|
|
# indicates no limit. (integer value)
|
|
# Deprecated group/name - [DEFAULT]/sql_max_pool_size
|
|
# Deprecated group/name - [DATABASE]/sql_max_pool_size
|
|
#max_pool_size = 5
|
|
|
|
# Maximum number of database connection retries during startup. Set to -1 to
|
|
# specify an infinite retry count. (integer value)
|
|
# Deprecated group/name - [DEFAULT]/sql_max_retries
|
|
# Deprecated group/name - [DATABASE]/sql_max_retries
|
|
#max_retries = 10
|
|
|
|
# Interval between retries of opening a SQL connection. (integer value)
|
|
# Deprecated group/name - [DEFAULT]/sql_retry_interval
|
|
# Deprecated group/name - [DATABASE]/reconnect_interval
|
|
#retry_interval = 10
|
|
|
|
# If set, use this value for max_overflow with SQLAlchemy. (integer value)
|
|
# Deprecated group/name - [DEFAULT]/sql_max_overflow
|
|
# Deprecated group/name - [DATABASE]/sqlalchemy_max_overflow
|
|
#max_overflow = 50
|
|
|
|
# Verbosity of SQL debugging information: 0=None, 100=Everything. (integer
|
|
# value)
|
|
# Minimum value: 0
|
|
# Maximum value: 100
|
|
# Deprecated group/name - [DEFAULT]/sql_connection_debug
|
|
#connection_debug = 0
|
|
|
|
# Add Python stack traces to SQL as comment strings. (boolean value)
|
|
# Deprecated group/name - [DEFAULT]/sql_connection_trace
|
|
#connection_trace = false
|
|
|
|
# If set, use this value for pool_timeout with SQLAlchemy. (integer value)
|
|
# Deprecated group/name - [DATABASE]/sqlalchemy_pool_timeout
|
|
#pool_timeout = <None>
|
|
|
|
# Enable the experimental use of database reconnect on connection lost. (boolean
|
|
# value)
|
|
#use_db_reconnect = false
|
|
|
|
# Seconds between retries of a database transaction. (integer value)
|
|
#db_retry_interval = 1
|
|
|
|
# If True, increases the interval between retries of a database operation up to
|
|
# db_max_retry_interval. (boolean value)
|
|
#db_inc_retry_interval = true
|
|
|
|
# If db_inc_retry_interval is set, the maximum seconds between retries of a
|
|
# database operation. (integer value)
|
|
#db_max_retry_interval = 10
|
|
|
|
# Maximum retries in case of connection error or deadlock error before error is
|
|
# raised. Set to -1 to specify an infinite retry count. (integer value)
|
|
#db_max_retries = 20
|
|
|
|
# Optional URL parameters to append onto the connection URL at connect time;
|
|
# specify as param1=value1¶m2=value2&... (string value)
|
|
#connection_parameters =
|
|
|
|
#
|
|
# From oslo.db.concurrency
|
|
#
|
|
|
|
# Enable the experimental use of thread pooling for all DB API calls (boolean
|
|
# value)
|
|
# Deprecated group/name - [DEFAULT]/dbapi_use_tpool
|
|
#use_tpool = false
|
|
|
|
|
|
[glance_store]
|
|
|
|
#
|
|
# From glance.store
|
|
#
|
|
|
|
# DEPRECATED:
|
|
# List of enabled Glance stores.
|
|
#
|
|
# Register the storage backends to use for storing disk images
|
|
# as a comma separated list. The default stores enabled for
|
|
# storing disk images with Glance are ``file`` and ``http``.
|
|
#
|
|
# Possible values:
|
|
# * A comma separated list that could include:
|
|
# * file
|
|
# * http
|
|
# * swift
|
|
# * rbd
|
|
# * sheepdog
|
|
# * cinder
|
|
# * vmware
|
|
#
|
|
# Related Options:
|
|
# * default_store
|
|
#
|
|
# (list value)
|
|
# This option is deprecated for removal since Rocky.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason:
|
|
# This option is deprecated against new config option
|
|
# ``enabled_backends`` which helps to configure multiple backend stores
|
|
# of different schemes.
|
|
#
|
|
# This option is scheduled for removal in the Stein development
|
|
# cycle.
|
|
#stores = file,http
|
|
|
|
# DEPRECATED:
|
|
# The default scheme to use for storing images.
|
|
#
|
|
# Provide a string value representing the default scheme to use for
|
|
# storing images. If not set, Glance uses ``file`` as the default
|
|
# scheme to store images with the ``file`` store.
|
|
#
|
|
# NOTE: The value given for this configuration option must be a valid
|
|
# scheme for a store registered with the ``stores`` configuration
|
|
# option.
|
|
#
|
|
# Possible values:
|
|
# * file
|
|
# * filesystem
|
|
# * http
|
|
# * https
|
|
# * swift
|
|
# * swift+http
|
|
# * swift+https
|
|
# * swift+config
|
|
# * rbd
|
|
# * sheepdog
|
|
# * cinder
|
|
# * vsphere
|
|
#
|
|
# Related Options:
|
|
# * stores
|
|
#
|
|
# (string value)
|
|
# Possible values:
|
|
# file - <No description provided>
|
|
# filesystem - <No description provided>
|
|
# http - <No description provided>
|
|
# https - <No description provided>
|
|
# swift - <No description provided>
|
|
# swift+http - <No description provided>
|
|
# swift+https - <No description provided>
|
|
# swift+config - <No description provided>
|
|
# rbd - <No description provided>
|
|
# sheepdog - <No description provided>
|
|
# cinder - <No description provided>
|
|
# vsphere - <No description provided>
|
|
# This option is deprecated for removal since Rocky.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason:
|
|
# This option is deprecated against new config option
|
|
# ``default_backend`` which acts similar to ``default_store`` config
|
|
# option.
|
|
#
|
|
# This option is scheduled for removal in the Stein development
|
|
# cycle.
|
|
#default_store = file
|
|
|
|
# DEPRECATED:
|
|
# Minimum interval in seconds to execute updating dynamic storage
|
|
# capabilities based on current backend status.
|
|
#
|
|
# Provide an integer value representing time in seconds to set the
|
|
# minimum interval before an update of dynamic storage capabilities
|
|
# for a storage backend can be attempted. Setting
|
|
# ``store_capabilities_update_min_interval`` does not mean updates
|
|
# occur periodically based on the set interval. Rather, the update
|
|
# is performed at the elapse of this interval set, if an operation
|
|
# of the store is triggered.
|
|
#
|
|
# By default, this option is set to zero and is disabled. Provide an
|
|
# integer value greater than zero to enable this option.
|
|
#
|
|
# NOTE 1: For more information on store capabilities and their updates,
|
|
# please visit: https://specs.openstack.org/openstack/glance-specs/specs/kilo
|
|
# /store-capabilities.html
|
|
#
|
|
# For more information on setting up a particular store in your
|
|
# deployment and help with the usage of this feature, please contact
|
|
# the storage driver maintainers listed here:
|
|
# https://docs.openstack.org/glance_store/latest/user/drivers.html
|
|
#
|
|
# NOTE 2: The dynamic store update capability described above is not
|
|
# implemented by any current store drivers. Thus, this option DOES
|
|
# NOT DO ANYTHING (and it never has). It is DEPRECATED and scheduled
|
|
# for removal early in the Stein development cycle.
|
|
#
|
|
# Possible values:
|
|
# * Zero
|
|
# * Positive integer
|
|
#
|
|
# Related Options:
|
|
# * None
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 0
|
|
# This option is deprecated for removal since Rocky.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason:
|
|
# This option configures a stub method that has not been implemented
|
|
# for any existing store drivers. Hence it is non-operational, and
|
|
# giving it a value does absolutely nothing.
|
|
#
|
|
# This option is scheduled for removal early in the Stein development
|
|
# cycle.
|
|
#store_capabilities_update_min_interval = 0
|
|
|
|
#
|
|
# Information to match when looking for cinder in the service catalog.
|
|
#
|
|
# When the ``cinder_endpoint_template`` is not set and any of
|
|
# ``cinder_store_auth_address``, ``cinder_store_user_name``,
|
|
# ``cinder_store_project_name``, ``cinder_store_password`` is not set,
|
|
# cinder store uses this information to lookup cinder endpoint from the service
|
|
# catalog in the current context. ``cinder_os_region_name``, if set, is taken
|
|
# into consideration to fetch the appropriate endpoint.
|
|
#
|
|
# The service catalog can be listed by the ``openstack catalog list`` command.
|
|
#
|
|
# Possible values:
|
|
# * A string of of the following form:
|
|
# ``<service_type>:<service_name>:<interface>``
|
|
# At least ``service_type`` and ``interface`` should be specified.
|
|
# ``service_name`` can be omitted.
|
|
#
|
|
# Related options:
|
|
# * cinder_os_region_name
|
|
# * cinder_endpoint_template
|
|
# * cinder_store_auth_address
|
|
# * cinder_store_user_name
|
|
# * cinder_store_project_name
|
|
# * cinder_store_password
|
|
#
|
|
# (string value)
|
|
#cinder_catalog_info = volumev2::publicURL
|
|
|
|
#
|
|
# Override service catalog lookup with template for cinder endpoint.
|
|
#
|
|
# When this option is set, this value is used to generate cinder endpoint,
|
|
# instead of looking up from the service catalog.
|
|
# This value is ignored if ``cinder_store_auth_address``,
|
|
# ``cinder_store_user_name``, ``cinder_store_project_name``, and
|
|
# ``cinder_store_password`` are specified.
|
|
#
|
|
# If this configuration option is set, ``cinder_catalog_info`` will be ignored.
|
|
#
|
|
# Possible values:
|
|
# * URL template string for cinder endpoint, where ``%%(tenant)s`` is
|
|
# replaced with the current tenant (project) name.
|
|
# For example: ``http://cinder.openstack.example.org/v2/%%(tenant)s``
|
|
#
|
|
# Related options:
|
|
# * cinder_store_auth_address
|
|
# * cinder_store_user_name
|
|
# * cinder_store_project_name
|
|
# * cinder_store_password
|
|
# * cinder_catalog_info
|
|
#
|
|
# (string value)
|
|
#cinder_endpoint_template = <None>
|
|
|
|
#
|
|
# Region name to lookup cinder service from the service catalog.
|
|
#
|
|
# This is used only when ``cinder_catalog_info`` is used for determining the
|
|
# endpoint. If set, the lookup for cinder endpoint by this node is filtered to
|
|
# the specified region. It is useful when multiple regions are listed in the
|
|
# catalog. If this is not set, the endpoint is looked up from every region.
|
|
#
|
|
# Possible values:
|
|
# * A string that is a valid region name.
|
|
#
|
|
# Related options:
|
|
# * cinder_catalog_info
|
|
#
|
|
# (string value)
|
|
# Deprecated group/name - [glance_store]/os_region_name
|
|
#cinder_os_region_name = <None>
|
|
|
|
#
|
|
# Location of a CA certificates file used for cinder client requests.
|
|
#
|
|
# The specified CA certificates file, if set, is used to verify cinder
|
|
# connections via HTTPS endpoint. If the endpoint is HTTP, this value is
|
|
# ignored.
|
|
# ``cinder_api_insecure`` must be set to ``True`` to enable the verification.
|
|
#
|
|
# Possible values:
|
|
# * Path to a ca certificates file
|
|
#
|
|
# Related options:
|
|
# * cinder_api_insecure
|
|
#
|
|
# (string value)
|
|
#cinder_ca_certificates_file = <None>
|
|
|
|
#
|
|
# Number of cinderclient retries on failed http calls.
|
|
#
|
|
# When a call failed by any errors, cinderclient will retry the call up to the
|
|
# specified times after sleeping a few seconds.
|
|
#
|
|
# Possible values:
|
|
# * A positive integer
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 0
|
|
#cinder_http_retries = 3
|
|
|
|
#
|
|
# Time period, in seconds, to wait for a cinder volume transition to
|
|
# complete.
|
|
#
|
|
# When the cinder volume is created, deleted, or attached to the glance node to
|
|
# read/write the volume data, the volume's state is changed. For example, the
|
|
# newly created volume status changes from ``creating`` to ``available`` after
|
|
# the creation process is completed. This specifies the maximum time to wait for
|
|
# the status change. If a timeout occurs while waiting, or the status is changed
|
|
# to an unexpected value (e.g. `error``), the image creation fails.
|
|
#
|
|
# Possible values:
|
|
# * A positive integer
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 0
|
|
#cinder_state_transition_timeout = 300
|
|
|
|
#
|
|
# Allow to perform insecure SSL requests to cinder.
|
|
#
|
|
# If this option is set to True, HTTPS endpoint connection is verified using the
|
|
# CA certificates file specified by ``cinder_ca_certificates_file`` option.
|
|
#
|
|
# Possible values:
|
|
# * True
|
|
# * False
|
|
#
|
|
# Related options:
|
|
# * cinder_ca_certificates_file
|
|
#
|
|
# (boolean value)
|
|
#cinder_api_insecure = false
|
|
|
|
#
|
|
# The address where the cinder authentication service is listening.
|
|
#
|
|
# When all of ``cinder_store_auth_address``, ``cinder_store_user_name``,
|
|
# ``cinder_store_project_name``, and ``cinder_store_password`` options are
|
|
# specified, the specified values are always used for the authentication.
|
|
# This is useful to hide the image volumes from users by storing them in a
|
|
# project/tenant specific to the image service. It also enables users to share
|
|
# the image volume among other projects under the control of glance's ACL.
|
|
#
|
|
# If either of these options are not set, the cinder endpoint is looked up
|
|
# from the service catalog, and current context's user and project are used.
|
|
#
|
|
# Possible values:
|
|
# * A valid authentication service address, for example:
|
|
# ``http://openstack.example.org/identity/v2.0``
|
|
#
|
|
# Related options:
|
|
# * cinder_store_user_name
|
|
# * cinder_store_password
|
|
# * cinder_store_project_name
|
|
#
|
|
# (string value)
|
|
#cinder_store_auth_address = <None>
|
|
|
|
#
|
|
# User name to authenticate against cinder.
|
|
#
|
|
# This must be used with all the following related options. If any of these are
|
|
# not specified, the user of the current context is used.
|
|
#
|
|
# Possible values:
|
|
# * A valid user name
|
|
#
|
|
# Related options:
|
|
# * cinder_store_auth_address
|
|
# * cinder_store_password
|
|
# * cinder_store_project_name
|
|
#
|
|
# (string value)
|
|
#cinder_store_user_name = <None>
|
|
|
|
#
|
|
# Password for the user authenticating against cinder.
|
|
#
|
|
# This must be used with all the following related options. If any of these are
|
|
# not specified, the user of the current context is used.
|
|
#
|
|
# Possible values:
|
|
# * A valid password for the user specified by ``cinder_store_user_name``
|
|
#
|
|
# Related options:
|
|
# * cinder_store_auth_address
|
|
# * cinder_store_user_name
|
|
# * cinder_store_project_name
|
|
#
|
|
# (string value)
|
|
#cinder_store_password = <None>
|
|
|
|
#
|
|
# Project name where the image volume is stored in cinder.
|
|
#
|
|
# If this configuration option is not set, the project in current context is
|
|
# used.
|
|
#
|
|
# This must be used with all the following related options. If any of these are
|
|
# not specified, the project of the current context is used.
|
|
#
|
|
# Possible values:
|
|
# * A valid project name
|
|
#
|
|
# Related options:
|
|
# * ``cinder_store_auth_address``
|
|
# * ``cinder_store_user_name``
|
|
# * ``cinder_store_password``
|
|
#
|
|
# (string value)
|
|
#cinder_store_project_name = <None>
|
|
|
|
#
|
|
# Path to the rootwrap configuration file to use for running commands as root.
|
|
#
|
|
# The cinder store requires root privileges to operate the image volumes (for
|
|
# connecting to iSCSI/FC volumes and reading/writing the volume data, etc.).
|
|
# The configuration file should allow the required commands by cinder store and
|
|
# os-brick library.
|
|
#
|
|
# Possible values:
|
|
# * Path to the rootwrap config file
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
#rootwrap_config = /etc/glance/rootwrap.conf
|
|
|
|
#
|
|
# Volume type that will be used for volume creation in cinder.
|
|
#
|
|
# Some cinder backends can have several volume types to optimize storage usage.
|
|
# Adding this option allows an operator to choose a specific volume type
|
|
# in cinder that can be optimized for images.
|
|
#
|
|
# If this is not set, then the default volume type specified in the cinder
|
|
# configuration will be used for volume creation.
|
|
#
|
|
# Possible values:
|
|
# * A valid volume type from cinder
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
#cinder_volume_type = <None>
|
|
|
|
#
|
|
# 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
|
|
# https://docs.openstack.org/glance/latest/configuration/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:
|
|
# * ``<a valid directory path>:<optional integer priority>``
|
|
#
|
|
# 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 = <None>
|
|
|
|
#
|
|
# 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
|
|
# https://docs.openstack.org/glance/latest/configuration/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 = <None>
|
|
|
|
#
|
|
# 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 = <None>
|
|
|
|
#
|
|
# 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.<USER> 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
|
|
#
|
|
# (host address value)
|
|
#sheepdog_store_address = 127.0.0.1
|
|
|
|
#
|
|
# Set verification of the server certificate.
|
|
#
|
|
# This boolean determines whether or not to verify the server
|
|
# certificate. If this option is set to True, swiftclient won't check
|
|
# for a valid SSL certificate when authenticating. If the option is set
|
|
# to False, then the default CA truststore is used for verification.
|
|
#
|
|
# Possible values:
|
|
# * True
|
|
# * False
|
|
#
|
|
# Related options:
|
|
# * swift_store_cacert
|
|
#
|
|
# (boolean value)
|
|
#swift_store_auth_insecure = false
|
|
|
|
#
|
|
# Path to the CA bundle file.
|
|
#
|
|
# This configuration option enables the operator to specify the path to
|
|
# a custom Certificate Authority file for SSL verification when
|
|
# connecting to Swift.
|
|
#
|
|
# Possible values:
|
|
# * A valid path to a CA file
|
|
#
|
|
# Related options:
|
|
# * swift_store_auth_insecure
|
|
#
|
|
# (string value)
|
|
#swift_store_cacert = /etc/ssl/certs/ca-certificates.crt
|
|
|
|
#
|
|
# The region of Swift endpoint to use by Glance.
|
|
#
|
|
# Provide a string value representing a Swift region where Glance
|
|
# can connect to for image storage. By default, there is no region
|
|
# set.
|
|
#
|
|
# When Glance uses Swift as the storage backend to store images
|
|
# for a specific tenant that has multiple endpoints, setting of a
|
|
# Swift region with ``swift_store_region`` allows Glance to connect
|
|
# to Swift in the specified region as opposed to a single region
|
|
# connectivity.
|
|
#
|
|
# This option can be configured for both single-tenant and
|
|
# multi-tenant storage.
|
|
#
|
|
# NOTE: Setting the region with ``swift_store_region`` is
|
|
# tenant-specific and is necessary ``only if`` the tenant has
|
|
# multiple endpoints across different regions.
|
|
#
|
|
# Possible values:
|
|
# * A string value representing a valid Swift region.
|
|
#
|
|
# Related Options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
#swift_store_region = RegionTwo
|
|
|
|
#
|
|
# The URL endpoint to use for Swift backend storage.
|
|
#
|
|
# Provide a string value representing the URL endpoint to use for
|
|
# storing Glance images in Swift store. By default, an endpoint
|
|
# is not set and the storage URL returned by ``auth`` is used.
|
|
# Setting an endpoint with ``swift_store_endpoint`` overrides the
|
|
# storage URL and is used for Glance image storage.
|
|
#
|
|
# NOTE: The URL should include the path up to, but excluding the
|
|
# container. The location of an object is obtained by appending
|
|
# the container and object to the configured URL.
|
|
#
|
|
# Possible values:
|
|
# * String value representing a valid URL path up to a Swift container
|
|
#
|
|
# Related Options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
#swift_store_endpoint = https://swift.openstack.example.org/v1/path_not_including_container_name
|
|
|
|
#
|
|
# Endpoint Type of Swift service.
|
|
#
|
|
# This string value indicates the endpoint type to use to fetch the
|
|
# Swift endpoint. The endpoint type determines the actions the user will
|
|
# be allowed to perform, for instance, reading and writing to the Store.
|
|
# This setting is only used if swift_store_auth_version is greater than
|
|
# 1.
|
|
#
|
|
# Possible values:
|
|
# * publicURL
|
|
# * adminURL
|
|
# * internalURL
|
|
#
|
|
# Related options:
|
|
# * swift_store_endpoint
|
|
#
|
|
# (string value)
|
|
# Possible values:
|
|
# publicURL - <No description provided>
|
|
# adminURL - <No description provided>
|
|
# internalURL - <No description provided>
|
|
#swift_store_endpoint_type = publicURL
|
|
|
|
#
|
|
# Type of Swift service to use.
|
|
#
|
|
# Provide a string value representing the service type to use for
|
|
# storing images while using Swift backend storage. The default
|
|
# service type is set to ``object-store``.
|
|
#
|
|
# NOTE: If ``swift_store_auth_version`` is set to 2, the value for
|
|
# this configuration option needs to be ``object-store``. If using
|
|
# a higher version of Keystone or a different auth scheme, this
|
|
# option may be modified.
|
|
#
|
|
# Possible values:
|
|
# * A string representing a valid service type for Swift storage.
|
|
#
|
|
# Related Options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
#swift_store_service_type = object-store
|
|
|
|
#
|
|
# Name of single container to store images/name prefix for multiple containers
|
|
#
|
|
# When a single container is being used to store images, this configuration
|
|
# option indicates the container within the Glance account to be used for
|
|
# storing all images. When multiple containers are used to store images, this
|
|
# will be the name prefix for all containers. Usage of single/multiple
|
|
# containers can be controlled using the configuration option
|
|
# ``swift_store_multiple_containers_seed``.
|
|
#
|
|
# When using multiple containers, the containers will be named after the value
|
|
# set for this configuration option with the first N chars of the image UUID
|
|
# as the suffix delimited by an underscore (where N is specified by
|
|
# ``swift_store_multiple_containers_seed``).
|
|
#
|
|
# Example: if the seed is set to 3 and swift_store_container = ``glance``, then
|
|
# an image with UUID ``fdae39a1-bac5-4238-aba4-69bcc726e848`` would be placed in
|
|
# the container ``glance_fda``. All dashes in the UUID are included when
|
|
# creating the container name but do not count toward the character limit, so
|
|
# when N=10 the container name would be ``glance_fdae39a1-ba.``
|
|
#
|
|
# Possible values:
|
|
# * If using single container, this configuration option can be any string
|
|
# that is a valid swift container name in Glance's Swift account
|
|
# * If using multiple containers, this configuration option can be any
|
|
# string as long as it satisfies the container naming rules enforced by
|
|
# Swift. The value of ``swift_store_multiple_containers_seed`` should be
|
|
# taken into account as well.
|
|
#
|
|
# Related options:
|
|
# * ``swift_store_multiple_containers_seed``
|
|
# * ``swift_store_multi_tenant``
|
|
# * ``swift_store_create_container_on_put``
|
|
#
|
|
# (string value)
|
|
#swift_store_container = glance
|
|
|
|
#
|
|
# The size threshold, in MB, after which Glance will start segmenting image
|
|
# data.
|
|
#
|
|
# Swift has an upper limit on the size of a single uploaded object. By default,
|
|
# this is 5GB. To upload objects bigger than this limit, objects are segmented
|
|
# into multiple smaller objects that are tied together with a manifest file.
|
|
# For more detail, refer to
|
|
# https://docs.openstack.org/swift/latest/overview_large_objects.html
|
|
#
|
|
# This configuration option specifies the size threshold over which the Swift
|
|
# driver will start segmenting image data into multiple smaller files.
|
|
# Currently, the Swift driver only supports creating Dynamic Large Objects.
|
|
#
|
|
# NOTE: This should be set by taking into account the large object limit
|
|
# enforced by the Swift cluster in consideration.
|
|
#
|
|
# Possible values:
|
|
# * A positive integer that is less than or equal to the large object limit
|
|
# enforced by the Swift cluster in consideration.
|
|
#
|
|
# Related options:
|
|
# * ``swift_store_large_object_chunk_size``
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 1
|
|
#swift_store_large_object_size = 5120
|
|
|
|
#
|
|
# The maximum size, in MB, of the segments when image data is segmented.
|
|
#
|
|
# When image data is segmented to upload images that are larger than the limit
|
|
# enforced by the Swift cluster, image data is broken into segments that are no
|
|
# bigger than the size specified by this configuration option.
|
|
# Refer to ``swift_store_large_object_size`` for more detail.
|
|
#
|
|
# For example: if ``swift_store_large_object_size`` is 5GB and
|
|
# ``swift_store_large_object_chunk_size`` is 1GB, an image of size 6.2GB will be
|
|
# segmented into 7 segments where the first six segments will be 1GB in size and
|
|
# the seventh segment will be 0.2GB.
|
|
#
|
|
# Possible values:
|
|
# * A positive integer that is less than or equal to the large object limit
|
|
# enforced by Swift cluster in consideration.
|
|
#
|
|
# Related options:
|
|
# * ``swift_store_large_object_size``
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 1
|
|
#swift_store_large_object_chunk_size = 200
|
|
|
|
#
|
|
# Create container, if it doesn't already exist, when uploading image.
|
|
#
|
|
# At the time of uploading an image, if the corresponding container doesn't
|
|
# exist, it will be created provided this configuration option is set to True.
|
|
# By default, it won't be created. This behavior is applicable for both single
|
|
# and multiple containers mode.
|
|
#
|
|
# Possible values:
|
|
# * True
|
|
# * False
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (boolean value)
|
|
#swift_store_create_container_on_put = false
|
|
|
|
#
|
|
# Store images in tenant's Swift account.
|
|
#
|
|
# This enables multi-tenant storage mode which causes Glance images to be stored
|
|
# in tenant specific Swift accounts. If this is disabled, Glance stores all
|
|
# images in its own account. More details multi-tenant store can be found at
|
|
# https://wiki.openstack.org/wiki/GlanceSwiftTenantSpecificStorage
|
|
#
|
|
# NOTE: If using multi-tenant swift store, please make sure
|
|
# that you do not set a swift configuration file with the
|
|
# 'swift_store_config_file' option.
|
|
#
|
|
# Possible values:
|
|
# * True
|
|
# * False
|
|
#
|
|
# Related options:
|
|
# * swift_store_config_file
|
|
#
|
|
# (boolean value)
|
|
#swift_store_multi_tenant = false
|
|
|
|
#
|
|
# Seed indicating the number of containers to use for storing images.
|
|
#
|
|
# When using a single-tenant store, images can be stored in one or more than one
|
|
# containers. When set to 0, all images will be stored in one single container.
|
|
# When set to an integer value between 1 and 32, multiple containers will be
|
|
# used to store images. This configuration option will determine how many
|
|
# containers are created. The total number of containers that will be used is
|
|
# equal to 16^N, so if this config option is set to 2, then 16^2=256 containers
|
|
# will be used to store images.
|
|
#
|
|
# Please refer to ``swift_store_container`` for more detail on the naming
|
|
# convention. More detail about using multiple containers can be found at
|
|
# https://specs.openstack.org/openstack/glance-specs/specs/kilo/swift-store-
|
|
# multiple-containers.html
|
|
#
|
|
# NOTE: This is used only when swift_store_multi_tenant is disabled.
|
|
#
|
|
# Possible values:
|
|
# * A non-negative integer less than or equal to 32
|
|
#
|
|
# Related options:
|
|
# * ``swift_store_container``
|
|
# * ``swift_store_multi_tenant``
|
|
# * ``swift_store_create_container_on_put``
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 0
|
|
# Maximum value: 32
|
|
#swift_store_multiple_containers_seed = 0
|
|
|
|
#
|
|
# List of tenants that will be granted admin access.
|
|
#
|
|
# This is a list of tenants that will be granted read/write access on
|
|
# all Swift containers created by Glance in multi-tenant mode. The
|
|
# default value is an empty list.
|
|
#
|
|
# Possible values:
|
|
# * A comma separated list of strings representing UUIDs of Keystone
|
|
# projects/tenants
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (list value)
|
|
#swift_store_admin_tenants =
|
|
|
|
#
|
|
# SSL layer compression for HTTPS Swift requests.
|
|
#
|
|
# Provide a boolean value to determine whether or not to compress
|
|
# HTTPS Swift requests for images at the SSL layer. By default,
|
|
# compression is enabled.
|
|
#
|
|
# When using Swift as the backend store for Glance image storage,
|
|
# SSL layer compression of HTTPS Swift requests can be set using
|
|
# this option. If set to False, SSL layer compression of HTTPS
|
|
# Swift requests is disabled. Disabling this option may improve
|
|
# performance for images which are already in a compressed format,
|
|
# for example, qcow2.
|
|
#
|
|
# Possible values:
|
|
# * True
|
|
# * False
|
|
#
|
|
# Related Options:
|
|
# * None
|
|
#
|
|
# (boolean value)
|
|
#swift_store_ssl_compression = true
|
|
|
|
#
|
|
# The number of times a Swift download will be retried before the
|
|
# request fails.
|
|
#
|
|
# Provide an integer value representing the number of times an image
|
|
# download must be retried before erroring out. The default value is
|
|
# zero (no retry on a failed image download). When set to a positive
|
|
# integer value, ``swift_store_retry_get_count`` ensures that the
|
|
# download is attempted this many more times upon a download failure
|
|
# before sending an error message.
|
|
#
|
|
# Possible values:
|
|
# * Zero
|
|
# * Positive integer value
|
|
#
|
|
# Related Options:
|
|
# * None
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 0
|
|
#swift_store_retry_get_count = 0
|
|
|
|
#
|
|
# Time in seconds defining the size of the window in which a new
|
|
# token may be requested before the current token is due to expire.
|
|
#
|
|
# Typically, the Swift storage driver fetches a new token upon the
|
|
# expiration of the current token to ensure continued access to
|
|
# Swift. However, some Swift transactions (like uploading image
|
|
# segments) may not recover well if the token expires on the fly.
|
|
#
|
|
# Hence, by fetching a new token before the current token expiration,
|
|
# we make sure that the token does not expire or is close to expiry
|
|
# before a transaction is attempted. By default, the Swift storage
|
|
# driver requests for a new token 60 seconds or less before the
|
|
# current token expiration.
|
|
#
|
|
# Possible values:
|
|
# * Zero
|
|
# * Positive integer value
|
|
#
|
|
# Related Options:
|
|
# * None
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 0
|
|
#swift_store_expire_soon_interval = 60
|
|
|
|
#
|
|
# Use trusts for multi-tenant Swift store.
|
|
#
|
|
# This option instructs the Swift store to create a trust for each
|
|
# add/get request when the multi-tenant store is in use. Using trusts
|
|
# allows the Swift store to avoid problems that can be caused by an
|
|
# authentication token expiring during the upload or download of data.
|
|
#
|
|
# By default, ``swift_store_use_trusts`` is set to ``True``(use of
|
|
# trusts is enabled). If set to ``False``, a user token is used for
|
|
# the Swift connection instead, eliminating the overhead of trust
|
|
# creation.
|
|
#
|
|
# NOTE: This option is considered only when
|
|
# ``swift_store_multi_tenant`` is set to ``True``
|
|
#
|
|
# Possible values:
|
|
# * True
|
|
# * False
|
|
#
|
|
# Related options:
|
|
# * swift_store_multi_tenant
|
|
#
|
|
# (boolean value)
|
|
#swift_store_use_trusts = true
|
|
|
|
#
|
|
# Buffer image segments before upload to Swift.
|
|
#
|
|
# Provide a boolean value to indicate whether or not Glance should
|
|
# buffer image data to disk while uploading to swift. This enables
|
|
# Glance to resume uploads on error.
|
|
#
|
|
# NOTES:
|
|
# When enabling this option, one should take great care as this
|
|
# increases disk usage on the API node. Be aware that depending
|
|
# upon how the file system is configured, the disk space used
|
|
# for buffering may decrease the actual disk space available for
|
|
# the glance image cache. Disk utilization will cap according to
|
|
# the following equation:
|
|
# (``swift_store_large_object_chunk_size`` * ``workers`` * 1000)
|
|
#
|
|
# Possible values:
|
|
# * True
|
|
# * False
|
|
#
|
|
# Related options:
|
|
# * swift_upload_buffer_dir
|
|
#
|
|
# (boolean value)
|
|
#swift_buffer_on_upload = false
|
|
|
|
#
|
|
# Reference to default Swift account/backing store parameters.
|
|
#
|
|
# Provide a string value representing a reference to the default set
|
|
# of parameters required for using swift account/backing store for
|
|
# image storage. The default reference value for this configuration
|
|
# option is 'ref1'. This configuration option dereferences the
|
|
# parameters and facilitates image storage in Swift storage backend
|
|
# every time a new image is added.
|
|
#
|
|
# Possible values:
|
|
# * A valid string value
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
#default_swift_reference = ref1
|
|
|
|
# DEPRECATED: Version of the authentication service to use. Valid versions are 2
|
|
# and 3 for keystone and 1 (deprecated) for swauth and rackspace. (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason:
|
|
# The option 'auth_version' in the Swift back-end configuration file is
|
|
# used instead.
|
|
#swift_store_auth_version = 2
|
|
|
|
# DEPRECATED: The address where the Swift authentication service is listening.
|
|
# (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason:
|
|
# The option 'auth_address' in the Swift back-end configuration file is
|
|
# used instead.
|
|
#swift_store_auth_address = <None>
|
|
|
|
# DEPRECATED: The user to authenticate against the Swift authentication service.
|
|
# (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason:
|
|
# The option 'user' in the Swift back-end configuration file is set instead.
|
|
#swift_store_user = <None>
|
|
|
|
# DEPRECATED: Auth key for the user authenticating against the Swift
|
|
# authentication service. (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason:
|
|
# The option 'key' in the Swift back-end configuration file is used
|
|
# to set the authentication key instead.
|
|
#swift_store_key = <None>
|
|
|
|
#
|
|
# Absolute path to the file containing the swift account(s)
|
|
# configurations.
|
|
#
|
|
# Include a string value representing the path to a configuration
|
|
# file that has references for each of the configured Swift
|
|
# account(s)/backing stores. By default, no file path is specified
|
|
# and customized Swift referencing is disabled. Configuring this
|
|
# option is highly recommended while using Swift storage backend for
|
|
# image storage as it avoids storage of credentials in the database.
|
|
#
|
|
# NOTE: Please do not configure this option if you have set
|
|
# ``swift_store_multi_tenant`` to ``True``.
|
|
#
|
|
# Possible values:
|
|
# * String value representing an absolute path on the glance-api
|
|
# node
|
|
#
|
|
# Related options:
|
|
# * swift_store_multi_tenant
|
|
#
|
|
# (string value)
|
|
#swift_store_config_file = <None>
|
|
|
|
#
|
|
# Directory to buffer image segments before upload to Swift.
|
|
#
|
|
# Provide a string value representing the absolute path to the
|
|
# directory on the glance node where image segments will be
|
|
# buffered briefly before they are uploaded to swift.
|
|
#
|
|
# NOTES:
|
|
# * This is required only when the configuration option
|
|
# ``swift_buffer_on_upload`` is set to True.
|
|
# * This directory should be provisioned keeping in mind the
|
|
# ``swift_store_large_object_chunk_size`` and the maximum
|
|
# number of images that could be uploaded simultaneously by
|
|
# a given glance node.
|
|
#
|
|
# Possible values:
|
|
# * String value representing an absolute directory path
|
|
#
|
|
# Related options:
|
|
# * swift_buffer_on_upload
|
|
# * swift_store_large_object_chunk_size
|
|
#
|
|
# (string value)
|
|
#swift_upload_buffer_dir = <None>
|
|
|
|
#
|
|
# 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
|
|
#
|
|
# (host address 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
|
|
# <datacenter_path>:<datastore_name>:<optional_weight>.
|
|
#
|
|
# 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:
|
|
# <datacenter_path>:<datastore_name>:<optional_weight>
|
|
#
|
|
# Related options:
|
|
# * None
|
|
#
|
|
# (multi valued)
|
|
#vmware_datastores =
|
|
|
|
|
|
[image_format]
|
|
|
|
#
|
|
# From glance.api
|
|
#
|
|
|
|
# Supported values for the 'container_format' image attribute (list value)
|
|
# Deprecated group/name - [DEFAULT]/container_formats
|
|
#container_formats = ami,ari,aki,bare,ovf,ova,docker
|
|
|
|
# Supported values for the 'disk_format' image attribute (list value)
|
|
# Deprecated group/name - [DEFAULT]/disk_formats
|
|
#disk_formats = ami,ari,aki,vhd,vhdx,vmdk,raw,qcow2,vdi,iso,ploop
|
|
|
|
|
|
[keystone_authtoken]
|
|
|
|
#
|
|
# From keystonemiddleware.auth_token
|
|
#
|
|
|
|
# Complete "public" Identity API endpoint. This endpoint should not be an
|
|
# "admin" endpoint, as it should be accessible by all end users. Unauthenticated
|
|
# clients are redirected to this endpoint to authenticate. Although this
|
|
# endpoint should ideally be unversioned, client support in the wild varies. If
|
|
# you're using a versioned v2 endpoint here, then this should *not* be the same
|
|
# endpoint the service user utilizes for validating tokens, because normal end
|
|
# users may not be able to reach that endpoint. (string value)
|
|
# Deprecated group/name - [keystone_authtoken]/auth_uri
|
|
#www_authenticate_uri = <None>
|
|
|
|
# DEPRECATED: Complete "public" Identity API endpoint. This endpoint should not
|
|
# be an "admin" endpoint, as it should be accessible by all end users.
|
|
# Unauthenticated clients are redirected to this endpoint to authenticate.
|
|
# Although this endpoint should ideally be unversioned, client support in the
|
|
# wild varies. If you're using a versioned v2 endpoint here, then this should
|
|
# *not* be the same endpoint the service user utilizes for validating tokens,
|
|
# because normal end users may not be able to reach that endpoint. This option
|
|
# is deprecated in favor of www_authenticate_uri and will be removed in the S
|
|
# release. (string value)
|
|
# This option is deprecated for removal since Queens.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: The auth_uri option is deprecated in favor of www_authenticate_uri and
|
|
# will be removed in the S release.
|
|
#auth_uri = <None>
|
|
|
|
# API version of the admin Identity API endpoint. (string value)
|
|
#auth_version = <None>
|
|
|
|
# Do not handle authorization requests within the middleware, but delegate the
|
|
# authorization decision to downstream WSGI components. (boolean value)
|
|
#delay_auth_decision = false
|
|
|
|
# Request timeout value for communicating with Identity API server. (integer
|
|
# value)
|
|
#http_connect_timeout = <None>
|
|
|
|
# How many times are we trying to reconnect when communicating with Identity API
|
|
# Server. (integer value)
|
|
#http_request_max_retries = 3
|
|
|
|
# Request environment key where the Swift cache object is stored. When
|
|
# auth_token middleware is deployed with a Swift cache, use this option to have
|
|
# the middleware share a caching backend with swift. Otherwise, use the
|
|
# ``memcached_servers`` option instead. (string value)
|
|
#cache = <None>
|
|
|
|
# Required if identity server requires client certificate (string value)
|
|
#certfile = <None>
|
|
|
|
# Required if identity server requires client certificate (string value)
|
|
#keyfile = <None>
|
|
|
|
# A PEM encoded Certificate Authority to use when verifying HTTPs connections.
|
|
# Defaults to system CAs. (string value)
|
|
#cafile = <None>
|
|
|
|
# Verify HTTPS connections. (boolean value)
|
|
#insecure = false
|
|
|
|
# The region in which the identity server can be found. (string value)
|
|
#region_name = <None>
|
|
|
|
# DEPRECATED: Directory used to cache files related to PKI tokens. This option
|
|
# has been deprecated in the Ocata release and will be removed in the P release.
|
|
# (string value)
|
|
# This option is deprecated for removal since Ocata.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: PKI token format is no longer supported.
|
|
#signing_dir = <None>
|
|
|
|
# Optionally specify a list of memcached server(s) to use for caching. If left
|
|
# undefined, tokens will instead be cached in-process. (list value)
|
|
# Deprecated group/name - [keystone_authtoken]/memcache_servers
|
|
#memcached_servers = <None>
|
|
|
|
# In order to prevent excessive effort spent validating tokens, the middleware
|
|
# caches previously-seen tokens for a configurable duration (in seconds). Set to
|
|
# -1 to disable caching completely. (integer value)
|
|
#token_cache_time = 300
|
|
|
|
# DEPRECATED: Determines the frequency at which the list of revoked tokens is
|
|
# retrieved from the Identity service (in seconds). A high number of revocation
|
|
# events combined with a low cache duration may significantly reduce
|
|
# performance. Only valid for PKI tokens. This option has been deprecated in the
|
|
# Ocata release and will be removed in the P release. (integer value)
|
|
# This option is deprecated for removal since Ocata.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: PKI token format is no longer supported.
|
|
#revocation_cache_time = 10
|
|
|
|
# (Optional) If defined, indicate whether token data should be authenticated or
|
|
# authenticated and encrypted. If MAC, token data is authenticated (with HMAC)
|
|
# in the cache. If ENCRYPT, token data is encrypted and authenticated in the
|
|
# cache. If the value is not one of these options or empty, auth_token will
|
|
# raise an exception on initialization. (string value)
|
|
# Possible values:
|
|
# None - <No description provided>
|
|
# MAC - <No description provided>
|
|
# ENCRYPT - <No description provided>
|
|
#memcache_security_strategy = None
|
|
|
|
# (Optional, mandatory if memcache_security_strategy is defined) This string is
|
|
# used for key derivation. (string value)
|
|
#memcache_secret_key = <None>
|
|
|
|
# (Optional) Number of seconds memcached server is considered dead before it is
|
|
# tried again. (integer value)
|
|
#memcache_pool_dead_retry = 300
|
|
|
|
# (Optional) Maximum total number of open connections to every memcached server.
|
|
# (integer value)
|
|
#memcache_pool_maxsize = 10
|
|
|
|
# (Optional) Socket timeout in seconds for communicating with a memcached
|
|
# server. (integer value)
|
|
#memcache_pool_socket_timeout = 3
|
|
|
|
# (Optional) Number of seconds a connection to memcached is held unused in the
|
|
# pool before it is closed. (integer value)
|
|
#memcache_pool_unused_timeout = 60
|
|
|
|
# (Optional) Number of seconds that an operation will wait to get a memcached
|
|
# client connection from the pool. (integer value)
|
|
#memcache_pool_conn_get_timeout = 10
|
|
|
|
# (Optional) Use the advanced (eventlet safe) memcached client pool. The
|
|
# advanced pool will only work under python 2.x. (boolean value)
|
|
#memcache_use_advanced_pool = false
|
|
|
|
# (Optional) Indicate whether to set the X-Service-Catalog header. If False,
|
|
# middleware will not ask for service catalog on token validation and will not
|
|
# set the X-Service-Catalog header. (boolean value)
|
|
#include_service_catalog = true
|
|
|
|
# Used to control the use and type of token binding. Can be set to: "disabled"
|
|
# to not check token binding. "permissive" (default) to validate binding
|
|
# information if the bind type is of a form known to the server and ignore it if
|
|
# not. "strict" like "permissive" but if the bind type is unknown the token will
|
|
# be rejected. "required" any form of token binding is needed to be allowed.
|
|
# Finally the name of a binding method that must be present in tokens. (string
|
|
# value)
|
|
#enforce_token_bind = permissive
|
|
|
|
# DEPRECATED: If true, the revocation list will be checked for cached tokens.
|
|
# This requires that PKI tokens are configured on the identity server. (boolean
|
|
# value)
|
|
# This option is deprecated for removal since Ocata.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: PKI token format is no longer supported.
|
|
#check_revocations_for_cached = false
|
|
|
|
# DEPRECATED: Hash algorithms to use for hashing PKI tokens. This may be a
|
|
# single algorithm or multiple. The algorithms are those supported by Python
|
|
# standard hashlib.new(). The hashes will be tried in the order given, so put
|
|
# the preferred one first for performance. The result of the first hash will be
|
|
# stored in the cache. This will typically be set to multiple values only while
|
|
# migrating from a less secure algorithm to a more secure one. Once all the old
|
|
# tokens are expired this option should be set to a single value for better
|
|
# performance. (list value)
|
|
# This option is deprecated for removal since Ocata.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: PKI token format is no longer supported.
|
|
#hash_algorithms = md5
|
|
|
|
# A choice of roles that must be present in a service token. Service tokens are
|
|
# allowed to request that an expired token can be used and so this check should
|
|
# tightly control that only actual services should be sending this token. Roles
|
|
# here are applied as an ANY check so any role in this list must be present. For
|
|
# backwards compatibility reasons this currently only affects the allow_expired
|
|
# check. (list value)
|
|
#service_token_roles = service
|
|
|
|
# For backwards compatibility reasons we must let valid service tokens pass that
|
|
# don't pass the service_token_roles check as valid. Setting this true will
|
|
# become the default in a future release and should be enabled if possible.
|
|
# (boolean value)
|
|
#service_token_roles_required = false
|
|
|
|
# Authentication type to load (string value)
|
|
# Deprecated group/name - [keystone_authtoken]/auth_plugin
|
|
#auth_type = <None>
|
|
|
|
# Config Section from which to load plugin specific options (string value)
|
|
#auth_section = <None>
|
|
|
|
|
|
[matchmaker_redis]
|
|
|
|
#
|
|
# From oslo.messaging
|
|
#
|
|
|
|
# DEPRECATED: Host to locate redis. (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Replaced by [DEFAULT]/transport_url
|
|
#host = 127.0.0.1
|
|
|
|
# DEPRECATED: Use this port to connect to redis host. (port value)
|
|
# Minimum value: 0
|
|
# Maximum value: 65535
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Replaced by [DEFAULT]/transport_url
|
|
#port = 6379
|
|
|
|
# DEPRECATED: Password for Redis server (optional). (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Replaced by [DEFAULT]/transport_url
|
|
#password =
|
|
|
|
# DEPRECATED: List of Redis Sentinel hosts (fault tolerance mode), e.g.,
|
|
# [host:port, host1:port ... ] (list value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Replaced by [DEFAULT]/transport_url
|
|
#sentinel_hosts =
|
|
|
|
# Redis replica set name. (string value)
|
|
#sentinel_group_name = oslo-messaging-zeromq
|
|
|
|
# Time in ms to wait between connection attempts. (integer value)
|
|
#wait_timeout = 2000
|
|
|
|
# Time in ms to wait before the transaction is killed. (integer value)
|
|
#check_timeout = 20000
|
|
|
|
# Timeout in ms on blocking socket operations. (integer value)
|
|
#socket_timeout = 10000
|
|
|
|
|
|
[oslo_concurrency]
|
|
|
|
#
|
|
# From oslo.concurrency
|
|
#
|
|
|
|
# Enables or disables inter-process locks. (boolean value)
|
|
#disable_process_locking = false
|
|
|
|
# Directory to use for lock files. For security, the specified directory should
|
|
# only be writable by the user running the processes that need locking. Defaults
|
|
# to environment variable OSLO_LOCK_PATH. If external locks are used, a lock
|
|
# path must be set. (string value)
|
|
#lock_path = <None>
|
|
|
|
|
|
[oslo_messaging_amqp]
|
|
|
|
#
|
|
# From oslo.messaging
|
|
#
|
|
|
|
# Name for the AMQP container. must be globally unique. Defaults to a generated
|
|
# UUID (string value)
|
|
#container_name = <None>
|
|
|
|
# Timeout for inactive connections (in seconds) (integer value)
|
|
#idle_timeout = 0
|
|
|
|
# Debug: dump AMQP frames to stdout (boolean value)
|
|
#trace = false
|
|
|
|
# Attempt to connect via SSL. If no other ssl-related parameters are given, it
|
|
# will use the system's CA-bundle to verify the server's certificate. (boolean
|
|
# value)
|
|
#ssl = false
|
|
|
|
# CA certificate PEM file used to verify the server's certificate (string value)
|
|
#ssl_ca_file =
|
|
|
|
# Self-identifying certificate PEM file for client authentication (string value)
|
|
#ssl_cert_file =
|
|
|
|
# Private key PEM file used to sign ssl_cert_file certificate (optional) (string
|
|
# value)
|
|
#ssl_key_file =
|
|
|
|
# Password for decrypting ssl_key_file (if encrypted) (string value)
|
|
#ssl_key_password = <None>
|
|
|
|
# By default SSL checks that the name in the server's certificate matches the
|
|
# hostname in the transport_url. In some configurations it may be preferable to
|
|
# use the virtual hostname instead, for example if the server uses the Server
|
|
# Name Indication TLS extension (rfc6066) to provide a certificate per virtual
|
|
# host. Set ssl_verify_vhost to True if the server's SSL certificate uses the
|
|
# virtual host name instead of the DNS name. (boolean value)
|
|
#ssl_verify_vhost = false
|
|
|
|
# DEPRECATED: Accept clients using either SSL or plain TCP (boolean value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Not applicable - not a SSL server
|
|
#allow_insecure_clients = false
|
|
|
|
# Space separated list of acceptable SASL mechanisms (string value)
|
|
#sasl_mechanisms =
|
|
|
|
# Path to directory that contains the SASL configuration (string value)
|
|
#sasl_config_dir =
|
|
|
|
# Name of configuration file (without .conf suffix) (string value)
|
|
#sasl_config_name =
|
|
|
|
# SASL realm to use if no realm present in username (string value)
|
|
#sasl_default_realm =
|
|
|
|
# DEPRECATED: User name for message broker authentication (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Should use configuration option transport_url to provide the username.
|
|
#username =
|
|
|
|
# DEPRECATED: Password for message broker authentication (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Should use configuration option transport_url to provide the password.
|
|
#password =
|
|
|
|
# Seconds to pause before attempting to re-connect. (integer value)
|
|
# Minimum value: 1
|
|
#connection_retry_interval = 1
|
|
|
|
# Increase the connection_retry_interval by this many seconds after each
|
|
# unsuccessful failover attempt. (integer value)
|
|
# Minimum value: 0
|
|
#connection_retry_backoff = 2
|
|
|
|
# Maximum limit for connection_retry_interval + connection_retry_backoff
|
|
# (integer value)
|
|
# Minimum value: 1
|
|
#connection_retry_interval_max = 30
|
|
|
|
# Time to pause between re-connecting an AMQP 1.0 link that failed due to a
|
|
# recoverable error. (integer value)
|
|
# Minimum value: 1
|
|
#link_retry_delay = 10
|
|
|
|
# The maximum number of attempts to re-send a reply message which failed due to
|
|
# a recoverable error. (integer value)
|
|
# Minimum value: -1
|
|
#default_reply_retry = 0
|
|
|
|
# The deadline for an rpc reply message delivery. (integer value)
|
|
# Minimum value: 5
|
|
#default_reply_timeout = 30
|
|
|
|
# The deadline for an rpc cast or call message delivery. Only used when caller
|
|
# does not provide a timeout expiry. (integer value)
|
|
# Minimum value: 5
|
|
#default_send_timeout = 30
|
|
|
|
# The deadline for a sent notification message delivery. Only used when caller
|
|
# does not provide a timeout expiry. (integer value)
|
|
# Minimum value: 5
|
|
#default_notify_timeout = 30
|
|
|
|
# The duration to schedule a purge of idle sender links. Detach link after
|
|
# expiry. (integer value)
|
|
# Minimum value: 1
|
|
#default_sender_link_timeout = 600
|
|
|
|
# Indicates the addressing mode used by the driver.
|
|
# Permitted values:
|
|
# 'legacy' - use legacy non-routable addressing
|
|
# 'routable' - use routable addresses
|
|
# 'dynamic' - use legacy addresses if the message bus does not support routing
|
|
# otherwise use routable addressing (string value)
|
|
#addressing_mode = dynamic
|
|
|
|
# Enable virtual host support for those message buses that do not natively
|
|
# support virtual hosting (such as qpidd). When set to true the virtual host
|
|
# name will be added to all message bus addresses, effectively creating a
|
|
# private 'subnet' per virtual host. Set to False if the message bus supports
|
|
# virtual hosting using the 'hostname' field in the AMQP 1.0 Open performative
|
|
# as the name of the virtual host. (boolean value)
|
|
#pseudo_vhost = true
|
|
|
|
# address prefix used when sending to a specific server (string value)
|
|
#server_request_prefix = exclusive
|
|
|
|
# address prefix used when broadcasting to all servers (string value)
|
|
#broadcast_prefix = broadcast
|
|
|
|
# address prefix when sending to any server in group (string value)
|
|
#group_request_prefix = unicast
|
|
|
|
# Address prefix for all generated RPC addresses (string value)
|
|
#rpc_address_prefix = openstack.org/om/rpc
|
|
|
|
# Address prefix for all generated Notification addresses (string value)
|
|
#notify_address_prefix = openstack.org/om/notify
|
|
|
|
# Appended to the address prefix when sending a fanout message. Used by the
|
|
# message bus to identify fanout messages. (string value)
|
|
#multicast_address = multicast
|
|
|
|
# Appended to the address prefix when sending to a particular RPC/Notification
|
|
# server. Used by the message bus to identify messages sent to a single
|
|
# destination. (string value)
|
|
#unicast_address = unicast
|
|
|
|
# Appended to the address prefix when sending to a group of consumers. Used by
|
|
# the message bus to identify messages that should be delivered in a round-robin
|
|
# fashion across consumers. (string value)
|
|
#anycast_address = anycast
|
|
|
|
# Exchange name used in notification addresses.
|
|
# Exchange name resolution precedence:
|
|
# Target.exchange if set
|
|
# else default_notification_exchange if set
|
|
# else control_exchange if set
|
|
# else 'notify' (string value)
|
|
#default_notification_exchange = <None>
|
|
|
|
# Exchange name used in RPC addresses.
|
|
# Exchange name resolution precedence:
|
|
# Target.exchange if set
|
|
# else default_rpc_exchange if set
|
|
# else control_exchange if set
|
|
# else 'rpc' (string value)
|
|
#default_rpc_exchange = <None>
|
|
|
|
# Window size for incoming RPC Reply messages. (integer value)
|
|
# Minimum value: 1
|
|
#reply_link_credit = 200
|
|
|
|
# Window size for incoming RPC Request messages (integer value)
|
|
# Minimum value: 1
|
|
#rpc_server_credit = 100
|
|
|
|
# Window size for incoming Notification messages (integer value)
|
|
# Minimum value: 1
|
|
#notify_server_credit = 100
|
|
|
|
# Send messages of this type pre-settled.
|
|
# Pre-settled messages will not receive acknowledgement
|
|
# from the peer. Note well: pre-settled messages may be
|
|
# silently discarded if the delivery fails.
|
|
# Permitted values:
|
|
# 'rpc-call' - send RPC Calls pre-settled
|
|
# 'rpc-reply'- send RPC Replies pre-settled
|
|
# 'rpc-cast' - Send RPC Casts pre-settled
|
|
# 'notify' - Send Notifications pre-settled
|
|
# (multi valued)
|
|
#pre_settled = rpc-cast
|
|
#pre_settled = rpc-reply
|
|
|
|
|
|
[oslo_messaging_kafka]
|
|
|
|
#
|
|
# From oslo.messaging
|
|
#
|
|
|
|
# DEPRECATED: Default Kafka broker Host (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Replaced by [DEFAULT]/transport_url
|
|
#kafka_default_host = localhost
|
|
|
|
# DEPRECATED: Default Kafka broker Port (port value)
|
|
# Minimum value: 0
|
|
# Maximum value: 65535
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Replaced by [DEFAULT]/transport_url
|
|
#kafka_default_port = 9092
|
|
|
|
# Max fetch bytes of Kafka consumer (integer value)
|
|
#kafka_max_fetch_bytes = 1048576
|
|
|
|
# Default timeout(s) for Kafka consumers (floating point value)
|
|
#kafka_consumer_timeout = 1.0
|
|
|
|
# DEPRECATED: Pool Size for Kafka Consumers (integer value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Driver no longer uses connection pool.
|
|
#pool_size = 10
|
|
|
|
# DEPRECATED: The pool size limit for connections expiration policy (integer
|
|
# value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Driver no longer uses connection pool.
|
|
#conn_pool_min_size = 2
|
|
|
|
# DEPRECATED: The time-to-live in sec of idle connections in the pool (integer
|
|
# value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Driver no longer uses connection pool.
|
|
#conn_pool_ttl = 1200
|
|
|
|
# Group id for Kafka consumer. Consumers in one group will coordinate message
|
|
# consumption (string value)
|
|
#consumer_group = oslo_messaging_consumer
|
|
|
|
# Upper bound on the delay for KafkaProducer batching in seconds (floating point
|
|
# value)
|
|
#producer_batch_timeout = 0.0
|
|
|
|
# Size of batch for the producer async send (integer value)
|
|
#producer_batch_size = 16384
|
|
|
|
# Enable asynchronous consumer commits (boolean value)
|
|
#enable_auto_commit = false
|
|
|
|
# The maximum number of records returned in a poll call (integer value)
|
|
#max_poll_records = 500
|
|
|
|
# Protocol used to communicate with brokers (string value)
|
|
# Possible values:
|
|
# PLAINTEXT - <No description provided>
|
|
# SASL_PLAINTEXT - <No description provided>
|
|
# SSL - <No description provided>
|
|
# SASL_SSL - <No description provided>
|
|
#security_protocol = PLAINTEXT
|
|
|
|
# Mechanism when security protocol is SASL (string value)
|
|
#sasl_mechanism = PLAIN
|
|
|
|
# CA certificate PEM file used to verify the server certificate (string value)
|
|
#ssl_cafile =
|
|
|
|
|
|
[oslo_messaging_notifications]
|
|
|
|
#
|
|
# From oslo.messaging
|
|
#
|
|
|
|
# The Drivers(s) to handle sending notifications. Possible values are messaging,
|
|
# messagingv2, routing, log, test, noop (multi valued)
|
|
# Deprecated group/name - [DEFAULT]/notification_driver
|
|
#driver =
|
|
|
|
# A URL representing the messaging driver to use for notifications. If not set,
|
|
# we fall back to the same configuration used for RPC. (string value)
|
|
# Deprecated group/name - [DEFAULT]/notification_transport_url
|
|
#transport_url = <None>
|
|
|
|
# AMQP topic used for OpenStack notifications. (list value)
|
|
# Deprecated group/name - [rpc_notifier2]/topics
|
|
# Deprecated group/name - [DEFAULT]/notification_topics
|
|
#topics = notifications
|
|
|
|
# The maximum number of attempts to re-send a notification message which failed
|
|
# to be delivered due to a recoverable error. 0 - No retry, -1 - indefinite
|
|
# (integer value)
|
|
#retry = -1
|
|
|
|
|
|
[oslo_messaging_rabbit]
|
|
|
|
#
|
|
# From oslo.messaging
|
|
#
|
|
|
|
# Use durable queues in AMQP. (boolean value)
|
|
# Deprecated group/name - [DEFAULT]/amqp_durable_queues
|
|
# Deprecated group/name - [DEFAULT]/rabbit_durable_queues
|
|
#amqp_durable_queues = false
|
|
|
|
# Auto-delete queues in AMQP. (boolean value)
|
|
#amqp_auto_delete = false
|
|
|
|
# Connect over SSL. (boolean value)
|
|
# Deprecated group/name - [oslo_messaging_rabbit]/rabbit_use_ssl
|
|
#ssl = false
|
|
|
|
# SSL version to use (valid only if SSL enabled). Valid values are TLSv1 and
|
|
# SSLv23. SSLv2, SSLv3, TLSv1_1, and TLSv1_2 may be available on some
|
|
# distributions. (string value)
|
|
# Deprecated group/name - [oslo_messaging_rabbit]/kombu_ssl_version
|
|
#ssl_version =
|
|
|
|
# SSL key file (valid only if SSL enabled). (string value)
|
|
# Deprecated group/name - [oslo_messaging_rabbit]/kombu_ssl_keyfile
|
|
#ssl_key_file =
|
|
|
|
# SSL cert file (valid only if SSL enabled). (string value)
|
|
# Deprecated group/name - [oslo_messaging_rabbit]/kombu_ssl_certfile
|
|
#ssl_cert_file =
|
|
|
|
# SSL certification authority file (valid only if SSL enabled). (string value)
|
|
# Deprecated group/name - [oslo_messaging_rabbit]/kombu_ssl_ca_certs
|
|
#ssl_ca_file =
|
|
|
|
# How long to wait before reconnecting in response to an AMQP consumer cancel
|
|
# notification. (floating point value)
|
|
#kombu_reconnect_delay = 1.0
|
|
|
|
# EXPERIMENTAL: Possible values are: gzip, bz2. If not set compression will not
|
|
# be used. This option may not be available in future versions. (string value)
|
|
#kombu_compression = <None>
|
|
|
|
# How long to wait a missing client before abandoning to send it its replies.
|
|
# This value should not be longer than rpc_response_timeout. (integer value)
|
|
# Deprecated group/name - [oslo_messaging_rabbit]/kombu_reconnect_timeout
|
|
#kombu_missing_consumer_retry_timeout = 60
|
|
|
|
# Determines how the next RabbitMQ node is chosen in case the one we are
|
|
# currently connected to becomes unavailable. Takes effect only if more than one
|
|
# RabbitMQ node is provided in config. (string value)
|
|
# Possible values:
|
|
# round-robin - <No description provided>
|
|
# shuffle - <No description provided>
|
|
#kombu_failover_strategy = round-robin
|
|
|
|
# DEPRECATED: The RabbitMQ broker address where a single node is used. (string
|
|
# value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Replaced by [DEFAULT]/transport_url
|
|
#rabbit_host = localhost
|
|
|
|
# DEPRECATED: The RabbitMQ broker port where a single node is used. (port value)
|
|
# Minimum value: 0
|
|
# Maximum value: 65535
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Replaced by [DEFAULT]/transport_url
|
|
#rabbit_port = 5672
|
|
|
|
# DEPRECATED: RabbitMQ HA cluster host:port pairs. (list value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Replaced by [DEFAULT]/transport_url
|
|
#rabbit_hosts = $rabbit_host:$rabbit_port
|
|
|
|
# DEPRECATED: The RabbitMQ userid. (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Replaced by [DEFAULT]/transport_url
|
|
#rabbit_userid = guest
|
|
|
|
# DEPRECATED: The RabbitMQ password. (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Replaced by [DEFAULT]/transport_url
|
|
#rabbit_password = guest
|
|
|
|
# The RabbitMQ login method. (string value)
|
|
# Possible values:
|
|
# PLAIN - <No description provided>
|
|
# AMQPLAIN - <No description provided>
|
|
# RABBIT-CR-DEMO - <No description provided>
|
|
#rabbit_login_method = AMQPLAIN
|
|
|
|
# DEPRECATED: The RabbitMQ virtual host. (string value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
# Reason: Replaced by [DEFAULT]/transport_url
|
|
#rabbit_virtual_host = /
|
|
|
|
# How frequently to retry connecting with RabbitMQ. (integer value)
|
|
#rabbit_retry_interval = 1
|
|
|
|
# How long to backoff for between retries when connecting to RabbitMQ. (integer
|
|
# value)
|
|
#rabbit_retry_backoff = 2
|
|
|
|
# Maximum interval of RabbitMQ connection retries. Default is 30 seconds.
|
|
# (integer value)
|
|
#rabbit_interval_max = 30
|
|
|
|
# DEPRECATED: Maximum number of RabbitMQ connection retries. Default is 0
|
|
# (infinite retry count). (integer value)
|
|
# This option is deprecated for removal.
|
|
# Its value may be silently ignored in the future.
|
|
#rabbit_max_retries = 0
|
|
|
|
# Try to use HA queues in RabbitMQ (x-ha-policy: all). If you change this
|
|
# option, you must wipe the RabbitMQ database. In RabbitMQ 3.0, queue mirroring
|
|
# is no longer controlled by the x-ha-policy argument when declaring a queue. If
|
|
# you just want to make sure that all queues (except those with auto-generated
|
|
# names) are mirrored across all nodes, run: "rabbitmqctl set_policy HA
|
|
# '^(?!amq\.).*' '{"ha-mode": "all"}' " (boolean value)
|
|
#rabbit_ha_queues = false
|
|
|
|
# Positive integer representing duration in seconds for queue TTL (x-expires).
|
|
# Queues which are unused for the duration of the TTL are automatically deleted.
|
|
# The parameter affects only reply and fanout queues. (integer value)
|
|
# Minimum value: 1
|
|
#rabbit_transient_queues_ttl = 1800
|
|
|
|
# Specifies the number of messages to prefetch. Setting to zero allows unlimited
|
|
# messages. (integer value)
|
|
#rabbit_qos_prefetch_count = 0
|
|
|
|
# Number of seconds after which the Rabbit broker is considered down if
|
|
# heartbeat's keep-alive fails (0 disable the heartbeat). EXPERIMENTAL (integer
|
|
# value)
|
|
#heartbeat_timeout_threshold = 60
|
|
|
|
# How often times during the heartbeat_timeout_threshold we check the heartbeat.
|
|
# (integer value)
|
|
#heartbeat_rate = 2
|
|
|
|
|
|
[oslo_messaging_zmq]
|
|
|
|
#
|
|
# From oslo.messaging
|
|
#
|
|
|
|
# ZeroMQ bind address. Should be a wildcard (*), an ethernet interface, or IP.
|
|
# The "host" option should point or resolve to this address. (string value)
|
|
#rpc_zmq_bind_address = *
|
|
|
|
# MatchMaker driver. (string value)
|
|
# Possible values:
|
|
# redis - <No description provided>
|
|
# sentinel - <No description provided>
|
|
# dummy - <No description provided>
|
|
#rpc_zmq_matchmaker = redis
|
|
|
|
# Number of ZeroMQ contexts, defaults to 1. (integer value)
|
|
#rpc_zmq_contexts = 1
|
|
|
|
# Maximum number of ingress messages to locally buffer per topic. Default is
|
|
# unlimited. (integer value)
|
|
#rpc_zmq_topic_backlog = <None>
|
|
|
|
# Directory for holding IPC sockets. (string value)
|
|
#rpc_zmq_ipc_dir = /var/run/openstack
|
|
|
|
# Name of this node. Must be a valid hostname, FQDN, or IP address. Must match
|
|
# "host" option, if running Nova. (string value)
|
|
#rpc_zmq_host = localhost
|
|
|
|
# Number of seconds to wait before all pending messages will be sent after
|
|
# closing a socket. The default value of -1 specifies an infinite linger period.
|
|
# The value of 0 specifies no linger period. Pending messages shall be discarded
|
|
# immediately when the socket is closed. Positive values specify an upper bound
|
|
# for the linger period. (integer value)
|
|
# Deprecated group/name - [DEFAULT]/rpc_cast_timeout
|
|
#zmq_linger = -1
|
|
|
|
# The default number of seconds that poll should wait. Poll raises timeout
|
|
# exception when timeout expired. (integer value)
|
|
#rpc_poll_timeout = 1
|
|
|
|
# Expiration timeout in seconds of a name service record about existing target (
|
|
# < 0 means no timeout). (integer value)
|
|
#zmq_target_expire = 300
|
|
|
|
# Update period in seconds of a name service record about existing target.
|
|
# (integer value)
|
|
#zmq_target_update = 180
|
|
|
|
# Use PUB/SUB pattern for fanout methods. PUB/SUB always uses proxy. (boolean
|
|
# value)
|
|
#use_pub_sub = false
|
|
|
|
# Use ROUTER remote proxy. (boolean value)
|
|
#use_router_proxy = false
|
|
|
|
# This option makes direct connections dynamic or static. It makes sense only
|
|
# with use_router_proxy=False which means to use direct connections for direct
|
|
# message types (ignored otherwise). (boolean value)
|
|
#use_dynamic_connections = false
|
|
|
|
# How many additional connections to a host will be made for failover reasons.
|
|
# This option is actual only in dynamic connections mode. (integer value)
|
|
#zmq_failover_connections = 2
|
|
|
|
# Minimal port number for random ports range. (port value)
|
|
# Minimum value: 0
|
|
# Maximum value: 65535
|
|
#rpc_zmq_min_port = 49153
|
|
|
|
# Maximal port number for random ports range. (integer value)
|
|
# Minimum value: 1
|
|
# Maximum value: 65536
|
|
#rpc_zmq_max_port = 65536
|
|
|
|
# Number of retries to find free port number before fail with ZMQBindError.
|
|
# (integer value)
|
|
#rpc_zmq_bind_port_retries = 100
|
|
|
|
# Default serialization mechanism for serializing/deserializing
|
|
# outgoing/incoming messages (string value)
|
|
# Possible values:
|
|
# json - <No description provided>
|
|
# msgpack - <No description provided>
|
|
#rpc_zmq_serialization = json
|
|
|
|
# This option configures round-robin mode in zmq socket. True means not keeping
|
|
# a queue when server side disconnects. False means to keep queue and messages
|
|
# even if server is disconnected, when the server appears we send all
|
|
# accumulated messages to it. (boolean value)
|
|
#zmq_immediate = true
|
|
|
|
# Enable/disable TCP keepalive (KA) mechanism. The default value of -1 (or any
|
|
# other negative value) means to skip any overrides and leave it to OS default;
|
|
# 0 and 1 (or any other positive value) mean to disable and enable the option
|
|
# respectively. (integer value)
|
|
#zmq_tcp_keepalive = -1
|
|
|
|
# The duration between two keepalive transmissions in idle condition. The unit
|
|
# is platform dependent, for example, seconds in Linux, milliseconds in Windows
|
|
# etc. The default value of -1 (or any other negative value and 0) means to skip
|
|
# any overrides and leave it to OS default. (integer value)
|
|
#zmq_tcp_keepalive_idle = -1
|
|
|
|
# The number of retransmissions to be carried out before declaring that remote
|
|
# end is not available. The default value of -1 (or any other negative value and
|
|
# 0) means to skip any overrides and leave it to OS default. (integer value)
|
|
#zmq_tcp_keepalive_cnt = -1
|
|
|
|
# The duration between two successive keepalive retransmissions, if
|
|
# acknowledgement to the previous keepalive transmission is not received. The
|
|
# unit is platform dependent, for example, seconds in Linux, milliseconds in
|
|
# Windows etc. The default value of -1 (or any other negative value and 0) means
|
|
# to skip any overrides and leave it to OS default. (integer value)
|
|
#zmq_tcp_keepalive_intvl = -1
|
|
|
|
# Maximum number of (green) threads to work concurrently. (integer value)
|
|
#rpc_thread_pool_size = 100
|
|
|
|
# Expiration timeout in seconds of a sent/received message after which it is not
|
|
# tracked anymore by a client/server. (integer value)
|
|
#rpc_message_ttl = 300
|
|
|
|
# Wait for message acknowledgements from receivers. This mechanism works only
|
|
# via proxy without PUB/SUB. (boolean value)
|
|
#rpc_use_acks = false
|
|
|
|
# Number of seconds to wait for an ack from a cast/call. After each retry
|
|
# attempt this timeout is multiplied by some specified multiplier. (integer
|
|
# value)
|
|
#rpc_ack_timeout_base = 15
|
|
|
|
# Number to multiply base ack timeout by after each retry attempt. (integer
|
|
# value)
|
|
#rpc_ack_timeout_multiplier = 2
|
|
|
|
# Default number of message sending attempts in case of any problems occurred:
|
|
# positive value N means at most N retries, 0 means no retries, None or -1 (or
|
|
# any other negative values) mean to retry forever. This option is used only if
|
|
# acknowledgments are enabled. (integer value)
|
|
#rpc_retry_attempts = 3
|
|
|
|
# List of publisher hosts SubConsumer can subscribe on. This option has higher
|
|
# priority then the default publishers list taken from the matchmaker. (list
|
|
# value)
|
|
#subscribe_on =
|
|
|
|
|
|
[oslo_middleware]
|
|
|
|
#
|
|
# From oslo.middleware.http_proxy_to_wsgi
|
|
#
|
|
|
|
# Whether the application is behind a proxy or not. This determines if the
|
|
# middleware should parse the headers or not. (boolean value)
|
|
#enable_proxy_headers_parsing = false
|
|
|
|
|
|
[oslo_policy]
|
|
|
|
#
|
|
# From oslo.policy
|
|
#
|
|
|
|
# This option controls whether or not to enforce scope when evaluating policies.
|
|
# If ``True``, the scope of the token used in the request is compared to the
|
|
# ``scope_types`` of the policy being enforced. If the scopes do not match, an
|
|
# ``InvalidScope`` exception will be raised. If ``False``, a message will be
|
|
# logged informing operators that policies are being invoked with mismatching
|
|
# scope. (boolean value)
|
|
#enforce_scope = false
|
|
|
|
# The file that defines policies. (string value)
|
|
#policy_file = policy.json
|
|
|
|
# Default rule. Enforced when a requested rule is not found. (string value)
|
|
#policy_default_rule = default
|
|
|
|
# Directories where policy configuration files are stored. They can be relative
|
|
# to any directory in the search path defined by the config_dir option, or
|
|
# absolute paths. The file defined by policy_file must exist for these
|
|
# directories to be searched. Missing or empty directories are ignored. (multi
|
|
# valued)
|
|
#policy_dirs = policy.d
|
|
|
|
# Content Type to send and receive data for REST based policy check (string
|
|
# value)
|
|
# Possible values:
|
|
# application/x-www-form-urlencoded - <No description provided>
|
|
# application/json - <No description provided>
|
|
#remote_content_type = application/x-www-form-urlencoded
|
|
|
|
# server identity verification for REST based policy check (boolean value)
|
|
#remote_ssl_verify_server_crt = false
|
|
|
|
# Absolute path to ca cert file for REST based policy check (string value)
|
|
#remote_ssl_ca_crt_file = <None>
|
|
|
|
# Absolute path to client cert for REST based policy check (string value)
|
|
#remote_ssl_client_crt_file = <None>
|
|
|
|
# Absolute path client key file REST based policy check (string value)
|
|
#remote_ssl_client_key_file = <None>
|
|
|
|
|
|
[paste_deploy]
|
|
|
|
#
|
|
# From glance.api
|
|
#
|
|
|
|
#
|
|
# Deployment flavor to use in the server application pipeline.
|
|
#
|
|
# Provide a string value representing the appropriate deployment
|
|
# flavor used in the server application pipleline. This is typically
|
|
# the partial name of a pipeline in the paste configuration file with
|
|
# the service name removed.
|
|
#
|
|
# For example, if your paste section name in the paste configuration
|
|
# file is [pipeline:glance-api-keystone], set ``flavor`` to
|
|
# ``keystone``.
|
|
#
|
|
# Possible values:
|
|
# * String value representing a partial pipeline name.
|
|
#
|
|
# Related Options:
|
|
# * config_file
|
|
#
|
|
# (string value)
|
|
#flavor = keystone
|
|
|
|
#
|
|
# Name of the paste configuration file.
|
|
#
|
|
# Provide a string value representing the name of the paste
|
|
# configuration file to use for configuring piplelines for
|
|
# server application deployments.
|
|
#
|
|
# NOTES:
|
|
# * Provide the name or the path relative to the glance directory
|
|
# for the paste configuration file and not the absolute path.
|
|
# * The sample paste configuration file shipped with Glance need
|
|
# not be edited in most cases as it comes with ready-made
|
|
# pipelines for all common deployment flavors.
|
|
#
|
|
# If no value is specified for this option, the ``paste.ini`` file
|
|
# with the prefix of the corresponding Glance service's configuration
|
|
# file name will be searched for in the known configuration
|
|
# directories. (For example, if this option is missing from or has no
|
|
# value set in ``glance-api.conf``, the service will look for a file
|
|
# named ``glance-api-paste.ini``.) If the paste configuration file is
|
|
# not found, the service will not start.
|
|
#
|
|
# Possible values:
|
|
# * A string value representing the name of the paste configuration
|
|
# file.
|
|
#
|
|
# Related Options:
|
|
# * flavor
|
|
#
|
|
# (string value)
|
|
#config_file = glance-api-paste.ini
|
|
|
|
|
|
[profiler]
|
|
|
|
#
|
|
# From glance.api
|
|
#
|
|
|
|
#
|
|
# Enable the profiling for all services on this node.
|
|
#
|
|
# Default value is False (fully disable the profiling feature).
|
|
#
|
|
# Possible values:
|
|
#
|
|
# * True: Enables the feature
|
|
# * False: Disables the feature. The profiling cannot be started via this
|
|
# project
|
|
# operations. If the profiling is triggered by another project, this project
|
|
# part will be empty.
|
|
# (boolean value)
|
|
# Deprecated group/name - [profiler]/profiler_enabled
|
|
#enabled = false
|
|
|
|
#
|
|
# Enable SQL requests profiling in services.
|
|
#
|
|
# Default value is False (SQL requests won't be traced).
|
|
#
|
|
# Possible values:
|
|
#
|
|
# * True: Enables SQL requests profiling. Each SQL query will be part of the
|
|
# trace and can the be analyzed by how much time was spent for that.
|
|
# * False: Disables SQL requests profiling. The spent time is only shown on a
|
|
# higher level of operations. Single SQL queries cannot be analyzed this way.
|
|
# (boolean value)
|
|
#trace_sqlalchemy = false
|
|
|
|
#
|
|
# Secret key(s) to use for encrypting context data for performance profiling.
|
|
#
|
|
# This string value should have the following format: <key1>[,<key2>,...<keyn>],
|
|
# where each key is some random string. A user who triggers the profiling via
|
|
# the REST API has to set one of these keys in the headers of the REST API call
|
|
# to include profiling results of this node for this particular project.
|
|
#
|
|
# Both "enabled" flag and "hmac_keys" config options should be set to enable
|
|
# profiling. Also, to generate correct profiling information across all services
|
|
# at least one key needs to be consistent between OpenStack projects. This
|
|
# ensures it can be used from client side to generate the trace, containing
|
|
# information from all possible resources.
|
|
# (string value)
|
|
#hmac_keys = SECRET_KEY
|
|
|
|
#
|
|
# Connection string for a notifier backend.
|
|
#
|
|
# Default value is ``messaging://`` which sets the notifier to oslo_messaging.
|
|
#
|
|
# Examples of possible values:
|
|
#
|
|
# * ``messaging://`` - use oslo_messaging driver for sending spans.
|
|
# * ``redis://127.0.0.1:6379`` - use redis driver for sending spans.
|
|
# * ``mongodb://127.0.0.1:27017`` - use mongodb driver for sending spans.
|
|
# * ``elasticsearch://127.0.0.1:9200`` - use elasticsearch driver for sending
|
|
# spans.
|
|
# * ``jaeger://127.0.0.1:6831`` - use jaeger tracing as driver for sending
|
|
# spans.
|
|
# (string value)
|
|
#connection_string = messaging://
|
|
|
|
#
|
|
# Document type for notification indexing in elasticsearch.
|
|
# (string value)
|
|
#es_doc_type = notification
|
|
|
|
#
|
|
# This parameter is a time value parameter (for example: es_scroll_time=2m),
|
|
# indicating for how long the nodes that participate in the search will maintain
|
|
# relevant resources in order to continue and support it.
|
|
# (string value)
|
|
#es_scroll_time = 2m
|
|
|
|
#
|
|
# Elasticsearch splits large requests in batches. This parameter defines
|
|
# maximum size of each batch (for example: es_scroll_size=10000).
|
|
# (integer value)
|
|
#es_scroll_size = 10000
|
|
|
|
#
|
|
# Redissentinel provides a timeout option on the connections.
|
|
# This parameter defines that timeout (for example: socket_timeout=0.1).
|
|
# (floating point value)
|
|
#socket_timeout = 0.1
|
|
|
|
#
|
|
# Redissentinel uses a service name to identify a master redis service.
|
|
# This parameter defines the name (for example:
|
|
# ``sentinal_service_name=mymaster``).
|
|
# (string value)
|
|
#sentinel_service_name = mymaster
|
|
|
|
#
|
|
# Enable filter traces that contain error/exception to a separated place.
|
|
#
|
|
# Default value is set to False.
|
|
#
|
|
# Possible values:
|
|
#
|
|
# * True: Enable filter traces that contain error/exception.
|
|
# * False: Disable the filter.
|
|
# (boolean value)
|
|
#filter_error_trace = false
|
|
|
|
|
|
[store_type_location_strategy]
|
|
|
|
#
|
|
# From glance.api
|
|
#
|
|
|
|
#
|
|
# Preference order of storage backends.
|
|
#
|
|
# Provide a comma separated list of store names in the order in
|
|
# which images should be retrieved from storage backends.
|
|
# These store names must be registered with the ``stores``
|
|
# configuration option.
|
|
#
|
|
# NOTE: The ``store_type_preference`` configuration option is applied
|
|
# only if ``store_type`` is chosen as a value for the
|
|
# ``location_strategy`` configuration option. An empty list will not
|
|
# change the location order.
|
|
#
|
|
# Possible values:
|
|
# * Empty list
|
|
# * Comma separated list of registered store names. Legal values are:
|
|
# * file
|
|
# * http
|
|
# * rbd
|
|
# * swift
|
|
# * sheepdog
|
|
# * cinder
|
|
# * vmware
|
|
#
|
|
# Related options:
|
|
# * location_strategy
|
|
# * stores
|
|
#
|
|
# (list value)
|
|
#store_type_preference =
|
|
|
|
|
|
[task]
|
|
|
|
#
|
|
# From glance.api
|
|
#
|
|
|
|
# Time in hours for which a task lives after, either succeeding or failing
|
|
# (integer value)
|
|
# Deprecated group/name - [DEFAULT]/task_time_to_live
|
|
#task_time_to_live = 48
|
|
|
|
#
|
|
# Task executor to be used to run task scripts.
|
|
#
|
|
# Provide a string value representing the executor to use for task
|
|
# executions. By default, ``TaskFlow`` executor is used.
|
|
#
|
|
# ``TaskFlow`` helps make task executions easy, consistent, scalable
|
|
# and reliable. It also enables creation of lightweight task objects
|
|
# and/or functions that are combined together into flows in a
|
|
# declarative manner.
|
|
#
|
|
# Possible values:
|
|
# * taskflow
|
|
#
|
|
# Related Options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
#task_executor = taskflow
|
|
|
|
#
|
|
# Absolute path to the work directory to use for asynchronous
|
|
# task operations.
|
|
#
|
|
# The directory set here will be used to operate over images -
|
|
# normally before they are imported in the destination store.
|
|
#
|
|
# NOTE: When providing a value for ``work_dir``, please make sure
|
|
# that enough space is provided for concurrent tasks to run
|
|
# efficiently without running out of space.
|
|
#
|
|
# A rough estimation can be done by multiplying the number of
|
|
# ``max_workers`` with an average image size (e.g 500MB). The image
|
|
# size estimation should be done based on the average size in your
|
|
# deployment. Note that depending on the tasks running you may need
|
|
# to multiply this number by some factor depending on what the task
|
|
# does. For example, you may want to double the available size if
|
|
# image conversion is enabled. All this being said, remember these
|
|
# are just estimations and you should do them based on the worst
|
|
# case scenario and be prepared to act in case they were wrong.
|
|
#
|
|
# Possible values:
|
|
# * String value representing the absolute path to the working
|
|
# directory
|
|
#
|
|
# Related Options:
|
|
# * None
|
|
#
|
|
# (string value)
|
|
#work_dir = /work_dir
|
|
|
|
|
|
[taskflow_executor]
|
|
|
|
#
|
|
# From glance.api
|
|
#
|
|
|
|
#
|
|
# Set the taskflow engine mode.
|
|
#
|
|
# Provide a string type value to set the mode in which the taskflow
|
|
# engine would schedule tasks to the workers on the hosts. Based on
|
|
# this mode, the engine executes tasks either in single or multiple
|
|
# threads. The possible values for this configuration option are:
|
|
# ``serial`` and ``parallel``. When set to ``serial``, the engine runs
|
|
# all the tasks in a single thread which results in serial execution
|
|
# of tasks. Setting this to ``parallel`` makes the engine run tasks in
|
|
# multiple threads. This results in parallel execution of tasks.
|
|
#
|
|
# Possible values:
|
|
# * serial
|
|
# * parallel
|
|
#
|
|
# Related options:
|
|
# * max_workers
|
|
#
|
|
# (string value)
|
|
# Possible values:
|
|
# serial - <No description provided>
|
|
# parallel - <No description provided>
|
|
#engine_mode = parallel
|
|
|
|
#
|
|
# Set the number of engine executable tasks.
|
|
#
|
|
# Provide an integer value to limit the number of workers that can be
|
|
# instantiated on the hosts. In other words, this number defines the
|
|
# number of parallel tasks that can be executed at the same time by
|
|
# the taskflow engine. This value can be greater than one when the
|
|
# engine mode is set to parallel.
|
|
#
|
|
# Possible values:
|
|
# * Integer value greater than or equal to 1
|
|
#
|
|
# Related options:
|
|
# * engine_mode
|
|
#
|
|
# (integer value)
|
|
# Minimum value: 1
|
|
# Deprecated group/name - [task]/eventlet_executor_pool_size
|
|
#max_workers = 10
|
|
|
|
#
|
|
# Set the desired image conversion format.
|
|
#
|
|
# Provide a valid image format to which you want images to be
|
|
# converted before they are stored for consumption by Glance.
|
|
# Appropriate image format conversions are desirable for specific
|
|
# storage backends in order to facilitate efficient handling of
|
|
# bandwidth and usage of the storage infrastructure.
|
|
#
|
|
# By default, ``conversion_format`` is not set and must be set
|
|
# explicitly in the configuration file.
|
|
#
|
|
# The allowed values for this option are ``raw``, ``qcow2`` and
|
|
# ``vmdk``. The ``raw`` format is the unstructured disk format and
|
|
# should be chosen when RBD or Ceph storage backends are used for
|
|
# image storage. ``qcow2`` is supported by the QEMU emulator that
|
|
# expands dynamically and supports Copy on Write. The ``vmdk`` is
|
|
# another common disk format supported by many common virtual machine
|
|
# monitors like VMWare Workstation.
|
|
#
|
|
# Possible values:
|
|
# * qcow2
|
|
# * raw
|
|
# * vmdk
|
|
#
|
|
# Related options:
|
|
# * disk_formats
|
|
#
|
|
# (string value)
|
|
# Possible values:
|
|
# qcow2 - <No description provided>
|
|
# raw - <No description provided>
|
|
# vmdk - <No description provided>
|
|
#conversion_format = raw
|