[config-ref] fix incorrect table format

re-run the tool with latest version.

Closes-Bug: #1638004

Change-Id: I13a4e53c403e189839d04a0376bc0db1cf0ef049
This commit is contained in:
KATO Tomoyuki 2016-11-11 17:40:51 +09:00
parent 4050e3f515
commit 55167764ae
37 changed files with 2074 additions and 237 deletions

View File

@ -19,55 +19,389 @@
* - **[DEFAULT]**
-
* - ``admin_role`` = ``admin``
- (String) Role used to identify an authenticated user as administrator.$sentinal$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'.$sentinal$Possible values: * A string value which is a valid Keystone role$sentinal$Related options: * None
- (String) 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
* - ``allow_anonymous_access`` = ``False``
- (Boolean) Allow limited access to unauthenticated users.$sentinal$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.$sentinal$Possible values: * True * False$sentinal$Related options: * None
- (Boolean) 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
* - ``available_plugins`` =
- (List) A list of artifacts that are allowed in the format name or name-version. Empty list means that any artifact can be loaded.
* - ``client_socket_timeout`` = ``900``
- (Integer) Timeout for client connections' socket operations.$sentinal$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.$sentinal$The value zero implies wait forever.$sentinal$Possible values: * Zero * Positive integer$sentinal$Related options: * None
- (Integer) 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
* - ``enable_v1_api`` = ``True``
- (Boolean) Deploy the v1 OpenStack Images API.$sentinal$When this option is set to ``True``, Glance service will respond to requests on registered endpoints conforming to the v1 OpenStack Images API.$sentinal$NOTES: * If this option is enabled, then ``enable_v1_registry`` must also be set to ``True`` to enable mandatory usage of Registry service with v1 API.$sentinal$ * If this option is disabled, then the ``enable_v1_registry`` option, which is enabled by default, is also recommended to be disabled.$sentinal$ * This option is separate from ``enable_v2_api``, both v1 and v2 OpenStack Images API can be deployed independent of each other.$sentinal$ * If deploying only the v2 Images API, this option, which is enabled by default, should be disabled.$sentinal$Possible values: * True * False$sentinal$Related options: * enable_v1_registry * enable_v2_api
- (Boolean) Deploy the v1 OpenStack Images API.
When this option is set to ``True``, Glance service will respond to requests on registered endpoints conforming to the v1 OpenStack Images API.
NOTES:
* If this option is enabled, then ``enable_v1_registry`` must also be set to ``True`` to enable mandatory usage of Registry service with v1 API.
* If this option is disabled, then the ``enable_v1_registry`` option, which is enabled by default, is also recommended to be disabled.
* This option is separate from ``enable_v2_api``, both v1 and v2 OpenStack Images API can be deployed independent of each other.
* If deploying only the v2 Images API, this option, which is enabled by default, should be disabled.
Possible values:
* True
* False
Related options:
* enable_v1_registry
* enable_v2_api
* - ``enable_v1_registry`` = ``True``
- (Boolean) Deploy the v1 API Registry service.$sentinal$When this option is set to ``True``, the Registry service will be enabled in Glance for v1 API requests.$sentinal$NOTES: * Use of Registry is mandatory in v1 API, so this option must be set to ``True`` if the ``enable_v1_api`` option is enabled.$sentinal$ * If deploying only the v2 OpenStack Images API, this option, which is enabled by default, should be disabled.$sentinal$Possible values: * True * False$sentinal$Related options: * enable_v1_api
- (Boolean) Deploy the v1 API Registry service.
When this option is set to ``True``, the Registry service will be enabled in Glance for v1 API requests.
NOTES:
* Use of Registry is mandatory in v1 API, so this option must be set to ``True`` if the ``enable_v1_api`` option is enabled.
* If deploying only the v2 OpenStack Images API, this option, which is enabled by default, should be disabled.
Possible values:
* True
* False
Related options:
* enable_v1_api
* - ``enable_v2_api`` = ``True``
- (Boolean) Deploy the v2 OpenStack Images API.$sentinal$When this option is set to ``True``, Glance service will respond to requests on registered endpoints conforming to the v2 OpenStack Images API.$sentinal$NOTES: * If this option is disabled, then the ``enable_v2_registry`` option, which is enabled by default, is also recommended to be disabled.$sentinal$ * This option is separate from ``enable_v1_api``, both v1 and v2 OpenStack Images API can be deployed independent of each other.$sentinal$ * If deploying only the v1 Images API, this option, which is enabled by default, should be disabled.$sentinal$Possible values: * True * False$sentinal$Related options: * enable_v2_registry * enable_v1_api
- (Boolean) 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.
* This option is separate from ``enable_v1_api``, both v1 and v2 OpenStack Images API can be deployed independent of each other.
* If deploying only the v1 Images API, this option, which is enabled by default, should be disabled.
Possible values:
* True
* False
Related options:
* enable_v2_registry
* enable_v1_api
* - ``enable_v2_registry`` = ``True``
- (Boolean) Deploy the v2 API Registry service.$sentinal$When this option is set to ``True``, the Registry service will be enabled in Glance for v2 API requests.$sentinal$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``.$sentinal$ * If deploying only the v1 OpenStack Images API, this option, which is enabled by default, should be disabled.$sentinal$Possible values: * True * False$sentinal$Related options: * enable_v2_api * data_api
- (Boolean) 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
* - ``http_keepalive`` = ``True``
- (Boolean) Set keep alive option for HTTP over TCP.$sentinal$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.$sentinal$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.$sentinal$Possible values: * True * False$sentinal$Related options: * None
- (Boolean) 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
* - ``image_size_cap`` = ``1099511627776``
- (Integer) Maximum size of image a user can upload in bytes.$sentinal$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).$sentinal$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.$sentinal$Possible values: * Any positive number less than or equal to 9223372036854775808
- (Integer) 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
* - ``load_enabled`` = ``True``
- (Boolean) When false, no artifacts can be loaded regardless of available_plugins. When true, artifacts can be loaded.
* - ``location_strategy`` = ``location_order``
- (String) Strategy to determine the preference order of image locations.$sentinal$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.$sentinal$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``.$sentinal$Possible values: * location_order * store_type$sentinal$Related options: * store_type_preference
- (String) 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
* - ``max_header_line`` = ``16384``
- (Integer) Maximum line size of message headers.$sentinal$Provide an integer value representing a length to limit the size of message headers. The default value is 16384.$sentinal$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.$sentinal$Setting ``max_header_line`` to 0 sets no limit for the line size of message headers.$sentinal$Possible values: * 0 * Positive integer$sentinal$Related options: * None
- (Integer) 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
* - ``max_request_id_length`` = ``64``
- (Integer) Limit the request ID length.$sentinal$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.$sentinal$Possible values: * Integer value between 0 and 16384$sentinal$Related options: * None
- (Integer) 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
* - ``owner_is_tenant`` = ``True``
- (Boolean) Set the image owner to tenant or the authenticated user.$sentinal$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.$sentinal$Possible values: * True * False$sentinal$Related options: * None
- (Boolean) 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
* - ``public_endpoint`` = ``None``
- (String) Public url endpoint to use for Glance/Glare versions response.$sentinal$This is the public url endpoint that will appear in the Glance/Glare "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.$sentinal$Possible values: * None * Proxy URL * Load balancer URL$sentinal$Related options: * None
- (String) Public url endpoint to use for Glance/Glare versions response.
This is the public url endpoint that will appear in the Glance/Glare "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
* - ``secure_proxy_ssl_header`` = ``None``
- (String) 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". Use the http_proxy_to_wsgi middleware instead.
* - ``send_identity_headers`` = ``False``
- (Boolean) Send headers received from identity when making requests to registry.$sentinal$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``.$sentinal$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.$sentinal$Possible values: * True * False$sentinal$Related options: * flavor
- (Boolean) 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
* - ``show_multiple_locations`` = ``False``
- (Boolean) DEPRECATED: Show all image locations when returning an image.$sentinal$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``.$sentinal$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``.$sentinal$Possible values: * True * False$sentinal$Related options: * show_image_direct_url * location_strategy This option will be removed in the Ocata release because the same functionality can be achieved with greater granularity by using policies. Please see the Newton release notes for more information.
- (Boolean) 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 This option will be removed in the Ocata release because the same functionality can be achieved with greater granularity by using policies. Please see the Newton release notes for more information.
* - ``tcp_keepidle`` = ``600``
- (Integer) Set the wait time before a connection recheck.$sentinal$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.$sentinal$Setting ``tcp_keepidle`` helps verify at regular intervals that a connection is intact and prevents frequent TCP connection reestablishment.$sentinal$Possible values: * Positive integer value representing time in seconds$sentinal$Related options: * None
- (Integer) 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
* - ``use_user_token`` = ``True``
- (Boolean) 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. 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.
* - **[glance_store]**
-
* - ``default_store`` = ``file``
- (String) The default scheme to use for storing images.$sentinal$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.$sentinal$NOTE: The value given for this configuration option must be a valid scheme for a store registered with the ``stores`` configuration option.$sentinal$Possible values: * file * filesystem * http * https * swift * swift+http * swift+https * swift+config * rbd * sheepdog * cinder * vsphere$sentinal$Related Options: * stores
- (String) 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
* - ``store_capabilities_update_min_interval`` = ``0``
- (Integer) Minimum interval in seconds to execute updating dynamic storage capabilities based on current backend status.$sentinal$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.$sentinal$By default, this option is set to zero and is disabled. Provide an integer value greater than zero to enable this option.$sentinal$NOTE: For more information on store capabilities and their updates, please visit: https://specs.openstack.org/openstack/glance-specs/specs/kilo/store-capabilities.html$sentinal$For more information on setting up a particular store in your deplyment and help with the usage of this feature, please contact the storage driver maintainers listed here: http://docs.openstack.org/developer/glance_store/drivers/index.html$sentinal$Possible values: * Zero * Positive integer$sentinal$Related Options: * None
- (Integer) 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: 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 deplyment and help with the usage of this feature, please contact the storage driver maintainers listed here: http://docs.openstack.org/developer/glance_store/drivers/index.html
Possible values:
* Zero
* Positive integer
Related Options:
* None
* - ``stores`` = ``file, http``
- (List) List of enabled Glance stores.$sentinal$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``.$sentinal$Possible values: * A comma separated list that could include: * file * http * swift * rbd * sheepdog * cinder * vmware$sentinal$Related Options: * default_store
- (List) 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
* - **[oslo_middleware]**
-
* - ``enable_proxy_headers_parsing`` = ``False``
@ -79,10 +413,70 @@
* - **[paste_deploy]**
-
* - ``config_file`` = ``glance-api-paste.ini``
- (String) Name of the paste configuration file.$sentinal$Provide a string value representing the name of the paste configuration file to use for configuring piplelines for server application deployments.$sentinal$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.$sentinal$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.$sentinal$Possible values: * A string value representing the name of the paste configuration file.$sentinal$Related Options: * flavor
- (String) 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
* - ``flavor`` = ``keystone``
- (String) Deployment flavor to use in the server application pipeline.$sentinal$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.$sentinal$For example, if your paste section name in the paste configuration file is [pipeline:glance-api-keystone], set ``flavor`` to ``keystone``.$sentinal$Possible values: * String value representing a partial pipeline name.$sentinal$Related Options: * config_file
- (String) 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
* - **[store_type_location_strategy]**
-
* - ``store_type_preference`` =
- (List) Preference order of storage backends.$sentinal$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.$sentinal$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.$sentinal$Possible values: * Empty list * Comma separated list of registered store names. Legal values are: * file * http * rbd * swift * sheepdog * cinder * vmware$sentinal$Related options: * location_strategy * stores
- (List) 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

