glance VERSION - en to en_GB translation catalogue (39 entries)

en: 
    Deployment flavor to use in the server application pipeline.
    
    Provide a string value representing the appropriate deployment
    flavor used in the server application pipeline. 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
en_GB: 
    Deployment flavour to use in the server application pipeline.
    
    Provide a string value representing the appropriate deployment
    flavour used in the server application pipeline. 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

en: 
    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 helps avoid storage of credentials in the
    database.
    
    Possible values:
        * None
        * String value representing a valid configuration file path
    
    Related options:
        * None
en_GB: 
    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 the Swift storage backend for image
    storage as it helps avoid storage of credentials in the
    database.
    
    Possible values:
        * None
        * String value representing a valid configuration file path
    
    Related options:
        * None

en: 
    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
en_GB: 
    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

en: 
    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
en_GB: 
    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 integer 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

en: 
    List of notifications to be disabled.
    
    Specify a list of notifications that should not be emitted.
    A notification can be given either as a notification type to
    disable a single event notification, or as a notification group
    prefix to disable all event notifications within a group.
    
    Possible values:
        A comma-separated list of individual notification types or
        notification groups to be disabled. Currently supported groups:
    
        * image
        * image.member
        * task
        * metadef_namespace
        * metadef_object
        * metadef_property
        * metadef_resource_type
        * metadef_tag
    
        For a complete listing and description of each event refer to:
        https://docs.openstack.org/glance/latest/admin/notifications.html
    
        The values must be specified as: <group_name>.<event_name>
        For example: image.create,task.success,metadef_tag
    
    Related options:
        * None
en_GB: 
    List of notifications to be disabled.
    
    Specify a list of notifications that should not be emitted.
    A notification can be given either as a notification type to
    disable a single event notification or as a notification group
    prefix to disable all event notifications within a group.
    
    Possible values:
        A comma-separated list of individual notification types or
        notification groups to be disabled. Currently supported groups:
    
        * image
        * image.member
        * task
        * metadef_namespace
        * metadef_object
        * metadef_property
        * metadef_resource_type
        * metadef_tag
    
        For a complete listing and description of each event refer to:
        https://docs.openstack.org/glance/latest/admin/notifications.html
    
        The values must be specified as: <group_name>.<event_name>
        For example: image.create,task.success,metadef_tag
    
    Related options:
        * None

en: 
    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
en_GB: 
    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 catalogues). 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

en: 
    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
en_GB: 
    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
    1,099,511,627,776 bytes (1 TiB).
    
    NOTES:
        * This value should only be increased after careful
          consideration and must be set less than or equal to
          8 EiB (9,223,372,036,854,775,808).
        * 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 9,223,372,036,854,775,808

en: 
    Name of the paste configuration file.
    
    Provide a string value representing the name of the paste
    configuration file to use for configuring pipelines 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
en_GB: 
    Name of the paste configuration file.
    
    Provide a string value representing the name of the paste
    configuration file to use for configuring pipelines 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 needs
          not be edited in most cases as it comes with ready-made
          pipelines for all common deployment flavours.
    
    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:
        * flavour

en: 
    Path to the python interpreter to use when spawning external
    processes. If left unspecified, this will be sys.executable, which should
    be the same interpreter running Glance itself. However, in some situations
    (for example, uwsgi) sys.executable may not actually point to a python
    interpreter and an alternative value must be set.
en_GB: 
    Path to the Python interpreter to use when spawning external
    processes. If left unspecified, this will be sys.executable, which should
    be the same interpreter running Glance itself. However, in some situations
    (for example, uwsgi) sys.executable may not actually point to a Python
    interpreter and an alternative value must be set.

en: 
    Public url endpoint to use for Glance versions response.
    
    This is the public url endpoint that will appear in the Glance
    "versions" response. If no value is specified, the endpoint that is
    displayed in the version's response is that of the host running the
    API service. Change the endpoint to represent the proxy URL if the
    API service is running behind a proxy. If the service is running
    behind a load balancer, add the load balancer's URL for this value.
    
    Possible values:
        * None
        * Proxy URL
        * Load balancer URL
    
    Related options:
        * None
