Refresh Glance example configs for Train

Change-Id: I9930dc0fa1c7da883ecb1b77a52a492e2d3e7baa
This commit is contained in:
Erno Kuvaja 2019-10-01 10:38:27 +01:00
parent feb8ebd75b
commit 0cefe020df
4 changed files with 6 additions and 2182 deletions

View File

@ -579,7 +579,7 @@
# (string value)
#digest_algorithm = sha256
# DEPRECATED:
#
# The URL provides location where the temporary data will be stored
#
# This option is for Glance internal use only. Glance will save the
@ -596,30 +596,13 @@
# NOTE: The staging path must be on shared filesystem available to all
# Glance API nodes.
#
# NOTE: If you are using the Glance multistore feature, you *must*
# use a filesystem store instead of this setting. See the
# ``[os_glance_staging_store]`` section of this configuration file
# for more information.
#
# Possible values:
# * String starting with 'file://' followed by absolute FS path
#
# Related options:
# * [task]/work_dir
# * enabled_backends
# * [os_glance_staging_store]/filesystem_store_datadir
#
# (string value)
# This option is deprecated for removal since Train.
# Its value may be silently ignored in the future.
# Reason:
# With the introduction of the Glance multistore feature, the way of
# configuring this option has changed. Please refer to
# [os_glance_staging_store]/filesystem_store_datadir for multistore
# configuration.
#
# This option is scheduled to be removed early in the 'U' development
# cycle.
#node_staging_uri = file:///tmp/staging/
#
@ -5033,326 +5016,6 @@
#auth_section = <None>
[os_glance_staging_store]
#
# This is the configuration block for a store reserved for Glance's
# internal use.
#
# When the Glance multistore feature is in use, as indicated by the
# configuration option ``[DEFAULT]/enabled_backends`` having been
# configured, you must configure a *filesystem store* as the "staging
# area" for the interoperable image import process. Please see the
# Glance Train release notes and the "Multi Store Support" chapter of
# the Glance Administration Guide for more information.
#
# NOTE: Configuring this store replaces the use of the old
# ``[DEFAULT]/node_staging_uri`` option. Keep in mind, however, that the
# reserved store you configure in this section of the configuration file
# is *ignored* unless the Glance multistore feature is configured.
#
# Related Options:
#
# * [DEFAULT]/enabled_backends - NOTE: ``enabled_backends`` must have
# a value (that's how the multistore feature is enabled), but the
# list of backends must NOT include this reserved store
#
#
# From glance.reserved_stores
#
#
# Absolute path to the work directory to use as the staging area
# for the interoperable image import process.
#
# NOTE: When providing a value for this option, please make sure
# that enough space is provided for concurrent user image import operations.
# A rough estimation can be done by multiplying the expected number of
# concurrent image imports with an average image size (e.g 500MB). (A
# worst case scenario for concurrent uploads would be ``[DEFAULT]/workers``,
# in which every available API thread is satisfying a PUT request to the
# staging area.) The size estimation should be done based on the average
# size image in your deployment.
#
# Possible values:
#
# * String value representing the absolute path to a directory
# to be used by a filesystem store
# * This value MUST be different from the value used for the
# ``[os_glance_tasks_store]/filesystem_store_datadir`` option
#
# Related Options:
#
# * [os_glance_tasks_store]/filesystem_store_datadir
#
# (string value)
#
# This option has a sample default set, which means that
# its actual default value may vary from the one documented
# below.
#filesystem_store_datadir = /var/lib/glance/staging/
#
# 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
#
# Chunk size, in bytes.
#
# The chunk size used when reading or writing image files. Raising this value
# may improve the throughput but it may also slightly increase the memory usage
# when handling a large number of requests.
#
# Possible Values:
# * Any positive integer value
#
# Related options:
# * None
#
# (integer value)
# Minimum value: 1
#filesystem_store_chunk_size = 65536
[os_glance_tasks_store]
#
# This is the configuration block for a store reserved for Glance's
# internal use.
#
# When the Glance multistore feature is in use, as indicated by the
# configuration option ``[DEFAULT]/enabled_backends`` having been
# configured, you must configure a *filesystem store* for the use of
# the tasks engine. Please see the Glance Train release notes
# and the "Multi Store Support" chapter of the Glance Administration
# Guide for more information.
#
# NOTE: Configuring this store replaces the use of the old
# ``[tasks]/work_dir`` option. Keep in mind, however, that
# the reserved store you configure in this section of the configuration
# file is *ignored* unless the Glance multistore feature is configured.
#
# Related Options:
#
# * [DEFAULT]/enabled_backends - NOTE: ``enabled_backends`` must have
# a value (that's how the multistore feature is enabled), but the
# list of backends must NOT include this reserved store
#
#
# From glance.reserved_stores
#
#
# Absolute path to the work directory to use for asynchronous
# task operations.
#
# NOTE: When providing a value for this option, 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
# ``[taskflow_executor]/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 a directory
# to be used by a filesystem store
# * This value MUST be different from the value used for the
# ``[os_glance_staging_store]/filesystem_store_datadir`` option
#
# Related Options:
# * [taskflow_executor]/max_workers
# * [os_glance_staging_store]/filesystem_store_datadir
#
# (string value)
#
# This option has a sample default set, which means that
# its actual default value may vary from the one documented
# below.
#filesystem_store_datadir = /var/lib/glance/tasks_work_dir/
#
# 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
#
# Chunk size, in bytes.
#
# The chunk size used when reading or writing image files. Raising this value
# may improve the throughput but it may also slightly increase the memory usage
# when handling a large number of requests.
#
# Possible Values:
# * Any positive integer value
#
# Related options:
# * None
#
# (integer value)
# Minimum value: 1
#filesystem_store_chunk_size = 65536
[oslo_concurrency]
#
@ -6077,7 +5740,7 @@
# (string value)
#task_executor = taskflow
# DEPRECATED:
#
# Absolute path to the work directory to use for asynchronous
# task operations.
#
@ -6098,30 +5761,14 @@
# are just estimations and you should do them based on the worst
# case scenario and be prepared to act in case they were wrong.
#
# NOTE: If you are using the Glance multistore feature, you *must*
# use a filesystem store instead of this setting. See the
# ``[os_glance_tasks_store]`` section of this configuration file
# for more information.
#
# Possible values:
# * String value representing the absolute path to the working
# directory
#
# Related Options:
# * enabled_backends
# * [os_glance_tasks_store]/filesystem_store_datadir
# * None
#
# (string value)
# This option is deprecated for removal since Train.
# Its value may be silently ignored in the future.
# Reason:
# With the introduction of the Glance multistore feature, the way of
# configuring this option has changed. Please refer to
# [os_glance_tasks_store]/filesystem_store_datadir for multistore
# configuration.
#
# This option is scheduled to be removed early in the 'U' development
# cycle.
#
# This option has a sample default set, which means that
# its actual default value may vary from the one documented