View File

@ -19,8 +19,42 @@
* - **[DEFAULT]**
-
* - ``ca_file`` = ``/etc/ssl/cafile``
- (String) Absolute path to the CA file.$sentinal$Provide a string value representing a valid absolute path to the Certificate Authority file to use for client authentication.$sentinal$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.$sentinal$Possible values: * Valid absolute path to the CA file$sentinal$Related options: * None
- (String) 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
* - ``cert_file`` = ``/etc/ssl/certs``
- (String) Absolute path to the certificate file.$sentinal$Provide a string value representing a valid absolute path to the certificate file which is required to start the API service securely.$sentinal$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.$sentinal$Possible values: * Valid absolute path to the certificate file$sentinal$Related options: * None
- (String) 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
* - ``key_file`` = ``/etc/ssl/key/key-file.pem``
- (String) Absolute path to a private key file.$sentinal$Provide a string value representing a valid absolute path to a private key file which is required to establish the client-server connection.$sentinal$Possible values: * Absolute path to the private key file$sentinal$Related options: * None
- (String) 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

View File

@ -19,24 +19,178 @@
* - **[glance_store]**
-
* - ``cinder_api_insecure`` = ``False``
- (Boolean) Allow to perform insecure SSL requests to cinder.$sentinal$If this option is set to True, HTTPS endpoint connection is verified using the CA certificates file specified by ``cinder_ca_certificates_file`` option.$sentinal$Possible values: * True * False$sentinal$Related options: * cinder_ca_certificates_file
- (Boolean) 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
* - ``cinder_ca_certificates_file`` = ``None``
- (String) Location of a CA certificates file used for cinder client requests.$sentinal$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.$sentinal$Possible values: * Path to a ca certificates file$sentinal$Related options: * cinder_api_insecure
- (String) 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
* - ``cinder_catalog_info`` = ``volumev2::publicURL``
- (String) Information to match when looking for cinder in the service catalog.$sentinal$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.$sentinal$The service catalog can be listed by the ``openstack catalog list`` command.$sentinal$Possible values: * A string of of the following form: ``<service_type>:<service_name>:<endpoint_type>`` At least ``service_type`` and ``endpoint_type`` should be specified. ``service_name`` can be omitted.$sentinal$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) 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>:<endpoint_type>`` At least ``service_type`` and ``endpoint_type`` 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
* - ``cinder_endpoint_template`` = ``None``
- (String) Override service catalog lookup with template for cinder endpoint.$sentinal$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.$sentinal$If this configuration option is set, ``cinder_catalog_info`` will be ignored.$sentinal$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$sentinal$`` Related options: * cinder_store_auth_address * cinder_store_user_name * cinder_store_project_name * cinder_store_password * cinder_catalog_info
- (String) 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
* - ``cinder_http_retries`` = ``3``
- (Integer) Number of cinderclient retries on failed http calls.$sentinal$When a call failed by any errors, cinderclient will retry the call up to the specified times after sleeping a few seconds.$sentinal$Possible values: * A positive integer$sentinal$Related options: * None
- (Integer) 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
* - ``cinder_os_region_name`` = ``None``
- (String) Region name to lookup cinder service from the service catalog.$sentinal$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.$sentinal$Possible values: * A string that is a valid region name.$sentinal$Related options: * cinder_catalog_info
- (String) 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
* - ``cinder_state_transition_timeout`` = ``300``
- (Integer) Time period, in seconds, to wait for a cinder volume transition to complete.$sentinal$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.$sentinal$Possible values: * A positive integer$sentinal$Related options: * None
- (Integer) 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
* - ``cinder_store_auth_address`` = ``None``
- (String) The address where the cinder authentication service is listening.$sentinal$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.$sentinal$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.$sentinal$Possible values: * A valid authentication service address, for example: ``http://openstack.example.org/identity/v2.0`` $sentinal$ Related options: * cinder_store_user_name * cinder_store_password * cinder_store_project_name
- (String) 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
* - ``cinder_store_password`` = ``None``
- (String) Password for the user authenticating against cinder.$sentinal$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.$sentinal$Possible values: * A valid password for the user specified by ``cinder_store_user_name$sentinal$`` Related options: * cinder_store_auth_address * cinder_store_user_name * cinder_store_project_name
- (String) 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
* - ``cinder_store_project_name`` = ``None``
- (String) Project name where the image volume is stored in cinder.$sentinal$If this configuration option is not set, the project in current context is used.$sentinal$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.$sentinal$Possible values: * A valid project name$sentinal$Related options: * ``cinder_store_auth_address`` * ``cinder_store_user_name`` * ``cinder_store_password``
- (String) 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``
* - ``cinder_store_user_name`` = ``None``
- (String) User name to authenticate against cinder.$sentinal$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.$sentinal$Possible values: * A valid user name$sentinal$Related options: * cinder_store_auth_address * cinder_store_password * cinder_store_project_name
- (String) 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

View File

@ -19,49 +19,303 @@
* - **[DEFAULT]**
-
* - ``allow_additional_image_properties`` = ``True``
- (Boolean) Allow users to add additional/custom properties to images.$sentinal$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``.$sentinal$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.$sentinal$Possible values: * True * False$sentinal$Related options: * image_property_quota
- (Boolean) 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
* - ``api_limit_max`` = ``1000``
- (Integer) Maximum number of results that could be returned by a request.$sentinal$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.$sentinal$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.$sentinal$Possible values: * Any positive integer$sentinal$Related options: * limit_param_default
- (Integer) 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
* - ``backlog`` = ``4096``
- (Integer) Set the number of incoming connection requests.$sentinal$Provide a positive integer value to limit the number of requests in the backlog queue. The default queue size is 4096.$sentinal$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.$sentinal$Possible values: * Positive integer$sentinal$Related options: * None
- (Integer) 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
* - ``bind_host`` = ``0.0.0.0``
- (String) IP address to bind the glance servers to.$sentinal$Provide an IP address to bind the glance server to. The default value is ``0.0.0.0``.$sentinal$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.$sentinal$Possible values: * A valid IPv4 address * A valid IPv6 address$sentinal$Related options: * None
- (String) 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
* - ``bind_port`` = ``None``
- (Port number) Port number on which the server will listen.$sentinal$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.$sentinal$Possible values: * A valid port number (0 to 65535)$sentinal$Related options: * None
- (Port number) 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
* - ``data_api`` = ``glance.db.sqlalchemy.api``
- (String) Python module path of data access API.$sentinal$Specifies the path to the API to use for accessing the data model. This option determines how the image catalog data will be accessed.$sentinal$Possible values: * glance.db.sqlalchemy.api * glance.db.registry.api * glance.db.simple.api$sentinal$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.$sentinal$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.$sentinal$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``.$sentinal$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.$sentinal$Related options: * enable_v2_api * enable_v2_registry
- (String) 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
* - ``digest_algorithm`` = ``sha256``
- (String) Digest algorithm to use for digital signature.$sentinal$Provide a string value representing the digest algorithm to use for generating digital signatures. By default, ``sha256`` is used.$sentinal$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'.$sentinal$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.$sentinal$Possible values: * An OpenSSL message digest algorithm identifier$sentinal$Relation options: * None
- (String) 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
* - ``executor_thread_pool_size`` = ``64``
- (Integer) Size of executor thread pool.
* - ``image_location_quota`` = ``10``
- (Integer) Maximum number of locations allowed on an image.$sentinal$Any negative value is interpreted as unlimited.$sentinal$Related options: * None
- (Integer) Maximum number of locations allowed on an image.
Any negative value is interpreted as unlimited.
Related options:
* None
* - ``image_member_quota`` = ``128``
- (Integer) Maximum number of image members per image.$sentinal$This limits the maximum of users an image can be shared with. Any negative value is interpreted as unlimited.$sentinal$Related options: * None
- (Integer) 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
* - ``image_property_quota`` = ``128``
- (Integer) Maximum number of properties allowed on an image.$sentinal$This enforces an upper limit on the number of additional properties an image can have. Any negative value is interpreted as unlimited.$sentinal$NOTE: This won't have any impact if additional properties are disabled. Please refer to ``allow_additional_image_properties``.$sentinal$Related options: * ``allow_additional_image_properties``
- (Integer) 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``
* - ``image_tag_quota`` = ``128``
- (Integer) Maximum number of tags allowed on an image.$sentinal$Any negative value is interpreted as unlimited.$sentinal$Related options: * None
- (Integer) Maximum number of tags allowed on an image.
Any negative value is interpreted as unlimited.
Related options:
* None
* - ``limit_param_default`` = ``25``
- (Integer) The default number of results to return for a request.$sentinal$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.$sentinal$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.$sentinal$Possible values: * Any positive integer$sentinal$Related options: * api_limit_max
- (Integer) 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
* - ``metadata_encryption_key`` = ``None``
- (String) AES key for encrypting store location metadata.$sentinal$Provide a string value representing the AES cipher to use for encrypting Glance store metadata.$sentinal$NOTE: The AES key to use must be set to a random string of length 16, 24 or 32 bytes.$sentinal$Possible values: * String value representing a valid AES key$sentinal$Related options: * None
- (String) 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
* - ``metadata_source_path`` = ``/etc/glance/metadefs/``
- (String) Absolute path to the directory where JSON metadefs files are stored.$sentinal$Glance Metadata Definitions ("metadefs") are served from the database, but are stored in files in the JSON format. The files in this directory are used to initialize the metadefs in the database. Additionally, when metadefs are exported from the database, the files are written to this directory.$sentinal$NOTE: If you plan to export metadefs, make sure that this directory has write permissions set for the user being used to run the glance-api service.$sentinal$Possible values: * String value representing a valid absolute pathname$sentinal$Related options: * None
- (String) Absolute path to the directory where JSON metadefs files are stored.
Glance Metadata Definitions ("metadefs") are served from the database, but are stored in files in the JSON format. The files in this directory are used to initialize the metadefs in the database. Additionally, when metadefs are exported from the database, the files are written to this directory.
NOTE: If you plan to export metadefs, make sure that this directory has write permissions set for the user being used to run the glance-api service.
Possible values:
* String value representing a valid absolute pathname
Related options:
* None
* - ``property_protection_file`` = ``None``
- (String) The location of the property protection file.$sentinal$Provide a valid path to the property protection file which contains the rules for property protections and the roles/policies associated with them.$sentinal$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: http://docs.openstack.org/developer/glance/property-protections.html$sentinal$Possible values: * Empty string * Valid path to the property protection configuration file$sentinal$Related options: * property_protection_rule_format
- (String) 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: http://docs.openstack.org/developer/glance/property-protections.html
Possible values:
* Empty string
* Valid path to the property protection configuration file
Related options:
* property_protection_rule_format
* - ``property_protection_rule_format`` = ``roles``
- (String) Rule format for property protection.$sentinal$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``.$sentinal$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: http://docs.openstack.org/developer/glance/property-protections.html#examples$sentinal$Possible values: * roles * policies$sentinal$Related options: * property_protection_file
- (String) 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: http://docs.openstack.org/developer/glance/property-protections.html#examples
Possible values:
* roles
* policies
Related options:
* property_protection_file
* - ``show_image_direct_url`` = ``False``
- (Boolean) Show direct image location when returning an image.$sentinal$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``.$sentinal$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``.$sentinal$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``.$sentinal$Possible values: * True * False$sentinal$Related options: * show_multiple_locations * location_strategy
- (Boolean) 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
* - ``user_storage_quota`` = ``0``
- (String) Maximum amount of image storage per tenant.$sentinal$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.$sentinal$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.$sentinal$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.$sentinal$Related options: * None
- (String) 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
* - ``workers`` = ``None``
- (Integer) Number of Glance worker processes to start.$sentinal$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``.$sentinal$Each worker process is made to listen on the port set in the configuration file and contains a greenthread pool of size 1000.$sentinal$NOTE: Setting the number of workers to zero, triggers the creation of a single API process with a greenthread pool of size 1000.$sentinal$Possible values: * 0 * Positive integer value (typically equal to the number of CPUs)$sentinal$Related options: * None
- (Integer) 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``.
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
* - **[glance_store]**
-
* - ``rootwrap_config`` = ``/etc/glance/rootwrap.conf``
- (String) Path to the rootwrap configuration file to use for running commands as root.$sentinal$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.$sentinal$Possible values: * Path to the rootwrap config file$sentinal$Related options: * None
- (String) 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
* - **[image_format]**
-
* - ``container_formats`` = ``ami, ari, aki, bare, ovf, ova, docker``
@ -71,8 +325,34 @@
* - **[task]**
-
* - ``task_executor`` = ``taskflow``
- (String) Task executor to be used to run task scripts.$sentinal$Provide a string value representing the executor to use for task executions. By default, ``TaskFlow`` executor is used.$sentinal$``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.$sentinal$Possible values: * taskflow$sentinal$Related Options: * None
- (String) 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
* - ``task_time_to_live`` = ``48``
- (Integer) Time in hours for which a task lives after, either succeeding or failing
* - ``work_dir`` = ``/work_dir``
- (String) Absolute path to the work directory to use for asynchronous task operations.$sentinal$The directory set here will be used to operate over images - normally before they are imported in the destination store.$sentinal$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.$sentinal$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.$sentinal$Possible values: * String value representing the absolute path to the working directory$sentinal$Related Options: * None
- (String) 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

