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

Change-Id: I789fb2413985942460d3275b479d6410c62c380f

Add the log_msg_template option in proxy-server.conf and log_format in
a/c/o-server.conf. It is a string parsable by Python's format()
function. Some fields containing user data might be anonymized by using
log_anonymization_method and log_anonymization_salt.
Change-Id: I29e30ef45fe3f8a026e7897127ffae08a6a80cd9

There's a bug in CPython [1] that causes servers to mis-parse request
lines that include the bytes \x85 or \xa0. Naturally, we have
functional tests that (with high probability) will send such request
lines. There's a fix proposed, but the earliest it's likely to land
would be for 3.8, and we need to be able to target an earlier Python.
So, intercept the request line immediately before parsing and re-write
it to be RFC-compliant. Note that this is done for Python 2 as well,
though there should be no change in the request environment that
eventlet eventually hands to us.
[1] https://bugs.python.org/issue33973
Change-Id: Ie648f5c04d4415f3b620fb196fa567ce7575d522

There are some processes which don't pass their logger instances
when creating AccountBrokers/ContainerBrokers, which causes some
error messages with a different setting from the other logs
generated by the processes.
This patch makes them pass logger instances, to make sure they
generate all logs according to their log settings.
Change-Id: I914c3a2811e1a2b7f19ad2bc9b3d042fcba63820

Add a test assertion for invalid ETag of MPU manifest and make some
global constants more obvious.
Change-Id: I830c0d2e473d1740f9138ebc6efd64a39d85d1dc
Related-Change-Id: I7df13e670f702a2956a9c8057fcb971f4bfb7319

Change-Id: I7df13e670f702a2956a9c8057fcb971f4bfb7319
Closes-Bug: 1810397

Thorough replacement of git.openstack.org URLs with their opendev.org
counterparts.
Change-Id: I5e77307de6a484fd69b2a5863423ceb357e8601f

This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html
Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.

We don't actually need so many py2/py3 branches, and once we
clean those up, there's hardly any reason to import six.
Change-Id: Ia3b4f02e7eb99ad1a76aa35c39dc198528fd39ad

Change-Id: I7236ddea0acde93d0789ad8affa76df0097a86aa

Looking at https://governance.openstack.org/tc/reference/runtimes/train.html
OpenStack is no longer targetting Python 3.5, so it doesn't really make sense
to gate on it. Move to Python 3.7, just to make it so we can go longer before
having to do this shuffle again.
Presumably, once we actually declare support for Python 3.6, we should
make that job voting, too? We've had enough gate flaky-ness lately that
I'm not keen on it.
Change-Id: I9c9e5df76a6592ab9c512b7c1ba807f9a0053059

This is to use assertIn to check whether substring is in str,
go get clearer failure message.
Change-Id: I40aff29454c423389755a5330751d2f69a227a05

Also, enhance tests to verify proper encoding in generated responses.
Change-Id: Ib696b1c3a34722f3a6de010973b90ef8b1917012
Partial-Bug: 1774238

It has not been necessary since we dropped support for Python 2.6.
See https://github.com/python/cpython/commit/8c6d9d7 and
https://bugs.python.org/issue2987.
Be sure to keep a `urlparse` name in utils, though; swauth (at least)
still expects there to be a swift.common.utils.urlparse.
Change-Id: If2502868f251b8a83aa929ee22b10046e708d111

An earlier revision of the related change had a bug that this test would
have discovered.
Related-Change-Id: I85dcaf65b9f19ac4659fa5937f9b0b0e804fc54e
Change-Id: Iedd85ec65a11de189ce73e650d674aee0dc7e402

This patch is porting the staticweb middleware to py3.
Change-Id: I5d9a13baecedd13d2b7a8ae3dd639eaff0894441

Update to rocky release
Change-Id: Id35a41d689a24bf68d17647879780f5daaecdf37

Object-replicator let user to input target partition numbers and
run the replicator job, and partition input will be stored as
integer list. But in build_replication_jobs method, it use
os.listdir method to retreve partitions in string list, so it is
failed to compare with target partition numbers.
Change-Id: I85dcaf65b9f19ac4659fa5937f9b0b0e804fc54e
Closes-Bug: #1822731 

Also, ensure that the stored symlink headers really *are* url-encoded as
we've been assuming.
Change-Id: I1f300d69bec43f0deb430294da05a4ec04308040
Related-Bug: 1774238
Closes-Bug: #1821240 

It was a recommended practice for years to get away from straight
names in /dev, like /dev/sda1, when mounting filesystems. The
man page for mount(8) says:
 The device name of disk partitions are unstable; hardware
 reconfiguration, adding or removing a device can cause change
 in names. This is reason why it's strongly recommended to use
 filesystem or partition identificators like UUID or LABEL.
Nonetheless, novice operators sometimes follow our deployment
guide to the letter and then get into trouble when device names
shift from under their deployments. This patch fixes the problem
without bloating up the guide with general explanations.
Change-Id: I5faae158b62e0395d6e774cd67bd868c785c2186

Change-Id: Ibbff151703395d517452c3d6927652506a9eab66

Apparently some versions of py3 will drop symlinks in the venv.
Change-Id: I77c52b6ad776ab75c4f9713290cc42a1fcb6e0f7

Change-Id: I89d19c299cf67c459ee893cde7ed6f6716c04f9b

Change-Id: Ib853f79bc062ec550627342d0fc5b2b92029f25c

...and fix this one warning-treated-as-error that crept in since
https://github.com/openstack/swift/commit/d185b60
Change-Id: Id46ee3ab23e2703170191528427aaa2788aba1ee

Drive-by: run api-ref tox env under py3.
Change-Id: Iebce47eabcb3b198d4aa7c1b8cfaf8f53300f7f9