View File

@ -475,7 +475,7 @@
# (string value)
#digest_algorithm = sha256
# DEPRECATED:
#
# The URL provides location where the temporary data will be stored
#
# This option is for Glance internal use only. Glance will save the
@ -492,30 +492,13 @@
# NOTE: The staging path must be on shared filesystem available to all
# Glance API nodes.
#
# NOTE: If you are using the Glance multistore feature, you *must*
# use a filesystem store instead of this setting. See the
# ``[os_glance_staging_store]`` section of this configuration file
# for more information.
#
# Possible values:
# * String starting with 'file://' followed by absolute FS path
#
# Related options:
# * [task]/work_dir
# * enabled_backends
# * [os_glance_staging_store]/filesystem_store_datadir
#
# (string value)
# This option is deprecated for removal since Train.
# Its value may be silently ignored in the future.
# Reason:
# With the introduction of the Glance multistore feature, the way of
# configuring this option has changed. Please refer to
# [os_glance_staging_store]/filesystem_store_datadir for multistore
# configuration.
#
# This option is scheduled to be removed early in the 'U' development
# cycle.
#node_staging_uri = file:///tmp/staging/
#

View File

@ -558,7 +558,7 @@
# (string value)
#digest_algorithm = sha256
# DEPRECATED:
#
# The URL provides location where the temporary data will be stored
#
# This option is for Glance internal use only. Glance will save the
@ -575,30 +575,13 @@
# NOTE: The staging path must be on shared filesystem available to all
# Glance API nodes.
#
# NOTE: If you are using the Glance multistore feature, you *must*
# use a filesystem store instead of this setting. See the
# ``[os_glance_staging_store]`` section of this configuration file
# for more information.
#
# Possible values:
# * String starting with 'file://' followed by absolute FS path
#
# Related options:
# * [task]/work_dir
# * enabled_backends
# * [os_glance_staging_store]/filesystem_store_datadir
#
# (string value)
# This option is deprecated for removal since Train.
# Its value may be silently ignored in the future.
# Reason:
# With the introduction of the Glance multistore feature, the way of
# configuring this option has changed. Please refer to
# [os_glance_staging_store]/filesystem_store_datadir for multistore
# configuration.
#
# This option is scheduled to be removed early in the 'U' development
# cycle.
#node_staging_uri = file:///tmp/staging/
#

File diff suppressed because it is too large Load Diff