View File

@ -19,10 +19,68 @@
* - **[glance_store]**
-
* - ``filesystem_store_datadir`` = ``/var/lib/glance/images``
- (String) Directory to which the filesystem backend store writes images.$sentinal$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.$sentinal$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.$sentinal$Possible values: * A valid path to a directory$sentinal$Related options: * ``filesystem_store_datadirs`` * ``filesystem_store_file_perm``
- (String) 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``
* - ``filesystem_store_datadirs`` = ``None``
- (Multi-valued) List of directories and their priorities to which the filesystem backend store writes images.$sentinal$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.$sentinal$More information on configuring filesystem store with multiple store directories can be found at http://docs.openstack.org/developer/glance/configuring.html$sentinal$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.$sentinal$Possible values: * List of strings of the following form: * ``<a valid directory path>:<optional integer priority>``$sentinal$Related options: * ``filesystem_store_datadir`` * ``filesystem_store_file_perm``
- (Multi-valued) List of directories and their priorities to which the filesystem backend store writes images.
The filesystem store can be configured to store images in multiple directories as opposed to using a single directory specified by the ``filesystem_store_datadir`` configuration option. When using multiple directories, each directory can be given an optional priority to specify the preference order in which they should be used. Priority is an integer that is concatenated to the directory path with a colon where a higher value indicates higher priority. When two directories have the same priority, the directory with most free space is used. When no priority is specified, it defaults to zero.
More information on configuring filesystem store with multiple store directories can be found at http://docs.openstack.org/developer/glance/configuring.html
NOTE: This directory is used only when filesystem store is used as a storage backend. Either ``filesystem_store_datadir`` or ``filesystem_store_datadirs`` option must be specified in ``glance-api.conf``. If both options are specified, a ``BadStoreConfiguration`` will be raised and the filesystem store may not be available for adding new images.
Possible values:
* List of strings of the following form:
* ``<a valid directory path>:<optional integer priority>``
Related options:
* ``filesystem_store_datadir``
* ``filesystem_store_file_perm``
* - ``filesystem_store_file_perm`` = ``0``
- (Integer) File access permissions for the image files.$sentinal$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.$sentinal$For more information, please refer the documentation at http://docs.openstack.org/developer/glance/configuring.html$sentinal$Possible values: * A valid file access permission * Zero * Any negative integer$sentinal$Related options: * None
- (Integer) File access permissions for the image files.
Set the intended file access permissions for image data. This provides a way to enable other services, e.g. Nova, to consume images directly from the filesystem store. The users running the services that are intended to be given access to could be made a member of the group that owns the files created. Assigning a value less then or equal to zero for this configuration option signifies that no changes be made to the default permissions. This value will be decoded as an octal digit.
For more information, please refer the documentation at http://docs.openstack.org/developer/glance/configuring.html
Possible values:
* A valid file access permission
* Zero
* Any negative integer
Related options:
* None
* - ``filesystem_store_metadata_file`` = ``None``
- (String) Filesystem store metadata file.$sentinal$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.$sentinal$Possible values: * A valid path to the store metadata file$sentinal$Related options: * None
- (String) 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

View File

@ -19,8 +19,42 @@
* - **[glance_store]**
-
* - ``http_proxy_information`` = ``{}``
- (Dict) The http/https proxy information to be used to connect to the remote server.$sentinal$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.$sentinal$Possible values: * A comma separated list of scheme:proxy pairs as described above$sentinal$Related options: * None
- (Dict) 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
* - ``https_ca_certificates_file`` = ``None``
- (String) Path to the CA bundle file.$sentinal$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.$sentinal$Possible values: * A valid path to a CA file$sentinal$Related options: * https_insecure
- (String) 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
* - ``https_insecure`` = ``True``
- (Boolean) Set verification of the remote server certificate.$sentinal$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.$sentinal$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.$sentinal$Possible values: * True * False$sentinal$Related options: * https_ca_certificates_file
- (Boolean) 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

View File

@ -19,18 +19,126 @@
* - **[DEFAULT]**
-
* - ``delayed_delete`` = ``False``
- (Boolean) Turn on/off delayed delete.$sentinal$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.$sentinal$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.$sentinal$Possible values: * True * False$sentinal$Related options: * ``scrub_time`` * ``wakeup_time`` * ``scrub_pool_size``
- (Boolean) 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``
* - ``image_cache_dir`` = ``None``
- (String) Base directory for image cache.$sentinal$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``.$sentinal$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.$sentinal$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.$sentinal$Possible values: * A valid path$sentinal$Related options: * ``image_cache_sqlite_db``
- (String) 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``
* - ``image_cache_driver`` = ``sqlite``
- (String) The driver to use for image cache management.$sentinal$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.$sentinal$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.$sentinal$Possible values: * sqlite * xattr$sentinal$Related options: * None
- (String) 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
* - ``image_cache_max_size`` = ``10737418240``
- (Integer) The upper limit on cache size, in bytes, after which the cache-pruner cleans up the image cache.$sentinal$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.$sentinal$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.$sentinal$Possible values: * Any non-negative integer$sentinal$Related options: * None
- (Integer) 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
* - ``image_cache_sqlite_db`` = ``cache.db``
- (String) The relative path to sqlite file database that will be used for image cache management.$sentinal$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``.$sentinal$This is a lightweight database with just one table.$sentinal$Possible values: * A valid relative path to sqlite file database$sentinal$Related options: * ``image_cache_dir``
- (String) 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``
* - ``image_cache_stall_time`` = ``86400``
- (Integer) The amount of time, in seconds, an incomplete image remains in the cache.$sentinal$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.$sentinal$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.$sentinal$Possible values: * Any non-negative integer$sentinal$Related options: * None
- (Integer) 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
* - ``scrub_pool_size`` = ``1``
- (Integer) The size of thread pool to be used for scrubbing images.$sentinal$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.$sentinal$Possible values: * Any non-zero positive integer$sentinal$Related options: * ``delayed_delete``
- (Integer) 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``
* - ``scrub_time`` = ``0``
- (Integer) The amount of time, in seconds, to delay image scrubbing.$sentinal$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.$sentinal$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.$sentinal$Possible values: * Any non-negative integer$sentinal$Related options: * ``delayed_delete``
- (Integer) 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``

View File

