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

Change-Id: I5b0ae0b78d37a31928e0b34a1b6118802a3a8236

Change-Id: I175b9e1464494454b1193b9b9d5311cb6fd6503f

Following https://github.com/openstack/devstack/commit/6b6bdc711,
the swift-dsvm-functional job has been running everything under
Python 3 anyway.
Change-Id: Ie285f513e1ed71dbaf4e12fe747ea6087664f843

For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html
Change-Id: I1bb2aa262730d45a5852eaa3b3351f455a6ab337

Change-Id: Iec399aa8b58e72152a17265f2af1131f02667131

...instead of hacking up the pipeline ourselves.
Depends-On: https://review.opendev.org/731003
Depends-On: https://review.opendev.org/731065
Change-Id: Iea8a42ef54e1a2fd9c1d6132c840a20015cc5d7e

Change-Id: Ib78398111ee3d150b6f56aa4e59a65750aa115dd

This patch standardizes the CONTRIBUTING.rst file and adds the
required doc/source/contributor/contributing.rst
Swift already had a detailed CONTIRBUTING.rst and an informative
REVIEW_GUIDELINES.rst in the root of the repo. So we are also pulling
them into the contributor documentation so they can not only be easily
found in the checked repo but in the online documentation.
Change-Id: I4c84efbe50eb25ab922c9d6b69198dae341af48b

Change-Id: I0bdd3a1d044f8f99873f6270ca821862bb994d72

Change-Id: Idcc33c71869ccf7ad5a3134767d36ae94aab4598

Previously, the lack of container ACLs on the reserved container would
mean that attempting to grant access to the user-visible container would
not work; the user could not access the backing object.
Now, have symlinks with the allow-reserved-names sysmeta set be
pre-authed. Note that the user still has to be authorized to read the
symlink, and if the backing object was *itself* a symlink, that will be
authed separately.
Change-Id: Ifd744044421ef2ca917ce9502b155a6514ce8ecf
Closes-Bug: #1880013 

Regular objects can do conditional requests, versioned objects should be
able to as well.
Change-Id: If69dbf2a4c876fa4b830f6d8652f22f39ceaf549

Depends-On: https://review.opendev.org/#/c/571021/
Change-Id: I3ac3288cd61b745ce7dbf2bded8eade026d0418f

We want to do the table scan without locking and group the locking
deletes into small indexed operations to minimize the impact of
background processes calling reclaim each cycle.
Change-Id: I3ccd145c14a9b68ff8a9da61f79034549c9bc127
Co-Authored-By: Tim Burke <tim.burke@gmail.com>
Closes-Bug: #1877651 

Change-Id: Icd5312dec647f69a5df111c3a6766093ecfcb6ef

DSVM recently got a bunch more middlewares enabled, so it's running more
tests than it used to.
I can't think of much that's changed for probe tests, but I feel like
I've seen it popping timeouts more often lately.
Note that the new timeouts are still lower than the typical run-time of
our longest-running jobs (currently grenade / tempest-ipv6-only).
Change-Id: Iffbb567124096df02b04981550faec8204d5d1ec
Related-Change: I3cbbcd2ea9ced0923bee4a6b0783e4cf5e82e95b

We usually want to have ratelimit fairly far left in the pipeline -- the
assumption is that something like an auth check will be fairly expensive
and we should try to shield the auth system so it doesn't melt under the
load of a misbehaved swift client.
But with S3 requests, we can't know the account/container that a request
is destined for until *after* auth. Fortunately, we've already got some
code to make s3api play well with ratelimit.
So, let's have our cake and eat it, too: allow operators to place
ratelimit once, before auth, for swift requests and again, after auth,
for s3api. They'll both use the same memcached keys (so users can't
switch APIs to effectively double their limit), but still only have each
S3 request counted against the limit once.
Change-Id: If003bb43f39427fe47a0f5a01dbcc19e1b3b67ef

Connection was hard coded to use saio config
Change-Id: I9c11162de89fa3aa2a78aea093b187d0309860f5
Signed-off-by: Thiago da Silva <thiago@redhat.com>

Change-Id: If274a01a6660776cf01b71efbdd102159c520794

Sometimes even one database per second is too fast.
Change-Id: Iaf11743485e1ad320c82476430f450be0c4f849c
Closes-Bug: #1877827 

New flake8 came out with new & improved rules. Ignore E741; it would be
too much churn. Fix the rest.
Change-Id: I9125c8c53423232309a75cbcc5b695b378864c1b

When tuning your updater, you often want to try a new config, see how it
changes your metrics, then adjust concurrency up or down depending on
how your container layer is responding.
If your containers haven't been doing well, though, and you've got a
giant backlog of async pendings to work through, updater restarts to
change concurrency previously posed a problem: the updater would walk
the suffix directories in the same order every start-up. So, if you
found a config that was making decent progress for a while but still had
*some* failures, and you wanted to try tweaking settings to see if you
could *reduce* those failures -- you'd likely start getting *all*
failures as it went to retry the failed ones first and all at once. If
you continued trying to tweak configs to get your failures to a
reasonable rate, you'd almost certainly over-correct for these handful 
of overwhelmed DBs and not the overall cluster.
Now, shuffle the suffixes before we walk them.
Change-Id: I3ef34119f0cb563ab405a6517335a24dbaf2b4c3
Closes-Bug: #1878056 

Change-Id: Iaac1fb891d70707af38c567d9cca5913b8355b7d
Closes-Bug: #1877924 

Previously, we'd see warnings like
 UnicodeWarning: Unicode equal comparison failed to convert both
 arguments to Unicode - interpreting them as being unequal
when setting lower/upper bounds with non-ascii byte strings.
Change-Id: I328f297a5403d7e59db95bc726428a3f92df88e1

* Add a new config option, proxy_base_url
* Support HTTPS as well as HTTP connections
* Monkey-patch eventlet early so we never import an unpatched version
 from swiftclient
Change-Id: I4945d512966d3666f2738058f15a916c65ad4a6b

The global upper constraints repo will no longer track py2 packages,
meaning upper constraints for the py2.7 runtime will need to be handled
locally.
This adds an in-repo file for upper constraints enforcement using the
last py27 constraints from openstack/requirements to validate
functionality.
Change-Id: I624f914c6155178cbe474f1eae2871e2aef721eb
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>

The integrated gate templates has switched to the new grenade name
(grenade-py3 -> grenade). This repo uses an integrated gate template
but also listed the job for irrelevant files an extra entry.
Rename the job following the template change to avoid duplicate
grenade runs.
Details:
- http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014602.html
Change-Id: I4afc73301965b582fd338012f0ddc60f9b85fbb0

* Stop specifying logbufs=8; that's the default
* Stop including nodiratime with noatime; the latter implies the former
Nothing wrong with being explicit, I suppose, but may as well keep the
mount options to what we can easily explain: we want noatime because
Swift does not use atime, so we don't want to lose any performance to
tracking atime.
Change-Id: I1e52b4368ad7eb375964eee5132bc50297536355