openstack/swift - swift - OpenDev: Free Software Needs Free Tools

This patch removes an additional 'and' added to a sentence.
Change-Id: I6ab47637ef2d2f97f35188a84e741274c2b504e8

At some point, we should probably plumb in a ca_cert option or something.
Change-Id: I3b719be3e2ae5620ad84bd275516f6c8843ceaa4

Change-Id: Ife00798a450828c7b640142def8929a38e23d5ad
Related-Change: Icb88902f0a89b8d980c860be032d5e822845d03a

replace a OpenStack bucket with an OpenStack bucket
Change-Id: I4ada68720dcf23fb9b94c922ddb3eefd42aa80a7

replace a object with an object
Change-Id: Ied9cd7c7d0efaf455370e184abd31734574bff07

Previously some tests in /test/functional/test_staticweb.py assumed
that domain_remap middleware was configured with the default
storage_domain 'example.com'. As a result those tests would fail if
run against a cluster with domain_remap middleware installed but not
having an 'example.com' storage_domain.
This patch allows a storage_domain to be configured in the test.conf
file so that the tests may be successfully run against any cluster. If
the option is not set then the tests will be skipped.
To ensure that the in process test job func-domain-remap-staticweb
still runs all the tests in test_staticweb.py, its config loader is
modified to add the required storage_domain option to the test config
with the same value used by the domain_remap middleware.
Related-Change: I6bc70039c1b99b8a5bf5a30e9c6877d4f0aa638d
Co-Authored-By: Tim Burke <tim.burke@gmail.com>
Change-Id: Ifab84fc3ef66b9790e96ebb8e5c8061a12636045

Change-Id: Ib7b208669e900b84a7759819ef76b7b5b7ce8c9a
Closes-Bug: 1774719

Pulled the FS walking out into its own function so that finding
async_pendings is in one place and processing them is in another. This
should make it easier to add greenthread-based concurrency later.
Also refactored rate limiting to use utils.RateLimitedIterator instead
of calling ratelimit_sleep ourselves. The functionality's the same,
but the interface is easier.
Change-Id: I02f9e3201e9434080c6fb87ac5e249d8b327a231

When running in multiprocess mode, the object reconstructor would
periodically aggregate its workers' recon data into a single recon
measurement. However, at the end of the run, all that was left in
recon was the last periodic measurement; any work that took place
after that point was not recored in the aggregate. However, it was
recorded in the per-disk stats that the worker processes emitted.
This commit adds a final recon aggregation after the worker processes
have finished.
Change-Id: Ia6a3a931e9e7a23824765b2ab111a5492e509be8

Related-Change: I12eb55a42e5a8dc2dff5a4687f7fe31452f9508e
Change-Id: I0a7479e56b91a8e69bffd9c7df1c26b839ab13a2

The first item in groups is the account, the second item is the account_user.
The second one is *way* more useful for debugging.
Change-Id: I12eb55a42e5a8dc2dff5a4687f7fe31452f9508e

Change-Id: I791b03a7cabd63bf363e17f7ac603744d8dbf130

Add test assertions to verify that the related change fixes usync diff
stats being erroneously incremented as a side-effect of syncing shard
ranges when the object tables are in sync.
Related-Change: I2630bb127841837b35e7786b59895fa50090719b
Change-Id: Idffe93c63d16e74ea9ca42b33a636c0c0d9e35b5

The container server GET method became more complex with the
introduction of shard ranges [1]. This patch adds some commentary to
the docstring. The additional docstring is not intended to be
exhaustive, particularly where it would duplicate the API docs.
[1] Related-Change: I029782ae348f38c5fb76d2759609f67a06c883ef
Change-Id: Id661f5dd67768e1698901ca06e33900291e80964

Make the descriptions generic since they are used in both account and
container API specs.
Change-Id: Id3f8d87da00e6c57a3f4a41471ac64ada71f49ee

Change-Id: Id9dbf27e93bd9a4a38a1547953be0af0bf0c19c2

The object updater emits a log line saying "Object update sweep
completed on <disk> in <time>: <lots-of-stats>" after finishing each
storage policy's async pendings. That's not right; an update sweep is
completed on a device when you've looked at all the async pendings on
the device.
This commit moves the "sweep completed" message so it's once per
device, not per policy.
Change-Id: Ibb5f02a18ac431da230afe30c556a756f60d1680

See https://review.openstack.org/#/c/571007/ and
https://review.openstack.org/#/c/570999/ for context.
Change-Id: Ib6045de3cb9097ed7e6d48646109f35612cbbc74

This patch adds a read_only middleware to swift. It gives the ability
to make an entire cluster or individual accounts read only.
When a cluster or an account is in read only mode, requests that would
result in writes to the cluser are not allowed.
DocImpact
Change-Id: I7e0743aecd60b171bbcefcc8b6e1f3fd4cef2478

Lock timeouts happen, especially on very busy containers. It's not
worth a stack trace, and it's not an error. Now we still log the
lock timeout, but at INFO level and without a stack trace.
Change-Id: Ia202c876fb726f9ae6040d875a83105dd975539b

We probably don't need an extra INFO-level message every time a user
makes a PUT request with X-Copy-From set. It's still in the proxy's
access logs.
Change-Id: I32ce8ff16cb296dd5acef07202a59bc5125111c1