@ -19,10 +19,28 @@
* - **[profiler]**
-
* - ``connection_string`` = ``messaging://``
- (String) Connection string for a notifier backend. Default value is messaging:// which sets the notifier to oslo_messaging.$sentinal$Examples of possible values:$sentinal$* messaging://: use oslo_messaging driver for sending notifications.
- (String) 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 notifications.
* - ``enabled`` = ``False``
- (Boolean) Enables the profiling for all services on this node. Default value is False (fully disable the profiling feature).$sentinal$Possible values:$sentinal$* True: Enables the feature$sentinal$* 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) Enables 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.
* - ``hmac_keys`` = ``SECRET_KEY``
- (String) 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.$sentinal$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) 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.
* - ``trace_sqlalchemy`` = ``False``
- (Boolean) Enables SQL requests profiling in services. Default value is False (SQL requests won't be traced).$sentinal$Possible values:$sentinal$* 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.$sentinal$* 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) Enables 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.

View File

@ -19,12 +19,66 @@
* - **[glance_store]**
-
* - ``rados_connect_timeout`` = ``0``
- (Integer) Timeout value for connecting to Ceph cluster.$sentinal$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.$sentinal$Possible Values: * Any integer value$sentinal$Related options: * None
- (Integer) 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
* - ``rbd_store_ceph_conf`` = ``/etc/ceph/ceph.conf``
- (String) Ceph configuration file path.$sentinal$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$sentinal$Possible Values: * A valid path to a configuration file$sentinal$Related options: * rbd_store_user
- (String) 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
* - ``rbd_store_chunk_size`` = ``8``
- (Integer) Size, in megabytes, to chunk RADOS images into.$sentinal$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.$sentinal$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.$sentinal$Possible Values: * Any positive integer value$sentinal$Related options: * None
- (Integer) 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
* - ``rbd_store_pool`` = ``images``
- (String) RADOS pool in which images are stored.$sentinal$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'.$sentinal$More information on the RBD storage backend can be found here: http://ceph.com/planet/how-data-is-stored-in-ceph-cluster/$sentinal$Possible Values: * A valid pool name$sentinal$Related options: * None
- (String) 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
* - ``rbd_store_user`` = ``None``
- (String) RADOS user to authenticate as.$sentinal$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.$sentinal$Possible Values: * A valid RADOS user$sentinal$Related options: * rbd_store_ceph_conf
- (String) 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

View File

@ -31,18 +31,120 @@
* - ``auth_url`` = ``None``
- (String) 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. 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.
* - ``registry_client_ca_file`` = ``/etc/ssl/cafile/file.ca``
- (String) Absolute path to the Certificate Authority file.$sentinal$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.$sentinal$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``.$sentinal$Possible values: * String value representing a valid absolute path to the CA file.$sentinal$Related options: * registry_client_protocol * registry_client_insecure
- (String) 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
* - ``registry_client_cert_file`` = ``/etc/ssl/certs/file.crt``
- (String) Absolute path to the certificate file.$sentinal$Provide a string value representing a valid absolute path to the certificate file to use for establishing a secure connection to the registry server.$sentinal$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.$sentinal$Possible values: * String value representing a valid absolute path to the certificate file.$sentinal$Related options: * registry_client_protocol
- (String) 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
* - ``registry_client_insecure`` = ``False``
- (Boolean) Set verification of the registry server certificate.$sentinal$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.$sentinal$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.$sentinal$Possible values: * True * False$sentinal$Related options: * registry_client_protocol * registry_client_ca_file
- (Boolean) 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
* - ``registry_client_key_file`` = ``/etc/ssl/key/key-file.pem``
- (String) Absolute path to the private key file.$sentinal$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.$sentinal$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.$sentinal$Possible values: * String value representing a valid absolute path to the key file.$sentinal$Related options: * registry_client_protocol
- (String) 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
* - ``registry_client_protocol`` = ``http``
- (String) Protocol to use for communication with the registry server.$sentinal$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.$sentinal$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.$sentinal$Possible values: * http * https$sentinal$Related options: * registry_client_key_file * registry_client_cert_file * registry_client_ca_file
- (String) 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
* - ``registry_client_timeout`` = ``600``
- (Integer) Timeout value for registry requests.$sentinal$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.$sentinal$A value of 0 implies that a request will never timeout.$sentinal$Possible values: * Zero * Positive integer$sentinal$Related options: * None
- (Integer) 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
* - ``registry_host`` = ``0.0.0.0``
- (String) Address the registry server is hosted on.$sentinal$Possible values: * A valid IP or hostname$sentinal$Related options: * None
- (String) Address the registry server is hosted on.
Possible values:
* A valid IP or hostname
Related options:
* None
* - ``registry_port`` = ``9191``
- (Port number) Port the registry server is listening on.$sentinal$Possible values: * A valid port number$sentinal$Related options: * None
- (Port number) Port the registry server is listening on.
Possible values:
* A valid port number
Related options:
* None

View File

@ -19,4 +19,18 @@
* - **[DEFAULT]**
-
* - ``wakeup_time`` = ``300``
- (Integer) Time interval, in seconds, between scrubber runs in daemon mode.$sentinal$Scrubber can be run either as a cron job or daemon. When run as a daemon, this configuration time specifies the time period between two runs. When the scrubber wakes up, it fetches and scrubs all ``pending_delete`` images that are available for scrubbing after taking ``scrub_time`` into consideration.$sentinal$If the wakeup time is set to a large number, there may be a large number of images to be scrubbed for each run. Also, this impacts how quickly the backend storage is reclaimed.$sentinal$Possible values: * Any non-negative integer$sentinal$Related options: * ``daemon`` * ``delayed_delete``
- (Integer) Time interval, in seconds, between scrubber runs in daemon mode.
Scrubber can be run either as a cron job or daemon. When run as a daemon, this configuration time specifies the time period between two runs. When the scrubber wakes up, it fetches and scrubs all ``pending_delete`` images that are available for scrubbing after taking ``scrub_time`` into consideration.
If the wakeup time is set to a large number, there may be a large number of images to be scrubbed for each run. Also, this impacts how quickly the backend storage is reclaimed.
Possible values:
* Any non-negative integer
Related options:
* ``daemon``
* ``delayed_delete``

View File

@ -19,8 +19,50 @@
* - **[glance_store]**
-
* - ``sheepdog_store_address`` = ``127.0.0.1``
- (String) Address to bind the Sheepdog daemon to.$sentinal$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.$sentinal$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.$sentinal$Possible values: * A valid IPv4 address * A valid IPv6 address * A valid hostname$sentinal$Related Options: * sheepdog_store_port
- (String) 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
* - ``sheepdog_store_chunk_size`` = ``64``
- (Integer) Chunk size for images to be stored in Sheepdog data store.$sentinal$Provide an integer value representing the size in mebibyte (1048576 bytes) to chunk Glance images into. The default chunk size is 64 mebibytes.$sentinal$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.$sentinal$Chunk sizes, if a power of two, help avoid fragmentation and enable improved performance.$sentinal$Possible values: * Positive integer value representing size in mebibytes.$sentinal$Related Options: * None
- (Integer) 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
* - ``sheepdog_store_port`` = ``7000``
- (Port number) Port number on which the sheep daemon will listen.$sentinal$Provide an integer value representing a valid port number on which you want the Sheepdog daemon to listen on. The default port is 7000.$sentinal$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.$sentinal$Possible values: * A valid port number (0 to 65535)$sentinal$Related Options: * sheepdog_store_address
- (Port number) 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

View File

@ -19,11 +19,33 @@
* - **[DEFAULT]**
-
* - ``default_swift_reference`` = ``ref1``
- (String) Reference to default Swift account/backing store parameters.$sentinal$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.$sentinal$Possible values: * A valid string value$sentinal$Related options: * None
- (String) 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
* - ``swift_store_auth_address`` = ``None``
- (String) The address where the Swift authentication service is listening.
* - ``swift_store_config_file`` = ``None``
- (String) File containing the swift account(s) configurations.$sentinal$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 diabled. Configuring this option is highly recommended while using Swift storage backend for image storage as it helps avoid storage of credentials in the database.$sentinal$Possible values: * None * String value representing a vaid configuration file path$sentinal$Related options: * None
- (String) 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 diabled. Configuring this option is highly recommended while using Swift storage backend for image storage as it helps avoid storage of credentials in the database.
Possible values:
* None
* String value representing a vaid configuration file path
Related options:
* None
* - ``swift_store_key`` = ``None``
- (String) Auth key for the user authenticating against the Swift authentication service.
* - ``swift_store_user`` = ``None``
@ -31,48 +53,298 @@
* - **[glance_store]**
-
* - ``default_swift_reference`` = ``ref1``
- (String) Reference to default Swift account/backing store parameters.$sentinal$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.$sentinal$Possible values: * A valid string value$sentinal$Related options: * None
- (String) 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
* - ``swift_store_admin_tenants`` =
- (List) List of tenants that will be granted admin access.$sentinal$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.$sentinal$Possible values: * A comma separated list of strings representing UUIDs of Keystone projects/tenants$sentinal$Related options: * None
- (List) 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
* - ``swift_store_auth_address`` = ``None``
- (String) DEPRECATED: The address where the Swift authentication service is listening. The option 'auth_address' in the Swift back-end configuration file is used instead.
* - ``swift_store_auth_insecure`` = ``False``
- (Boolean) Set verification of the server certificate.$sentinal$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.$sentinal$Possible values: * True * False$sentinal$Related options: * swift_store_cacert
- (Boolean) 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
* - ``swift_store_auth_version`` = ``2``
- (String) DEPRECATED: Version of the authentication service to use. Valid versions are 2 and 3 for keystone and 1 (deprecated) for swauth and rackspace. The option 'auth_version' in the Swift back-end configuration file is used instead.
* - ``swift_store_cacert`` = ``/etc/ssl/certs/ca-certificates.crt``
- (String) Path to the CA bundle file.$sentinal$This configuration option enables the operator to specify the path to a custom Certificate Authority file for SSL verification when connecting to Swift.$sentinal$Possible values: * A valid path to a CA file$sentinal$Related options: * swift_store_auth_insecure
- (String) 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
* - ``swift_store_config_file`` = ``None``
- (String) Absolute path to the file containing the swift account(s) configurations.$sentinal$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.$sentinal$Possible values: * String value representing an absolute path on the glance-api node$sentinal$Related options: * None
- (String) 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.
Possible values:
* String value representing an absolute path on the glance-api node
Related options:
* None
* - ``swift_store_container`` = ``glance``
- (String) Name of single container to store images/name prefix for multiple containers$sentinal$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``.$sentinal$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``).$sentinal$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.``$sentinal$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.$sentinal$Related options: * ``swift_store_multiple_containers_seed`` * ``swift_store_multi_tenant`` * ``swift_store_create_container_on_put``
- (String) 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``
* - ``swift_store_create_container_on_put`` = ``False``
- (Boolean) Create container, if it doesn't already exist, when uploading image.$sentinal$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.$sentinal$Possible values: * True * False$sentinal$Related options: * None
- (Boolean) 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
* - ``swift_store_endpoint`` = ``https://swift.openstack.example.org/v1/path_not_including_container_name``
- (String) The URL endpoint to use for Swift backend storage.$sentinal$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.$sentinal$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.$sentinal$Possible values: * String value representing a valid URL path up to a Swift container$sentinal$Related Options: * None
- (String) 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
* - ``swift_store_endpoint_type`` = ``publicURL``
- (String) Endpoint Type of Swift service.$sentinal$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.$sentinal$Possible values: * publicURL * adminURL * internalURL$sentinal$Related options: * swift_store_endpoint
- (String) 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
* - ``swift_store_expire_soon_interval`` = ``60``
- (Integer) 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.$sentinal$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.$sentinal$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.$sentinal$Possible values: * Zero * Positive integer value$sentinal$Related Options: * None
- (Integer) 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
* - ``swift_store_key`` = ``None``
- (String) DEPRECATED: Auth key for the user authenticating against the Swift authentication service. The option 'key' in the Swift back-end configuration file is used to set the authentication key instead.
* - ``swift_store_large_object_chunk_size`` = ``200``
- (Integer) The maximum size, in MB, of the segments when image data is segmented.$sentinal$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.$sentinal$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.$sentinal$Possible values: * A positive integer that is less than or equal to the large object limit enforced by Swift cluster in consideration.$sentinal$Related options: * ``swift_store_large_object_size``
- (Integer) 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``
* - ``swift_store_large_object_size`` = ``5120``
- (Integer) The size threshold, in MB, after which Glance will start segmenting image data.$sentinal$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 http://docs.openstack.org/developer/swift/overview_large_objects.html$sentinal$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.$sentinal$NOTE: This should be set by taking into account the large object limit enforced by the Swift cluster in consideration.$sentinal$Possible values: * A positive integer that is less than or equal to the large object limit enforced by the Swift cluster in consideration.$sentinal$Related options: * ``swift_store_large_object_chunk_size``
- (Integer) 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 http://docs.openstack.org/developer/swift/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``
* - ``swift_store_multi_tenant`` = ``False``
- (Boolean) Store images in tenant's Swift account.$sentinal$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$sentinal$Possible values: * True * False$sentinal$Related options: * None
- (Boolean) 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
Possible values:
* True
* False
Related options:
* None
* - ``swift_store_multiple_containers_seed`` = ``0``
- (Integer) Seed indicating the number of containers to use for storing images.$sentinal$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.$sentinal$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$sentinal$NOTE: This is used only when swift_store_multi_tenant is disabled.$sentinal$Possible values: * A non-negative integer less than or equal to 32$sentinal$Related options: * ``swift_store_container`` * ``swift_store_multi_tenant`` * ``swift_store_create_container_on_put``
- (Integer) 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``
* - ``swift_store_region`` = ``RegionTwo``
- (String) The region of Swift endpoint to use by Glance.$sentinal$Provide a string value representing a Swift region where Glance can connect to for image storage. By default, there is no region set.$sentinal$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.$sentinal$This option can be configured for both single-tenant and multi-tenant storage.$sentinal$NOTE: Setting the region with ``swift_store_region`` is tenant-specific and is necessary ``only if`` the tenant has multiple endpoints across different regions.$sentinal$Possible values: * A string value representing a valid Swift region.$sentinal$Related Options: * None
- (String) 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
* - ``swift_store_retry_get_count`` = ``0``
- (Integer) The number of times a Swift download will be retried before the request fails.$sentinal$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.$sentinal$Possible values: * Zero * Positive integer value$sentinal$Related Options: * None
- (Integer) 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
* - ``swift_store_service_type`` = ``object-store``
- (String) Type of Swift service to use.$sentinal$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``.$sentinal$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.$sentinal$Possible values: * A string representing a valid service type for Swift storage.$sentinal$Related Options: * None
- (String) 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
* - ``swift_store_ssl_compression`` = ``True``
- (Boolean) SSL layer compression for HTTPS Swift requests.$sentinal$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.$sentinal$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.$sentinal$Possible values: * True * False$sentinal$Related Options: * None
- (Boolean) 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
* - ``swift_store_use_trusts`` = ``True``
- (Boolean) Use trusts for multi-tenant Swift store.$sentinal$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.$sentinal$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.$sentinal$NOTE: This option is considered only when ``swift_store_multi_tenant`` is set to ``True`` $sentinal$Possible values: * True * False$sentinal$Related options: * swift_store_multi_tenant
- (Boolean) 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
* - ``swift_store_user`` = ``None``
- (String) DEPRECATED: The user to authenticate against the Swift authentication service. The option 'user' in the Swift back-end configuration file is set instead.

