Tim Burke 6a8675e897 Use SLO by default for segmented uploads if the cluster supports it
We've had SLO for nearly ten years, and it is preferable for most
use-cases. It's time to default to SLO rather than DLO.

Add a new --use-dlo option to give users a way to return to old
behavior; ensure there is still a --use-slo option so we don't break
existing scripts that may use it.

UpgradeImpact:
==============
The default segmented-upload behavior has changed; Static Large Objects
are now used by default rather than Dynamic Large Objects. To revert to
the old behavior:

* CLI users may use the new `--use-dlo` option
* Service API users may explicitly set `use_slo` to False in their
  options dicts

Change-Id: Iebcd64ced8eab6efebb9f02a0c4be6bf6338cb3b
2023-03-21 12:46:44 -07:00
2014-03-25 11:36:39 +00:00
2022-03-21 18:29:25 +00:00
2022-01-12 10:19:50 +01:00
2018-07-13 11:24:24 -07:00
2018-11-05 09:52:03 +07:00
2019-04-19 19:32:30 +00:00
2019-03-01 08:32:50 -08:00
2018-01-30 00:28:17 +00:00
2012-05-08 16:30:13 +01:00
2013-05-01 12:23:12 -04:00
2022-03-21 18:31:10 +00:00
2022-03-16 15:06:19 -07:00
2023-03-17 16:47:34 -07:00
2022-03-16 15:06:19 -07:00
2023-01-05 16:58:36 -08:00

Team and repository tags

image

Python bindings to the OpenStack Object Storage API

Latest Version

This is a python client for the Swift API. There's a Python API (the swiftclient module), and a command-line script (swift).

Development takes place via the usual OpenStack processes as outlined in the OpenStack wiki.

This code is based on the original client previously included with OpenStack's Swift. The python-swiftclient is licensed under the Apache License like the rest of OpenStack.

Contents:

Description
OpenStack Storage (Swift) Client
Readme 14 MiB
Languages
Python 99.9%
Shell 0.1%