Swift Release Notes - en to en_GB translation catalogue (58 entries)

en: ACLs now work with unicode in user/account names.
en_GB: ACLs now work with Unicode in user/account names.

en: Add root containers with compactible ranges to recon cache.
en_GB: Add root containers with compatible ranges to recon cache.

en: Add support for PROXY protocol v1 to the proxy server. This allows the Swift proxy server to log accurate client IP addresses when there is a proxy or SSL-terminator between the client and the Swift proxy server.  Example servers supporting this PROXY protocol include stunnel, haproxy, hitch, and varnish. See the sample proxy server config file for the appropriate config setting to enable or disable this functionality.
en_GB: Add support for PROXY protocol v1 to the proxy server. This allows the Swift proxy server to log accurate client IP addresses when there is a proxy or SSL-terminator between the client and the Swift proxy server.  Example servers supporting this PROXY protocol include stunnel, HAProxy, hitch, and Varnish. See the sample proxy server config file for the appropriate config setting to enable or disable this functionality.

en: Added "emergency mode" hooks in the account and container replicators. These options may be used to prioritize moving handoff partitions to primary locations more quickly. This helps when adding capacity to a ring.
en_GB: Added "emergency mode" hooks in the account and container replicators. These options may be used to prioritise moving handoff partitions to primary locations more quickly. This helps when adding capacity to a ring.

en: Added a ``ring_ip`` option for various object services. This may be used to find own devices in the ring in a containerized environment where the ``bind_ip`` may not appear in the ring at all.
en_GB: Added a ``ring_ip`` option for various object services. This may be used to find own devices in the ring in a containerised environment where the ``bind_ip`` may not appear in the ring at all.

en: Added a new config option, ``rows_per_shard``, to specify how many objects should be in each shard when scanning for ranges. The default is ``shard_container_threshold / 2``, preserving existing behavior.
en_GB: Added a new config option, ``rows_per_shard``, to specify how many objects should be in each shard when scanning for ranges. The default is ``shard_container_threshold / 2``, preserving existing behaviour.

en: Added a new middleware to allow accounts and containers to opt-in to RFC-compliant ETags. For more information, see `the documentation <https://docs.openstack.org/swift/latest/middleware.html#module-swift.common.middleware.etag_quoter>`__. Clients should be aware of the fact that ETags may be quoted for RFC compliance; this may become the default behavior in some future release.
en_GB: Added a new middleware to allow accounts and containers to opt-in to RFC-compliant ETags. For more information, see `the documentation <https://docs.openstack.org/swift/latest/middleware.html#module-swift.common.middleware.etag_quoter>`__. Clients should be aware of the fact that ETags may be quoted for RFC compliance; this may become the default behaviour in some future release.

en: Added the ability to configure a chance to skip checking memcache when querying shard ranges. This allows some fraction of traffic to go to disk and refresh memcache before the key ages out. Recommended values for the new ``container_updating_shard_ranges_skip_cache_pct`` and ``container_listing_shard_ranges_skip_cache_pct`` options are in the range of 0.0 to 0.1.
en_GB: Added the ability to configure a chance to skip checking Memcache when querying shard ranges. This allows some fraction of traffic to go to disk and refresh Memcache before the key ages out. Recommended values for the new ``container_updating_shard_ranges_skip_cache_pct`` and ``container_listing_shard_ranges_skip_cache_pct`` options are in the range of 0.0 to 0.1.

en: Added the ability to connect to memcached over TLS. See the ``tls_*`` options in etc/memcache.conf-sample
en_GB: Added the ability to connect to Memcached over TLS. See the ``tls_*`` options in etc/memcache.conf-sample

en: Allow static large object segments to be deleted asynchronously. Operators may opt into this new behavior by enabling the new ``allow_async_delete`` option in the ``[filter:slo]`` section in their proxy-server.conf. For more information, see `the documentation <https://docs.openstack.org/swift/latest/overview_large_objects.html#deleting-a-large-object>`__.
en_GB: Allow static large object segments to be deleted asynchronously. Operators may opt into this new behaviour by enabling the new ``allow_async_delete`` option in the ``[filter:slo]`` section in their proxy-server.conf. For more information, see `the documentation <https://docs.openstack.org/swift/latest/overview_large_objects.html#deleting-a-large-object>`__.