View File

@ -19,8 +19,48 @@
* - **[taskflow_executor]**
-
* - ``conversion_format`` = ``raw``
- (String) Set the desired image conversion format.$sentinal$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.$sentinal$By default, ``conversion_format`` is not set and must be set explicitly in the configuration file.$sentinal$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.$sentinal$Possible values: * qcow2 * raw * vmdk$sentinal$Related options: * disk_formats
- (String) 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
* - ``engine_mode`` = ``parallel``
- (String) Set the taskflow engine mode.$sentinal$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.$sentinal$Possible values: * serial * parallel$sentinal$Related options: * max_workers
- (String) 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
* - ``max_workers`` = ``10``
- (Integer) Set the number of engine executable tasks.$sentinal$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.$sentinal$Possible values: * Integer value greater than or equal to 1$sentinal$Related options: * engine_mode
- (Integer) 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

View File

@ -19,6 +19,28 @@
* - **[DEFAULT]**
-
* - ``pydev_worker_debug_host`` = ``localhost``
- (String) Host address of the pydev server.$sentinal$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.$sentinal$Possible values: * Valid hostname * Valid IP address$sentinal$Related options: * None
- (String) 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
* - ``pydev_worker_debug_port`` = ``5678``
- (Port number) Port number that the pydev server will listen on.$sentinal$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.$sentinal$Possible values: * A valid port number$sentinal$Related options: * None
- (Port number) 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

View File

@ -19,20 +19,126 @@
* - **[glance_store]**
-
* - ``vmware_api_retry_count`` = ``10``
- (Integer) The number of VMware API retries.$sentinal$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'.$sentinal$Possible Values: * Any positive integer value$sentinal$Related options: * None
- (Integer) 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
* - ``vmware_ca_file`` = ``/etc/ssl/certs/ca-certificates.crt``
- (String) Absolute path to the CA bundle file.$sentinal$This configuration option enables the operator to use a custom Cerificate Authority File to verify the ESX/vCenter certificate.$sentinal$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.$sentinal$Possible Values: * Any string that is a valid absolute path to a CA file$sentinal$Related options: * vmware_insecure
- (String) 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
* - ``vmware_datastores`` = ``None``
- (Multi-valued) The datastores where the image can be stored.$sentinal$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>.$sentinal$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.$sentinal$Possible Values: * Any string of the format: <datacenter_path>:<datastore_name>:<optional_weight>$sentinal$Related options: * None
- (Multi-valued) 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
* - ``vmware_insecure`` = ``False``
- (Boolean) Set verification of the ESX/vCenter server certificate.$sentinal$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.$sentinal$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 .$sentinal$Possible Values: * True * False$sentinal$Related options: * vmware_ca_file
- (Boolean) 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
* - ``vmware_server_host`` = ``127.0.0.1``
- (String) Address of the ESX/ESXi or vCenter Server target system.$sentinal$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).$sentinal$Possible Values: * A valid IPv4 or IPv6 address * A valid DNS name$sentinal$Related options: * vmware_server_username * vmware_server_password
- (String) 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
* - ``vmware_server_password`` = ``vmware``
- (String) Server password.$sentinal$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.$sentinal$Possible Values: * Any string that is a password corresponding to the username specified using the "vmware_server_username" option$sentinal$Related options: * vmware_server_host * vmware_server_username
- (String) 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
* - ``vmware_server_username`` = ``root``
- (String) Server username.$sentinal$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.$sentinal$Possible Values: * Any string that is the username for a user with appropriate privileges$sentinal$Related options: * vmware_server_host * vmware_server_password
- (String) 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
* - ``vmware_store_image_dir`` = ``/openstack_glance``
- (String) The directory where the glance images will be stored in the datastore.$sentinal$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.$sentinal$Possible Values: * Any string that is a valid path to a directory$sentinal$Related options: * None
- (String) 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
* - ``vmware_task_poll_interval`` = ``5``
- (Integer) Interval in seconds used for polling remote tasks invoked on VMware ESX/VC server.$sentinal$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.$sentinal$Possible Values: * Any positive integer value$sentinal$Related options: * None
- (Integer) 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

View File

@ -113,11 +113,13 @@
Possible Values:
* db : Database ServiceGroup driver * mc : Memcache ServiceGroup driver
* db : Database ServiceGroup driver
* mc : Memcache ServiceGroup driver
Related Options:
* service_down_time (maximum time since last check-in for up service)
* service_down_time (maximum time since last check-in for up service)
* - ``snapshot_name_template`` = ``snapshot-%s``
- (String) DEPRECATED: Template string to be used to generate snapshot names This is not used anymore and will be removed in the O release.
* - ``use_forwarded_for`` = ``False``

View File

@ -25,7 +25,9 @@
Possible values:
* Any string representing an availability zone name * 'nova' is the default value
* Any string representing an availability zone name
* 'nova' is the default value
* - ``default_schedule_zone`` = ``None``
- (String) Availability zone to use when user doesn't specify one.
@ -41,4 +43,6 @@
Possible values:
* Any string representing an availability zone name * 'internal' is the default value
* Any string representing an availability zone name
* 'internal' is the default value

View File

@ -23,4 +23,4 @@
* - ``cert_manager`` = ``nova.cert.manager.CertManager``
- (String) DEPRECATED: Full class name for the Manager for cert
* - ``cert_topic`` = ``cert``
- (String) DEPRECATED: Determines the RPC topic that the cert nodes listen on. For most deployments there is no need to ever change it. Since the nova-cert service is marked for deprecation, the feature to change RPC topic that cert nodes listen may be removed as early as the 15.0.0
- (String) DEPRECATED: Determines the RPC topic that the cert nodes listen on. For most deployments there is no need to ever change it. Since the nova-cert service is marked for deprecation, the feature to change RPC topic that cert nodes listen may be removed as early as the 15.0.0 Ocata release.

View File

@ -155,7 +155,9 @@
* - ``reserve_percent`` = ``10.0``
- (Floating point) Reserve percentage
Percentage of cell capacity to hold in reserve, so the minimum amount of free resource is considered to be; min_free = total * (reserve_percent / 100.0) This option affects both memory and disk utilization. The primary purpose of this reserve is to ensure some space is available for users who want to resize their instance to be larger. Note that currently once the capacity expands into this reserve space this option is ignored.
Percentage of cell capacity to hold in reserve, so the minimum amount of free resource is considered to be; min_free = total
* (reserve_percent / 100.0) This option affects both memory and disk utilization. The primary purpose of this reserve is to ensure some space is available for users who want to resize their instance to be larger. Note that currently once the capacity expands into this reserve space this option is ignored.
* - ``rpc_driver_queue_base`` = ``cells.intercell``
- (String) RPC driver queue base