en_GB: 
    Public URL endpoint to use for Glance versions response.
    
    This is the public URL endpoint that will appear in the Glance
    "versions" response. If no value is specified, the endpoint that is
    displayed in the version's response is that of the host running the
    API service. Change the endpoint to represent the proxy URL if the
    API service is running behind a proxy. If the service is running
    behind a load balancer, add the load balancer's URL for this value.
    
    Possible values:
        * None
        * Proxy URL
        * Load balancer URL
    
    Related options:
        * None

en: 
    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
en_GB: 
    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

en: 
    Secure hashing algorithm used for computing the 'os_hash_value' property.
    
    This option configures the Glance "multihash", which consists of two
    image properties: the 'os_hash_algo' and the 'os_hash_value'.  The
    'os_hash_algo' will be populated by the value of this configuration
    option, and the 'os_hash_value' will be populated by the hexdigest computed
    when the algorithm is applied to the uploaded or imported image data.
    
    The value must be a valid secure hash algorithm name recognized by the
    python 'hashlib' library.  You can determine what these are by examining
    the 'hashlib.algorithms_available' data member of the version of the
    library being used in your Glance installation.  For interoperability
    purposes, however, we recommend that you use the set of secure hash
    names supplied by the 'hashlib.algorithms_guaranteed' data member because
    those algorithms are guaranteed to be supported by the 'hashlib' library
    on all platforms.  Thus, any image consumer using 'hashlib' locally should
    be able to verify the 'os_hash_value' of the image.
    
    The default value of 'sha512' is a performant secure hash algorithm.
    
    If this option is misconfigured, any attempts to store image data will fail.
    For that reason, we recommend using the default value.
    
    Possible values:
        * Any secure hash algorithm name recognized by the Python 'hashlib'
          library
    
    Related options:
        * None
en_GB: 
    Secure hashing algorithm used for computing the 'os_hash_value' property.
    
    This option configures the Glance "multihash", which consists of two
    image properties: the 'os_hash_algo' and the 'os_hash_value'.  The
    'os_hash_algo' will be populated by the value of this configuration
    option, and the 'os_hash_value' will be populated by the hexdigest computed
    when the algorithm is applied to the uploaded or imported image data.
    
    The value must be a valid secure hash algorithm name recognised by the
    python 'hashlib' library.  You can determine what these are by examining
    the 'hashlib.algorithms_available' data member of the version of the
    library being used in your Glance installation.  For interoperability
    purposes, however, we recommend that you use the set of secure hash
    names supplied by the 'hashlib.algorithms_guaranteed' data member because
    those algorithms are guaranteed to be supported by the 'hashlib' library
    on all platforms.  Thus, any image consumer using 'hashlib' locally should
    be able to verify the 'os_hash_value' of the image.
    
    The default value of 'sha512' is a performant secure hash algorithm.
    
    If this option is misconfigured, any attempts to store image data will fail.
    For that reason, we recommend using the default value.
    
    Possible values:
        * Any secure hash algorithm name recognised by the Python 'hashlib'
          library
    
    Related options:
        * None

en: 
    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
en_GB: 
    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
    re-establishment.
    
    Possible values:
        * Positive integer value representing time in seconds
    
    Related options:
        * None

en: 
    Specify metadata prefix to be set on the target image when using
    glance-download. All other properties coming from the source image won't be set
    on the target image. If specified metadata does not exist on the source image
    it won't be set on the target image. Note you can't set the os_glance prefix
    as it is reserved by glance, so the related properties won't be set on the
    target image.
    
    Possible values:
        * List containing extra_properties prefixes: ['os_', 'architecture']
en_GB: 
    Specify metadata prefix to be set on the target image when using
    glance-download. All other properties coming from the source image won't be set
    on the target image. If specified metadata does not exist on the source image
    it won't be set on the target image. Note you can't set the os_glance prefix
    as it is reserved by Glance, so the related properties won't be set on the
    target image.
    
    Possible values:
        * List containing extra_properties prefixes: ['os_', 'architecture']