en: COPY now works with unicode account names.
en_GB: COPY now works with Unicode account names.

en: Change the behavior of the EC reconstructor to perform a fragment rebuild to a handoff node when a primary peer responds with 507 to the REPLICATE request. This changes EC to match the existing behavior of replication when drives fail. After a rebalance of EC rings (potentially removing unmounted/failed devices), it's most IO efficient to run in handoffs_only mode to avoid unnecessary rebuilds.
en_GB: Change the behaviour of the EC reconstructor to perform a fragment rebuild to a handoff node when a primary peer responds with 507 to the REPLICATE request. This changes EC to match the existing behaviour of replication when drives fail. After a rebalance of EC rings (potentially removing unmounted/failed devices), it's most IO efficient to run in handoffs_only mode to avoid unnecessary rebuilds.

en: Closed a bug where ssync may have written bad fragment data in some circumstances. A check was added to ensure the correct number of bytes is written for a fragment before finalizing the write. Also, erasure coded fragment metadata will now be validated on read requests and, if bad data is found, the fragment will be quarantined.
en_GB: Closed a bug where ssync may have written bad fragment data in some circumstances. A check was added to ensure the correct number of bytes is written for a fragment before finalising the write. Also, erasure coded fragment metadata will now be validated on read requests and, if bad data is found, the fragment will be quarantined.

en: Closed a bug where ssync may have written bad fragment data in some circumstances. A check was added to ensure the correct number of bytes is written for a fragment before finalizing the write. Also, erasure coded fragment metadata will now be validated when read and, if bad data is found, the fragment will be quarantined.
en_GB: Closed a bug where sync may have written bad fragment data in some circumstances. A check was added to ensure the correct number of bytes is written for a fragment before finalising the write. Also, erasure coded fragment metadata will now be validated when read and, if bad data is found, the fragment will be quarantined.

en: Erasure code reconstruction handles moving data from handoff nodes better. Instead of moving the data to another handoff, it waits until it can be moved to a primary node.
en_GB: Erasure code reconstruction handles moving data from hand-off nodes better. Instead of moving the data to another hand-off, it waits until it can be moved to a primary node.

en: Fix an error in the proxy server when finalizing data.
en_GB: Fix an error in the proxy server when finalising data.

en: Fixed UnicodeDecodeError in the object reconstructor that would prevent objects with non-ascii names from being reconstructed and caused the reconstructor process to hang.
en_GB: Fixed UnicodeDecodeError in the object reconstructor that would prevent objects with non-ASCII names from being reconstructed and caused the reconstructor process to hang.

en: Fixed XML responses (eg on bulk extractions and SLO upload failures) to be more correct. The enclosing "delete" tag was removed where it doesn't make sense and replaced with "extract" or "upload" depending on the context.
en_GB: Fixed XML responses (e.g. on bulk extractions and SLO upload failures) to be more correct. The enclosing "delete" tag was removed where it doesn't make sense and replaced with "extract" or "upload" depending on the context.

en: Fixed encoding issue in ssync where a mix of ascii and non-ascii metadata values would cause an error.
en_GB: Fixed encoding issue in ssync where a mix of ASCII and non-ASCII metadata values would cause an error.

en: Fixed error where a container drive error resulted in double space usage on rest drives. When drive with container or account database is unmounted, the bug would create handoff replicas on all remaining drives, increasing the drive space used and filling the cluster.
en_GB: Fixed error where a container drive error resulted in double space usage on rest drives. When drive with container or account database is unmounted, the bug would create hand-off replicas on all remaining drives, increasing the drive space used and filling the cluster.

en: Fixed issue where bulk requests using xml and expect 100-continue would return a malformed HTTP response.
en_GB: Fixed issue where bulk requests using XML and expect 100-continue would return a malformed HTTP response.