View File

@ -45,13 +45,13 @@
Possible values
* 'console' (default) or any string representing topic exchange name.
* 'console' (default) or any string representing topic exchange name.
* - ``consoleauth_topic`` = ``consoleauth``
- (String) This option allows you to change the message topic used by nova-consoleauth service when communicating via the AMQP server. Nova Console Authentication server authenticates nova consoles. Users can then access their instances through VNC clients. The Nova API service uses a message queue to communicate with nova-consoleauth to get a VNC console.
Possible Values:
* 'consoleauth' (default) or Any string representing topic exchange name.
* 'consoleauth' (default) or Any string representing topic exchange name.
* - ``executor_thread_pool_size`` = ``64``
- (Integer) Size of executor thread pool.
* - ``fatal_exception_format_errors`` = ``False``

View File

@ -51,7 +51,7 @@
Possible values
* A string representing fully qualified class name.
* A string representing fully qualified class name.
* - ``console_host`` = ``socket.gethostname()``
- (String) Console proxy host to be used to connect to instances on this host. It is the publicly visible name for the console host.
@ -89,7 +89,11 @@
* - ``instance_usage_audit_period`` = ``month``
- (String) Time period to generate instance usages for. It is possible to define optional offset to given period by appending @ character followed by a number defining offset.
Possible values: * period, example: ``hour``, ``day``, ``month` or ``year`` * period with offset, example: ``month@15`` will result in monthly audits starting on 15th day of month.
Possible values:
* period, example: ``hour``, ``day``, ``month` or ``year``
* period with offset, example: ``month@15`` will result in monthly audits starting on 15th day of month.
* - ``instances_path`` = ``$state_path/instances``
- (String) Specifies where instances are stored on the hypervisor's disk. It can point to locally attached storage or a directory on NFS.

View File

@ -23,13 +23,13 @@
Possible values
* An empty list (default) or list of allowed origin hostnames.
* An empty list (default) or list of allowed origin hostnames.
* - ``console_public_hostname`` = ``localhost``
- (String) Publicly visible name for this console host.
Possible values
* Current hostname (default) or any string representing hostname.
* Current hostname (default) or any string representing hostname.
* - ``console_token_ttl`` = ``600``
- (Integer) This option indicates the lifetime of a console auth token. A console auth token is used in authorizing console access for a user. Once the auth token time to live count has elapsed, the token is considered expired. Expired tokens are then deleted.
* - ``consoleauth_manager`` = ``nova.consoleauth.manager.ConsoleAuthManager``

View File

@ -8,9 +8,9 @@
autogenerate-config-doc tool from the openstack-doc-tools repository, or
ask for help on the documentation mailing list, IRC channel or meeting.
.. _nova-crypt:
.. _nova-crypto:
.. list-table:: Description of crypt configuration options
.. list-table:: Description of crypto configuration options
:header-rows: 1
:class: config-ref-table

View File

@ -23,7 +23,13 @@
This configures guestfs to debug messages and push them to Openstack logging system. When set to True, it traces libguestfs API calls and enable verbose debug messages. In order to use the above feature, "libguestfs" package must be installed.
Related options: Since libguestfs access and modifies VM's managed by libvirt, below options should be set to give access to those VM's. * libvirt.inject_key * libvirt.inject_partition * libvirt.inject_password
Related options: Since libguestfs access and modifies VM's managed by libvirt, below options should be set to give access to those VM's.
* libvirt.inject_key
* libvirt.inject_partition
* libvirt.inject_password
* - **[remote_debug]**
-
* - ``host`` = ``None``
@ -33,7 +39,7 @@
Possible Values:
* IP address of a remote host as a command line parameter to a nova service. For Example:
* IP address of a remote host as a command line parameter to a nova service. For Example:
/usr/local/bin/nova-compute --config-file /etc/nova/nova.conf --remote_debug-host <IP address where the debugger is running>
* - ``port`` = ``None``
@ -43,6 +49,6 @@
Possible Values:
* Port number you want to use as a command line parameter to a nova service. For Example:
* Port number you want to use as a command line parameter to a nova service. For Example:
/usr/local/bin/nova-compute --config-file /etc/nova/nova.conf --remote_debug-host <IP address where the debugger is running> --remote_debug-port <port> it's listening on>.

View File

@ -25,7 +25,7 @@
Possible values:
* aes-xts-plain64 (Default), see /proc/crypto for available options.
* aes-xts-plain64 (Default), see /proc/crypto for available options.
* - ``enabled`` = ``False``
- (Boolean) Enables/disables LVM ephemeral storage encryption.
* - ``key_size`` = ``512``

View File

@ -56,4 +56,3 @@
-
* - ``filesystems`` =
- (List) DEPRECATED: List of file systems that are configured in this file in the image_file_url:<list entry name> sections The feature to download images from glance via filesystem is not used and will be removed in the future.

View File

@ -39,7 +39,13 @@
* - ``live_migration_bandwidth`` = ``0``
- (Integer) Maximum bandwidth(in MiB/s) to be used during migration. If set to 0, will choose a suitable default. Some hypervisors do not support this feature and will return an error if bandwidth is not 0. Please refer to the libvirt documentation for further details
* - ``live_migration_completion_timeout`` = ``800``
- (Integer) Time to wait, in seconds, for migration to successfully complete transferring data before aborting the operation. Value is per GiB of guest RAM + disk to be transferred, with lower bound of a minimum of 2 GiB. Should usually be larger than downtime delay * downtime steps. Set to 0 to disable timeouts. - **Mutable** This option can be changed without restarting.
- (Integer) Time to wait, in seconds, for migration to successfully complete transferring data before aborting the operation. Value is per GiB of guest RAM + disk to be transferred, with lower bound of a minimum of 2 GiB. Should usually be larger than downtime delay
* downtime steps. Set to 0 to disable timeouts.
**Mutable**
This option can be changed without restarting.
* - ``live_migration_downtime`` = ``500``
- (Integer) Maximum permitted downtime, in milliseconds, for live migration switchover. Will be rounded up to a minimum of 100ms. Use a large value if guest liveness is unimportant.
* - ``live_migration_downtime_delay`` = ``75``
@ -53,7 +59,7 @@
Related options:
* live_migration_permit_post_copy
* live_migration_permit_post_copy
* - ``live_migration_permit_post_copy`` = ``False``
- (Boolean) This option allows nova to switch an on-going live migration to post-copy mode, i.e., switch the active VM to the one on the destination node before the migration is complete, therefore ensuring an upper bound on the memory that needs to be transferred. Post-copy requires libvirt>=1.3.3 and QEMU>=2.5.0.
@ -65,9 +71,13 @@
Related options:
* live_migration_permit_auto_converge
* live_migration_permit_auto_converge
* - ``live_migration_progress_timeout`` = ``150``
- (Integer) Time to wait, in seconds, for migration to make forward progress in transferring data before aborting the operation. Set to 0 to disable timeouts. - **Mutable** This option can be changed without restarting.
- (Integer) Time to wait, in seconds, for migration to make forward progress in transferring data before aborting the operation. Set to 0 to disable timeouts.
**Mutable**
This option can be changed without restarting.
* - ``live_migration_tunnelled`` = ``False``
- (Boolean) Whether to use tunnelled migration, where migration data is transported over the libvirtd connection. If True, we use the VIR_MIGRATE_TUNNELLED migration flag, avoiding the need to configure the network to allow direct hypervisor to hypervisor communication. If False, use the native transport. If not set, Nova will choose a sensible default based on, for example the availability of native encryption support in the hypervisor.
* - ``live_migration_uri`` = ``None``

View File

@ -25,11 +25,11 @@
Possible values:
* Any valid IP address. The default is the address of the Nova API server.
* Any valid IP address. The default is the address of the Nova API server.
Related options:
* metadata_port
* metadata_port
* - ``metadata_listen`` = ``0.0.0.0``
- (String) The IP address on which the metadata API will listen.
* - ``metadata_listen_port`` = ``8775``
@ -41,7 +41,7 @@
Related options:
* metadata_host
* metadata_host
* - ``metadata_workers`` = ``None``
- (Integer) Number of workers for metadata service. The default will be the number of CPUs available.
* - ``vendordata_driver`` = ``nova.api.metadata.vendordata_json.JsonFileVendorData``

View File

@ -79,7 +79,7 @@
Possible values:
* Any string representing a floating IP pool name
* Any string representing a floating IP pool name
* - ``defer_iptables_apply`` = ``False``
- (Boolean) Whether to batch up the application of IPTables rules during a host restart and apply all at the end of the init phase.
* - ``dhcp_domain`` = ``novalocal``
@ -141,21 +141,27 @@
Possible values:
* Any positive integer
* Any positive integer
Related options:
* ebtables_retry_interval
* ebtables_retry_interval
* - ``ebtables_retry_interval`` = ``1.0``
- (Floating point) This option determines the time, in seconds, that the system will sleep in between ebtables retries. Note that each successive retry waits a multiple of this value, so for example, if this is set to the default of 1.0 seconds, and ebtables_exec_attempts is 4, after the first failure, the system will sleep for 1 * 1.0 seconds, after the second failure it will sleep 2 * 1.0 seconds, and after the third failure it will sleep 3 * 1.0 seconds.
- (Floating point) This option determines the time, in seconds, that the system will sleep in between ebtables retries. Note that each successive retry waits a multiple of this value, so for example, if this is set to the default of 1.0 seconds, and ebtables_exec_attempts is 4, after the first failure, the system will sleep for 1
* 1.0 seconds, after the second failure it will sleep 2
* 1.0 seconds, and after the third failure it will sleep 3
* 1.0 seconds.
Possible values:
* Any non-negative float or integer. Setting this to zero will result in no waiting between attempts.
* Any non-negative float or integer. Setting this to zero will result in no waiting between attempts.
Related options:
* ebtables_exec_attempts
* ebtables_exec_attempts
* - ``firewall_driver`` = ``None``
- (String) Firewall driver to use with ``nova-network`` service.
@ -227,7 +233,7 @@
Possible values:
* Full Python path to the class to be used
* Full Python path to the class to be used
* - ``force_dhcp_release`` = ``True``
- (Boolean) When this option is True, a call is made to release the DHCP for the instance when that instance is terminated.
@ -275,33 +281,33 @@
Possible values:
* Full Python path to the class to be used
* Full Python path to the class to be used
* - ``iptables_bottom_regex`` =
- (String) This expression, if defined, will select any matching iptables rules and place them at the bottom when applying metadata changes to the rules.
Possible values:
* Any string representing a valid regular expression, or an empty string
* Any string representing a valid regular expression, or an empty string
Related options:
* iptables_top_regex
* iptables_top_regex
* - ``iptables_drop_action`` = ``DROP``
- (String) By default, packets that do not pass the firewall are DROPped. In many cases, though, an operator may find it more useful to change this from DROP to REJECT, so that the user issuing those packets may have a better idea as to what's going on, or LOGDROP in order to record the blocked traffic before DROPping.
Possible values:
* A string representing an iptables chain. The default is DROP.
* A string representing an iptables chain. The default is DROP.
* - ``iptables_top_regex`` =
- (String) This expression, if defined, will select any matching iptables rules and place them at the top when applying metadata changes to the rules.
Possible values:
* Any string representing a valid regular expression, or an empty string
* Any string representing a valid regular expression, or an empty string
Related options:
* iptables_bottom_regex
* iptables_bottom_regex
* - ``l3_lib`` = ``nova.network.l3.LinuxNetL3``
- (String) This option allows you to specify the L3 management library to be used.
@ -373,7 +379,7 @@
Possible values:
* Any positive integer if a limited timeout is desired, or zero if the calls should wait forever for a response.
* Any positive integer if a limited timeout is desired, or zero if the calls should wait forever for a response.
* - ``public_interface`` = ``eth0``
- (String) This is the name of the network interface for public IP addresses. The default is 'eth0'.

