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

Change-Id: If284513ead5ff0d7f9e997ebf2a8820c9acf79e3

S3 supports two metadata operations on object copy: COPY and REPLACE.
When using REPLACE, the Content-Type should be set to the one supplied
by the caller. When using COPY, the existing object's Content-Type value
is used.
Change-Id: Ic7c6278dedef308c9219eb45751abfa5655f144f
Closes-Bug: #1828907 

Related-Change: I3603247e0c36299de2107aa8e494a3f87647696f
Change-Id: Iaf14c1ab3e236e6774492ed711fccef066a16fca

This finishes the proxy unit tests.
Change-Id: I2452e4e4dabef071bfbf376d03ec63211f7c2906

Change-Id: I8287db75b4f19581203360c646e72f64fe45f170

All except the versioned_writes tests, which are hairy.
Change-Id: Ieb54869f93a70c8887d33bd2ad46cf04a190d896

Removed trailing newline
Change-Id: I8b100b8213d6efde67b0452ce988bc47c830a2e2

Added Dockerfile and configuration files under the
new `docker` directory to build a Swift All in One container
image.
The primary goal of this container image is to provide
application developers with a Swift/S3 endpoint that can be
tested against during the development cycle.
Added Zuul jobs to build docker container
Change-Id: Ib10975a1862a4fa8c4eeaba139837cf1f22b272a

This patch removes default value for logger passed to
faked BrokerClass in some unit tests for account reaper,
to make sure that a logger instance is properly passed
when generation BrokerClass instance.
This patch also removes unnecessory parameter, which is
added to confirm logger passed to broker, but is not
useful in fact.
NOTE: This patch is a follow-up of my previous commit[1]
[1] https://review.opendev.org/#/c/295875/
Change-Id: Ica10e3ac42375c2dc141478e647408df90028ae9

This is to remove the unncessary slash when the line doesn't
exceed the length of 79, to make the code more readable.
Change-Id: I31070067913560d6147f95d0fdfba4f9f9ce0936

Change-Id: I378705a8d9ad51dbfa85287d44e6313aa7680c23

Change-Id: I2e233afff26878ba94e268c71f6779bcca7b641c

Mostly this ammounts to
 Exception.message -> Exception.args[0]
 '...' -> b'...'
 StringIO -> BytesIO
 makefile() -> makefile('rwb')
 iter.next() -> next(iter)
 bytes[n] -> bytes[n:n + 1]
 integer division
Note that the versioning tests are mostly untouched; they seemed to get
a little hairy.
Change-Id: I167b5375e7ed39d4abecf0653f84834ea7dac635

Change-Id: Iae9aa7a91b9afc19cb8613b5bc31de463b853dde

We've seen a noteworthy (literally -- there's a comment about it) number
of failures for test_multiphase_put_drains_extra_commit_junk_disconnect;
I'd rather waste an extra few hundredths of a second every run than have
to recheck most patches we want merged.
Co-Authored-By: Clay Gerrard <clay.gerrard@gmail.com>
Change-Id: Iebec6c18866e4f8ef40faab539b173f017d658e3

To prepare for object-expirer's general task queue feature [1],
this patch enables to configure object-expirer in object-server.conf.
Object-expirer.conf can be used in the same manner as before, but deprecated.
If both of object-server.conf with "object-expirer" section and
object-expirer.conf are in a node, only object-server.conf is used.
Object-expirer.conf is used only if all object-server.conf doesn't have
"object-expirer" section.
There are two differences between "object-expirer.conf" style and
"object-server.conf" style.
The first difference is `dequeue_from_legacy` default value.
`dequeue_from_legacy` defines task queue mode. In "object-expirer.conf"
style, the default mode is legacy queue. In "object-server.conf" style,
the default mode is general queue. But general mode means no-op mode
for now, because general task queue is not implemented yet.
The second difference is internal client config. In "object-expirer.conf"
style, config file of internal client is the object-expirer.conf itself.
In "object-server.conf" style, config file of internal client is
another file.
[1]: https://review.openstack.org/#/c/517389/
Co-Authored-By: Matthew Oliver <matt@oliver.net.au>
Change-Id: Ib21568f9b9d8547da87a99d65ae73a550e9c3230

More-recent versions of stestr are rather picky about wanting an integer
for concurrency [1], but ostestr prior to [2] defaults it to None. As a
result, all our func tests would fail with:
 TypeError: int() argument must be a string or a number, not 'NoneType'
Also, move the rolling upgrade job to non-voting since it's going to
pull in the old version but try to run with new deps.
[1] https://github.com/mtreinish/stestr/commit/c93bc81
[2] https://review.openstack.org/#/c/651275/
Change-Id: Icba6c46bcff0e0516107e0f6742d32c92488ae20

Change-Id: I789fb2413985942460d3275b479d6410c62c380f

Retain support for the old way, though (at least for now).
Change-Id: Id3c2ed87230c5918c18e2c01d086df8157f036b1

Change-Id: Iadb3bed811907740f85bd9277ba09a4ca17fc025

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

Drive-by: When passing a list or tuple to swob.Response as an app_iter,
check that it's full of byte strings.
Change-Id: Ifc35aacb2e45004f74c871f08ff3c52bc57c1463

Note that this only affects the functest client.
See also: https://bugs.python.org/issue36274
Change-Id: I1359c475fbe93db2f0fcc4b450be6dd5073f922e

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