en: Fixed regression in consolidate_hashes that occured when a new file was stored to new suffix to a non-empty partition. This bug was introduced in 2.7.0 and could cause an increase in rsync replication stats during and after upgrade, due to inconsistent hashing of partition suffixes.
en_GB: Fixed regression in consolidate_hashes that occurred when a new file was stored to new suffix to a non-empty partition. This bug was introduced in 2.7.0 and could cause an increase in rsync replication stats during and after upgrade, due to inconsistent hashing of partition suffixes.

en: Improved logging and statsd metrics. Be aware that this will cause an increase in the proxy-logging statsd metrics emited for S3 responses. However, this should more accurately reflect the state of the system.
en_GB: Improved logging and statsd metrics. Be aware that this will cause an increase in the proxy-logging statsd metrics emitted for S3 responses. However, this should more accurately reflect the state of the system.

en: Listing containers in accounts with json or xml now includes a `last_modified` time. This does not change any on-disk data, but simply exposes the value to offer consistency with the object listings on containers.
en_GB: Listing containers in accounts with JSON or XML now includes a `last_modified` time. This does not change any on-disk data, but simply exposes the value to offer consistency with the object listings on containers.

en: Log the correct request type of a subrequest downstream of copy.
en_GB: Log the correct request type of a sub-request downstream of copy.

en: Make mount_check option usable in containerized environments by adding a check for an ".ismount" file at the root directory of a device.
en_GB: Make mount_check option usable in containerised environments by adding a check for an ".ismount" file at the root directory of a device.

en: Move listing formatting out to a new proxy middleware named ``listing_formats``. ``listing_formats`` should be just right of the first proxy-logging middleware, and left of most other middlewares. If it is not already present, it will be automatically inserted for you.
en_GB: Move listing formatting out to a new proxy middleware named ``listing_formats``. ``listing_formats`` should be just right of the first proxy-logging middleware, and left of most other middleware. If it is not already present, it will be automatically inserted for you.

en: Moved other-requirements.txt to bindep.txt. bindep.txt lists non-python dependencies of Swift.
en_GB: Moved other-requirements.txt to bindep.txt. bindep.txt lists non-Python dependencies of Swift.

en: Now Swift will use ``write_affinity_handoff_delete_count`` to define how many local handoff nodes should swift send request to get more candidates for the final response. The default value "auto" means Swift will calculate the number automatically based on the number of replicas and current cluster topology.
en_GB: Now Swift will use ``write_affinity_handoff_delete_count`` to define how many local hand-off nodes should swift send request to get more candidates for the final response. The default value "auto" means Swift will calculate the number automatically based on the number of replicas and current cluster topology.

en: On Python 3, the formpost middleware now works with unicode file names.
en_GB: On Python 3, the formpost middleware now works with Unicode file names.

en: On newer kernels (3.15+ when using xfs), Swift will use the O_TMPFILE flag when opening a file instead of creating a temporary file and renaming it on commit. This makes the data path simpler and allows the filesystem to more efficiently optimize the files on disk, resulting in better performance.
en_GB: On newer kernels (3.15+ when using xfs), Swift will use the O_TMPFILE flag when opening a file instead of creating a temporary file and renaming it on commit. This makes the data path simpler and allows the filesystem to more efficiently optimise the files on disk, resulting in better performance.

en: Optimize the Erasure Code reconstructor protocol to reduce IO load on servers.
en_GB: Optimise the Erasure Code reconstructor protocol to reduce I/O load on servers.

en: Optimized the common case for hashing filesystem trees, thus eliminating a lot of extraneous disk I/O.
en_GB: Optimised the common case for hashing filesystem trees, thus eliminating a lot of extraneous disk I/O.

en: PUT subrequests generated from a client-side COPY will now properly log the SSC (server-side copy) Swift source field. See https://docs.openstack.org/developer/swift/logs.html#swift-source for more information.
en_GB: PUT sub-requests generated from a client-side COPY will now properly log the SSC (server-side copy) Swift source field. See https://docs.openstack.org/developer/swift/logs.html#swift-source for more information.

en: Remove empty db hash and suffix directories if a db gets quarantined.
en_GB: Remove empty DB hash and suffix directories if a DB gets quarantined.