en: 
    The URL to this worker.
    
    If this is set, other glance workers will know how to contact this one
    directly if needed. For image import, a single worker stages the image
    and other workers need to be able to proxy the import request to the
    right one.
    
    If unset, this will be considered to be `public_endpoint`, which
    normally would be set to the same value on all workers, effectively
    disabling the proxying behavior.
    
    Possible values:
        * A URL by which this worker is reachable from other workers
    
    Related options:
        * public_endpoint
en_GB: 
    The URL to this worker.
    
    If this is set, other glance workers will know how to contact this one
    directly if needed. For image import, a single worker stages the image
    and other workers need to be able to proxy the import request to the
    right one.
    
    If unset, this will be considered to be `public_endpoint`, which
    normally would be set to the same value on all workers, effectively
    disabling the proxying behaviour.
    
    Possible values:
        * A URL by which this worker is reachable from other workers
    
    Related options:
        * public_endpoint

en: 
    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``
en_GB: 
    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 realise 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``

en: 
    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
en_GB: 
    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 clean-up if the image
    cache grew beyond the size specified here. After the clean-up, the size of
    cache is less than or equal to size specified here.
    
    Possible values:
        * Any non-negative integer
    
    Related options:
        * None

en: 
    This option has been removed in Wallaby.  Because there is no migration path
    for installations that had owner_is_tenant==False, we have defined this option
    so that the code can probe the config file and refuse to start the api service
    if the deployment has been using that setting.
en_GB: 
    This option has been removed in Wallaby.  Because there is no migration path
    for installations that had owner_is_tenant==False, we have defined this option
    so that the code can probe the config file and refuse to start the API service
    if the deployment has been using that setting.

en: --os_auth_url option or OS_AUTH_URL environment variable required when keystone authentication strategy is enabled
en_GB: --os_auth_url option or OS_AUTH_URL environment variable required when Keystone authentication strategy is enabled

en: An image file url
en_GB: An image file URL

en: An image schema url
en_GB: An image schema URL

en: An image self url
en_GB: An image self URL

en: Authorization failed.
en_GB: Authorisation failed.

en: Failed to initialize the image cache database. Got error: %s
en_GB: Failed to initialise the image cache database. Got error: %s

en: Invalid service catalog json.
en_GB: Invalid service catalogue json.

en: Param values can't contain 4 byte unicode.
en_GB: Param values can't contain 4 byte Unicode.

en: Pointer `%s` contains "~" not part of a recognized escape sequence.
en_GB: Pointer `%s` contains "~" not part of a recognised escape sequence.

en: Property names can't contain 4 byte unicode.
en_GB: Property names can't contain 4 byte Unicode.

en: Redirecting to %(uri)s for authorization.
en_GB: Redirecting to %(uri)s for authorisation.

en: Specifying both 'visibility' and 'is_public' is not permiitted.
en_GB: Specifying both 'visibility' and 'is_public' is not permitted.

en: Suppressed respawn as %(serv)s was %(rsn)s.
en_GB: Suppressed re-spawn as %(serv)s was %(rsn)s.

en: The given uri is not valid. Please specify a valid uri from the following list of supported uri %(supported)s
en_GB: The given URI is not valid. Please specify a valid URI from the following list of supported URI %(supported)s

en: Unrecognized JSON Schema draft version
en_GB: Unrecognised JSON Schema draft version

en: You are not authorized to complete %(action)s action.
en_GB: You are not authorised to complete %(action)s action.

en: You are not authorized to complete this action.
en_GB: You are not authorised to complete this action.

en: You are not authorized to lookup image %s.
en_GB: You are not authorised to lookup image %s.

en: You are not authorized to lookup the members of the image %s.
en_GB: You are not authorised to lookup the members of the image %s.

en: checksum (%s) is not the correct size for md5 (should be 16 bytes)
en_GB: checksum (%s) is not the correct size for MD5 (should be 16 bytes)

en: md5 hash of image contents.
en_GB: MD5 hash of image contents.