View File

@ -31,7 +31,13 @@
defines an alias for the Intel QuickAssist card. (multi valued). Valid key values are :
* "name": Name of the PCI alias. * "product_id": Product ID of the device in hexadecimal. * "vendor_id": Vendor ID of the device in hexadecimal. * "device_type": Type of PCI device. Valid values are: "type-PCI", "type-PF" and "type-VF".
* "name": Name of the PCI alias.
* "product_id": Product ID of the device in hexadecimal.
* "vendor_id": Vendor ID of the device in hexadecimal.
* "device_type": Type of PCI device. Valid values are: "type-PCI", "type-PF" and "type-VF".
* - ``pci_passthrough_whitelist`` = ``[]``
- (Multi-valued) White list of PCI devices available to VMs.
@ -45,7 +51,15 @@
Valid key values are :
* "vendor_id": Vendor ID of the device in hexadecimal. * "product_id": Product ID of the device in hexadecimal. * "address": PCI address of the device. * "devname": Device name of the device (for e.g. interface name). Not all PCI devices have a name. * "<tag>": Additional <tag> and <tag_value> used for matching PCI devices. Supported <tag>: "physical_network".
* "vendor_id": Vendor ID of the device in hexadecimal.
* "product_id": Product ID of the device in hexadecimal.
* "address": PCI address of the device.
* "devname": Device name of the device (for e.g. interface name). Not all PCI devices have a name.
* "<tag>": Additional <tag> and <tag_value> used for matching PCI devices. Supported <tag>: "physical_network".
Valid examples are:

View File

@ -27,7 +27,7 @@
Possible values:
* 0 (default) or any positive integer representing number of seconds.
* 0 (default) or any positive integer representing number of seconds.
* - ``max_local_block_devices`` = ``3``
- (Integer) Maximum number of devices that will result in a local image being created on the hypervisor node.
@ -61,7 +61,7 @@
Possible values:
* 86400 (default) or any positive integer representing number of seconds.
* 86400 (default) or any positive integer representing number of seconds.
* - ``resize_fs_using_block_device`` = ``False``
- (Boolean) If enabled, attempt to resize the filesystem by accessing the image over a block device. This is done by the host and may not be necessary if the image contains a recent version of cloud-init. Possible mechanisms require the nbd driver (for qcow and raw), or loop (for raw).
* - ``until_refresh`` = ``0``
@ -69,4 +69,4 @@
Possible values:
* 0 (default) or any positive integer.
* 0 (default) or any positive integer.

View File

@ -25,103 +25,131 @@
Related options:
* quota_networks: CRUD operations on tenant networks are only available when using nova-network and nova-network is itself deprecated.
* quota_networks CRUD operations on tenant networks are only available when using nova-network and nova-network is itself deprecated.
* - ``quota_cores`` = ``20``
- (Integer) The number of instance cores or VCPUs allowed per project.
Possible values:
* 20 (default) or any positive integer. * -1 : treated as unlimited.
* 20 (default) or any positive integer.
* -1 : treated as unlimited.
* - ``quota_driver`` = ``nova.quota.DbQuotaDriver``
- (String) DEPRECATED: Provides abstraction for quota checks. Users can configure a specific driver to use for quota checks.
Possible values:
* nova.quota.DbQuotaDriver (default) or any string representing fully qualified class name.
* nova.quota.DbQuotaDriver (default) or any string representing fully qualified class name.
* - ``quota_fixed_ips`` = ``-1``
- (Integer) The number of fixed IPs allowed per project (this should be at least the number of instances allowed). Unlike floating IPs, fixed IPs are allocated dynamically by the network component when instances boot up.
Possible values:
* -1 (default) : treated as unlimited. * Any positive integer.
* -1 (default) : treated as unlimited.
* Any positive integer.
* - ``quota_floating_ips`` = ``10``
- (Integer) The number of floating IPs allowed per project. Floating IPs are not allocated to instances by default. Users need to select them from the pool configured by the OpenStack administrator to attach to their instances.
Possible values:
* 10 (default) or any positive integer. * -1 : treated as unlimited.
* 10 (default) or any positive integer.
* -1 : treated as unlimited.
* - ``quota_injected_file_content_bytes`` = ``10240``
- (Integer) The number of bytes allowed per injected file.
Possible values:
* 10240 (default) or any positive integer representing number of bytes. * -1 : treated as unlimited.
* 10240 (default) or any positive integer representing number of bytes.
* -1 : treated as unlimited.
* - ``quota_injected_file_path_length`` = ``255``
- (Integer) The maximum allowed injected file path length.
Possible values:
* 255 (default) or any positive integer. * -1 : treated as unlimited.
* 255 (default) or any positive integer.
* -1 : treated as unlimited.
* - ``quota_injected_files`` = ``5``
- (Integer) The number of injected files allowed. It allow users to customize the personality of an instance by injecting data into it upon boot. Only text file injection is permitted. Binary or zip files won't work. During file injection, any existing files that match specified files are renamed to include .bak extension appended with a timestamp.
Possible values:
* 5 (default) or any positive integer. * -1 : treated as unlimited.
* 5 (default) or any positive integer.
* -1 : treated as unlimited.
* - ``quota_instances`` = ``10``
- (Integer) The number of instances allowed per project.
Possible Values
* 10 (default) or any positive integer. * -1 : treated as unlimited.
* 10 (default) or any positive integer.
* -1 : treated as unlimited.
* - ``quota_key_pairs`` = ``100``
- (Integer) The maximum number of key pairs allowed per user. Users can create at least one key pair for each project and use the key pair for multiple instances that belong to that project.
Possible values:
* 100 (default) or any positive integer. * -1 : treated as unlimited.
* 100 (default) or any positive integer.
* -1 : treated as unlimited.
* - ``quota_metadata_items`` = ``128``
- (Integer) The number of metadata items allowed per instance. User can associate metadata while instance creation in the form of key-value pairs.
Possible values:
* 128 (default) or any positive integer. * -1 : treated as unlimited.
* 128 (default) or any positive integer.
* -1 : treated as unlimited.
* - ``quota_networks`` = ``3``
- (Integer) DEPRECATED: This option controls the number of private networks that can be created per project (or per tenant).
Related options:
* enable_network_quota: CRUD operations on tenant networks are only available when using nova-network and nova-network is itself deprecated.
* enable_network_quota CRUD operations on tenant networks are only available when using nova-network and nova-network is itself deprecated.
* - ``quota_ram`` = ``51200``
- (Integer) The number of megabytes of instance RAM allowed per project.
Possible values:
* 51200 (default) or any positive integer. * -1 : treated as unlimited.
* 51200 (default) or any positive integer.
* -1 : treated as unlimited.
* - ``quota_security_group_rules`` = ``20``
- (Integer) The number of security rules per security group. The associated rules in each security group control the traffic to instances in the group.
Possible values:
* 20 (default) or any positive integer. * -1 : treated as unlimited.
* 20 (default) or any positive integer.
* -1 : treated as unlimited.
* - ``quota_security_groups`` = ``10``
- (Integer) The number of security groups per project.
Possible values:
* 10 (default) or any positive integer. * -1 : treated as unlimited.
* 10 (default) or any positive integer.
* -1 : treated as unlimited.
* - ``quota_server_group_members`` = ``10``
- (Integer) Add quota values to constrain the number of servers per server group.
Possible values:
* 10 (default) or any positive integer. * -1 : treated as unlimited.
* 10 (default) or any positive integer.
* -1 : treated as unlimited.
* - ``quota_server_groups`` = ``10``
- (Integer) Add quota values to constrain the number of server groups per project. Server group used to control the affinity and anti-affinity scheduling policy for a group of servers or instances. Reducing the quota will not affect any existing group, but new servers will not be allowed into groups that have become over quota.
Possible values:
* 10 (default) or any positive integer. * -1 : treated as unlimited.
* 10 (default) or any positive integer.
* -1 : treated as unlimited.
* - **[cells]**
-
* - ``bandwidth_update_interval`` = ``600``

View File