en: Ring files now include byteorder information about the endian of the machine used to generate the file, and the values are appropriately byteswapped if deserialized on a machine with a different endianness. Newly created ring files will be byteorder agnostic, but previously generated ring files will still fail on different endian architectures. Regenerating older ring files will cause them to become byteorder agnostic. The regeneration of the ring files will not cause any new data movement. Newer ring files will still be usable by older versions of Swift (on machines with the same endianness--this maintains existing behavior).
en_GB: Ring files now include byteorder information about the endian of the machine used to generate the file, and the values are appropriately byteswapped if deserialised on a machine with a different endianness. Newly created ring files will be byteorder agnostic, but previously generated ring files will still fail on different endian architectures. Regenerating older ring files will cause them to become byteorder agnostic. The regeneration of the ring files will not cause any new data movement. Newer ring files will still be usable by older versions of Swift (on machines with the same endianness--this maintains existing behaviour).

en: Rings with min_part_hours set to zero will now only move one partition replica per rebalance, thus matching behavior when min_part_hours is greater than zero.
en_GB: Rings with min_part_hours set to zero will now only move one partition replica per rebalance, thus matching behaviour when min_part_hours is greater than zero.

en: SLO manifest PUT requests can now be properly validated by sending an ETag header of the md5 sum of the concatenated md5 sums of the referenced segments.
en_GB: SLO manifest PUT requests can now be properly validated by sending an ETag header of the MD5 sum of the concatenated MD5 sums of the referenced segments.

en: Server-side copying of erasure-coded data to a replicated policy no longer copies EC sysmeta. The previous behavior had no material effect, but could confuse operators examining data on disk.
en_GB: Server-side copying of erasure-coded data to a replicated policy no longer copies EC sysmeta. The previous behaviour had no material effect but could confuse operators examining data on disk.

en: Some client behaviors that the proxy previously logged at warning have been lowered to info.
en_GB: Some client behaviours that the proxy previously logged at warning have been lowered to info.

en: Static large object segments may now be deleted asynchronously by default. Operators may return to the old behavior by disabling the ``allow_async_delete`` option in the ``[filter:slo]`` section in their proxy-server.conf.
en_GB: Static large object segments may now be deleted asynchronously by default. Operators may return to the old behaviour by disabling the ``allow_async_delete`` option in the ``[filter:slo]`` section in their proxy-server.conf.

en: The ``kmip_keymaster`` middleware can now be configured directly in the proxy-server config file. The existing behavior of using an external config file is still supported.
en_GB: The ``kmip_keymaster`` middleware can now be configured directly in the proxy-server config file. The existing behaviour of using an external config file is still supported.

en: The ``storage_domain`` option now accepts a comma-separated list of storage domains. This allows multiple storage domains to configured for use with virtual-host style addressing.
en_GB: The ``storage_domain`` option now accepts a comma-separated list of storage domains. This allows multiple storage domains to be configured for use with virtual-host style addressing.

en: The container-updater now reports zero objects and bytes used for child DBs in sharded containers. This prevents double-counting in utilization reports.
en_GB: The container-updater now reports zero objects and bytes used for child DBs in sharded containers. This prevents double-counting in utilisation reports.

en: The erasure code reconstructor `handoffs_first` option has been deprecated in favor of `handoffs_only`. `handoffs_only` is far more useful, and just like `handoffs_first` mode in the replicator, it gives the operator the option of forcing the consistency engine to focus solely on revert (handoff) jobs, thus improving the speed of rebalances.  The `handoffs_only` behavior is somewhat consistent with the replicator's `handoffs_first` option (any error on any handoff in the replicator will make it essentially handoff only forever) but the `handoff_only` option does what you want and is named correctly in the reconstructor.
en_GB: The erasure code reconstructor `handoffs_first` option has been deprecated in favour of `handoffs_only`. `handoffs_only` is far more useful, and just like `handoffs_first` mode in the replicator, it gives the operator the option of forcing the consistency engine to focus solely on revert (handoff) jobs, thus improving the speed of rebalances.  The `handoffs_only` behaviour is somewhat consistent with the replicator's `handoffs_first` option (any error on any hand-off in the replicator will make it essentially hand-off only forever) but the `handoff_only` option does what you want and is named correctly in the reconstructor.

en: The formpost middleware now works with unicode file names.
en_GB: The formpost middleware now works with Unicode file names.

en: The object and container server config option ``slowdown`` has been deprecated in favor of the new ``objects_per_second`` and ``containers_per_second`` options.
en_GB: The object and container server config option ``slowdown`` has been deprecated in favour of the new ``objects_per_second`` and ``containers_per_second`` options.

en: The proxy-server now caches 'listing' shards, improving listing performance for sharded containers. A new config option, ``recheck_listing_shard_ranges``, controls the cache time and defaults to 10 minutes; set it to 0 to disable caching (the previous behavior).
en_GB: The proxy-server now caches 'listing' shards, improving listing performance for sharded containers. A new config option, ``recheck_listing_shard_ranges``, controls the cache time and defaults to 10 minutes; set it to 0 to disable caching (the previous behaviour).

en: The relinker now performs eventlet-hub selection the same way as other daemons. In particular, ``epolls`` will no longer be selected, as it seemed to cause occassional hangs.
en_GB: The relinker now performs eventlet-hub selection the same way as other daemons. In particular, ``epolls`` will no longer be selected, as it seemed to cause occasional hangs.

en: The relinker now spawns multiple subprocesses to process disks in parallel. By default, one worker is spawned per disk; use the new ``--workers`` option to control how many subprocesses are used. Use ``--workers=0`` to maintain the previous behavior.
en_GB: The relinker now spawns multiple subprocesses to process disks in parallel. By default, one worker is spawned per disk; use the new ``--workers`` option to control how many subprocesses are used. Use ``--workers=0`` to maintain the previous behaviour.

en: Updated the `hashes.pkl` file format to include timestamp information for race detection. Also simplified hashing logic to prevent race conditions and optimize for the common case.
en_GB: Updated the `hashes.pkl` file format to include timestamp information for race detection. Also simplified hashing logic to prevent race conditions and optimise for the common case.

en: User metadata is now exposed via CORS when encryption is enabled, matching the behavior when encryption is not enabled.
en_GB: User metadata is now exposed via CORS when encryption is enabled, matching the behaviour when encryption is not enabled.

en: When building a listing from shards, any failure to retrieve listings will result in a 503 response. Previously, failures fetching a partiucular shard would result in a gap in listings.
en_GB: When building a listing from shards, any failure to retrieve listings will result in a 503 response. Previously, failures fetching a particular shard would result in a gap in listings.

en: When requesting objects, return 404 if a tombstone is found and is newer than any data found. Previous behavior was to return stale data.
en_GB: When requesting objects, return 404 if a tombstone is found and is newer than any data found. Previous behaviour was to return stale data.

en: ``LastModified`` timestamps in listings are now rounded up to whole seconds, like they are in responses from AWS.
en_GB: ``LastModified`` timestamps in listings are now rounded up to whole seconds like they are in responses from AWS.

en: s3api now mimics some forms of AWS server-side encryption based on whether Swift's at-rest encryption functionality is enabled. Note that S3 API users are now able to know more about how the cluster is configured than they were previously, ie knowledge of encryption at-rest functionality being enabled or not.
en_GB: s3api now mimics some forms of AWS server-side encryption based on whether Swift's at-rest encryption functionality is enabled. Note that S3 API users are now able to know more about how the cluster is configured than they were previously, i.e. knowledge of encryption at-rest functionality being enabled or not.

en: s3api now mimics the AWS S3 behavior of periodically sending whitespace characters on a Complete Multipart Upload request to keep the connection from timing out. Note that since a request could fail after the initial 200 OK response has been sent, it is important to check the response body to determine if the request succeeded.
en_GB: s3api now mimics the AWS S3 behaviour of periodically sending whitespace characters on a Complete Multipart Upload request to keep the connection from timing out. Note that since a request could fail after the initial 200 OK response has been sent, it is important to check the response body to determine if the request succeeded.

en: tempauth user names now support unicode characters.
en_GB: tempauth user names now support Unicode characters.