@ -53,7 +53,9 @@
Possible values:
* Any valid positive integer or float value * Default value is 0.0
* Any valid positive integer or float value
* Default value is 0.0
NOTE: This can be set per-compute, or if set to 0.0, the value set on the scheduler node(s) or compute node(s) will be used and defaulted to 16.0'.
* - ``disk_allocation_ratio`` = ``0.0``
@ -63,7 +65,9 @@
Possible values:
* Any valid positive integer or float value * Default value is 0.0
* Any valid positive integer or float value
* Default value is 0.0
NOTE: This can be set per-compute, or if set to 0.0, the value set on the scheduler node(s) or compute node(s) will be used and defaulted to 1.0'.
* - ``disk_weight_multiplier`` = ``1.0``
@ -121,7 +125,9 @@
Possible values:
* Any valid positive integer or float value * Default value is 0.0
* Any valid positive integer or float value
* Default value is 0.0
NOTE: This can be set per-compute, or if set to 0.0, the value set on the scheduler node(s) or compute node(s) will be used and defaulted to 1.5.
* - ``ram_weight_multiplier`` = ``1.0``
@ -139,13 +145,13 @@
Possible values:
* Any positive integer representing amount of disk in MB to reserve for the host.
* Any positive integer representing amount of disk in MB to reserve for the host.
* - ``reserved_host_memory_mb`` = ``512``
- (Integer) Amount of memory in MB to reserve for the host so that it is always available to host processes. The host resources usage is reported back to the scheduler continuously from nova-compute running on the compute node. To prevent the host memory from being considered as available, this option is used to reserve memory for the host.
Possible values:
* Any positive integer representing amount of memory in MB to reserve for the host.
* Any positive integer representing amount of memory in MB to reserve for the host.
* - ``reserved_huge_pages`` = ``None``
- (Unknown) Reserves a number of huge/large memory pages per NUMA host cells
@ -189,11 +195,11 @@
Other options are:
* 'caching_scheduler' which aggressively caches the system state for better individual scheduler performance at the risk of more retries when running multiple schedulers.
* 'caching_scheduler' which aggressively caches the system state for better individual scheduler performance at the risk of more retries when running multiple schedulers.
* 'chance_scheduler' which simply picks a host at random.
* 'chance_scheduler' which simply picks a host at random.
* 'fake_scheduler' which is used for testing.
* 'fake_scheduler' which is used for testing.
* Related options:
@ -353,19 +359,19 @@
* - ``weight_multiplier`` = ``1.0``
- (Floating point) When using metrics to weight the suitability of a host, you can use this option to change how the calculated weight influences the weight assigned to a host as follows:
* Greater than 1.0: increases the effect of the metric on overall weight.
* Greater than 1.0: increases the effect of the metric on overall weight.
* Equal to 1.0: No change to the calculated weight.
* Equal to 1.0: No change to the calculated weight.
* Less than 1.0, greater than 0: reduces the effect of the metric on overall weight.
* Less than 1.0, greater than 0: reduces the effect of the metric on overall weight.
* 0: The metric value is ignored, and the value of the 'weight_of_unavailable' option is returned instead.
* 0: The metric value is ignored, and the value of the 'weight_of_unavailable' option is returned instead.
* Greater than -1.0, less than 0: the effect is reduced and reversed.
* Greater than -1.0, less than 0: the effect is reduced and reversed.
* -1.0: the effect is reversed
* -1.0: the effect is reversed
* Less than -1.0: the effect is increased proportionally and reversed.
* Less than -1.0: the effect is increased proportionally and reversed.
Valid values are numeric, either integer or float.
@ -377,11 +383,11 @@
* - ``weight_of_unavailable`` = ``-10000.0``
- (Floating point) When any of the following conditions are met, this value will be used in place of any actual metric value:
* One of the metrics named in 'weight_setting' is not available for a host, and the value of 'required' is False.
* One of the metrics named in 'weight_setting' is not available for a host, and the value of 'required' is False.
* The ratio specified for a metric in 'weight_setting' is 0.
* The ratio specified for a metric in 'weight_setting' is 0.
* The 'weight_multiplier' option is set to 0.
* The 'weight_multiplier' option is set to 0.
This option is only used by the FilterScheduler and its subclasses; if you use a different scheduler, this option has no effect.
@ -395,14 +401,14 @@
As an example, let's consider the case where this option is set to:
``name1=1.0, name2=-1.3``
``name1=1.0, name2=-1.3``
The final weight will be:
``(name1.value * 1.0) + (name2.value * -1.3)``
``(name1.value * 1.0) + (name2.value * -1.3)``
This option is only used by the FilterScheduler and its subclasses; if you use a different scheduler, this option has no effect.
* Related options:
weight_of_unavailable
weight_of_unavailable

View File

@ -25,7 +25,7 @@
Related options:
* ``monkey_patch_modules``: This must have values set for this option to have any effect
* ``monkey_patch_modules``: This must have values set for this option to have any effect
* - ``monkey_patch_modules`` = ``nova.compute.api:nova.notifications.notify_decorator``
- (List) List of modules/decorators to monkey patch.
@ -33,8 +33,12 @@
Possible values:
* nova.compute.api:nova.notifications.notify_decorator * nova.api.ec2.cloud:nova.notifications.notify_decorator * [...]
* nova.compute.api:nova.notifications.notify_decorator
* nova.api.ec2.cloud:nova.notifications.notify_decorator
* [...]
Related options:
* ``monkey_patch``: This must be set to ``True`` for this option to have any effect
* ``monkey_patch``: This must be set to ``True`` for this option to have any effect

View File

@ -21,7 +21,9 @@
* - ``api_paste_config`` = ``api-paste.ini``
- (String) This option represents a file name for the paste.deploy config for nova-api.
Possible values: * A string representing file name for the paste.deploy config.
Possible values:
* A string representing file name for the paste.deploy config.
* - ``client_socket_timeout`` = ``900``
- (Integer) This option specifies the timeout for client connections' socket operations. If an incoming connection is idle for this number of seconds it will be closed. It indicates timeout on individual read/writes on the socket connection. To wait forever set to 0.
* - ``default_pool_size`` = ``1000``
@ -31,11 +33,13 @@
Possible values:
* True : reuse HTTP connection. * False : closes the client socket connection explicitly.
* True : reuse HTTP connection.
* False : closes the client socket connection explicitly.
Related options:
* tcp_keepidle
* tcp_keepidle
* - ``max_header_line`` = ``16384``
- (Integer) This option specifies the maximum line size of message headers to be accepted. max_header_line may need to be increased when using large tokens (typically those generated by the Keystone v3 API with big service catalogs).
@ -45,43 +49,45 @@
Possible values:
* None (default) - the request scheme is not influenced by any HTTP headers. * Valid HTTP header, like HTTP_X_FORWARDED_PROTO
* None (default) - the request scheme is not influenced by any HTTP headers.
* Valid HTTP header, like HTTP_X_FORWARDED_PROTO
* - ``ssl_ca_file`` = ``None``
- (String) This option allows setting path to the CA certificate file that should be used to verify connecting clients.
Possible values:
* String representing path to the CA certificate file.
* String representing path to the CA certificate file.
Related options:
* enabled_ssl_apis
* enabled_ssl_apis
* - ``ssl_cert_file`` = ``None``
- (String) This option allows setting path to the SSL certificate of API server.
Possible values:
* String representing path to the SSL certificate.
* String representing path to the SSL certificate.
Related options:
* enabled_ssl_apis
* enabled_ssl_apis
* - ``ssl_key_file`` = ``None``
- (String) This option specifies the path to the file where SSL private key of API server is stored when SSL is in effect.
Possible values:
* String representing path to the SSL private key.
* String representing path to the SSL private key.
Related options:
* enabled_ssl_apis
* enabled_ssl_apis
* - ``tcp_keepidle`` = ``600``
- (Integer) This option sets the value of TCP_KEEPIDLE in seconds for each server socket. It specifies the duration of time to keep connection active. TCP generates a KEEPALIVE transmission for an application that requests to keep connection active. Not supported on OS X.
Related options:
* keep_alive
* keep_alive
* - ``wsgi_log_format`` = ``%(client_ip)s "%(request_line)s" status: %(status_code)s len: %(body_length)s time: %(wall_seconds).7f``
- (String) It represents a python format string that is used as the template to generate log lines. The following values can be formatted into it: client_ip, date_time, request_line, status_code, body_length, wall_seconds.
@ -89,4 +95,6 @@
Possible values:
* '%(client_ip)s "%(request_line)s" status: %(status_code)s' 'len: %(body_length)s time: %(wall_seconds).7f' (default) * Any formatted string formed by specific values.
* '%(client_ip)s "%(request_line)s" status: %(status_code)s' 'len: %(body_length)s time: %(wall_seconds).7f' (default)
* Any formatted string formed by specific values.

View File

@ -23,7 +23,7 @@
Possible values
* 'nova.console.xvp.XVPConsoleProxy' (default) or a string representing fully classified class name of console driver.
* 'nova.console.xvp.XVPConsoleProxy' (default) or a string representing fully classified class name of console driver.
* - **[libvirt]**
-
* - ``xen_hvmloader_path`` = ``/usr/lib/xen/boot/hvmloader``
@ -35,7 +35,11 @@
Specifies the path in which the XenAPI guest agent should be located. If the agent is present, network configuration is not injected into the image.
Related options: For this option to have an effect: * ``flat_injected`` should be set to ``True`` * ``compute_driver`` should be set to ``xenapi.XenAPIDriver``
Related options: For this option to have an effect:
* ``flat_injected`` should be set to ``True``
* ``compute_driver`` should be set to ``xenapi.XenAPIDriver``
* - ``agent_resetnetwork_timeout`` = ``60``
- (Integer) Number of seconds to wait for agent's reply to resetnetwork request.
@ -49,7 +53,11 @@
This config option determines how long the xapi 'agent' plugin shall wait to read the response off of xenstore for a given request/command. If the agent on the instance fails to write the result in this time period, the operation is considered to have timed out.
Related options: * ``agent_version_timeout`` * ``agent_resetnetwork_timeout``
Related options:
* ``agent_version_timeout``
* ``agent_resetnetwork_timeout``
* - ``agent_version_timeout`` = ``300``
- (Integer) Number of seconds to wait for agent't reply to version request.
@ -103,7 +111,9 @@
This configuration option suggests whether the use of agent should be enabled or not regardless of what image properties are present. Image properties have an effect only when this is set to ``True``. Read description of config option ``use_agent_default`` for more information.
Related options: * ``use_agent_default``
Related options:
* ``use_agent_default``
* - ``image_compression_level`` = ``None``
- (Integer) Compression level for images.
@ -187,7 +197,7 @@
Possible options:
* Any string that represents a bridge name(default is xapi1).
* Any string that represents a bridge name(default is xapi1).
* - ``remap_vbd_dev`` = ``False``
- (Boolean) Used to enable the remapping of VBD dev. (Works around an issue in Ubuntu Maverick)
* - ``remap_vbd_dev_prefix`` = ``sd``
@ -235,11 +245,11 @@
Possible values:
* `all`: will download all images.
* ``all``: will download all images.
* `some`: will only download images that have the image_property `bittorrent=true`.
* ``some``: will only download images that have the image_property ``bittorrent=true``.
* `none`: will turnoff downloading images via Bit Torrent.
* ``none``: will turnoff downloading images via Bit Torrent.
* - ``torrent_listen_port_end`` = ``6891``
- (Port number) End of port range to listen on
* - ``torrent_listen_port_start`` = ``6881``
@ -259,7 +269,9 @@
Note that if this configuration is set to ``True`` when the agent is not present, the boot times will increase significantly.
Related options: * ``disable_agent``
Related options:
* ``disable_agent``
* - ``use_join_force`` = ``True``
- (Boolean) When adding new host to a pool, this will append a --force flag to the command, forcing hosts to join a pool, even if they have different CPUs.