Here is an initial version of the next sharding POC, it is based off
discussions at the hackathon in Austin and the Tokyo design summit,
plus some initial work I have already put together to see how it would
work.
This approach is similar, but simpler then in the last distributed
prefix tree POC. It will simply split the table at a pivot point,
creating two new containers that hold all the objects. The root
container holds a reference to all the new containers and their range,
so it can short circuit requests as it knows all data will be in the tree's
leaves.
Change-Id: I21766423a07a5b6195656b06db4e590598bf3d41
When a development environment is under a proxy, tox is failed even if
environment variables of the proxy are set.
This patch fixes this problem.
Related-bug #1465086
Change-Id: Ia58b02521fa068db123e888d921a61dac4f1743e
Adding/enhancing Swift-Inspector middleware for OpenStack Swift to
tag a particular request/every 'x' requests which would undergo
more detailed logging.
A Swift user is having problems which we cannot recreate but tag this
request for more logging. Also an internal user(admin/op) could use
additional logs to investigate a cluster for bottlenecks/problems.
Change-Id: Ib42f7218d51b77d7976b50245b23b794cd93422a
The tempurl middleware should be allowed to use signatures with a
prefix-based scope in order to access all objects which share the same prefix.
This avoids the creation of a large amount of temporary urls, when
a whole container or pseudofolder is shared.
Change-Id: Ibb5e7118933ceff02c4325734ab29917239602a5
This is the proposal to give swift users power to change storage policies
of containers after creating them.
Implements: blueprint changing-policies
Change-Id: Ia4b3f8471e9b8347439dc2f6c41df15c5d84db8d
formpost currently requires that the signature used to validate a file
upload contains the same object_prefix as the object_prefix specified
in the action url of the form.
We propose that the middleware should also accept signatures calculated
with a subprefix of the object_prefix in the action url. Thus, formpost
would accept all uploads to pseudofolders which contain a common
subprefix.
With this, sharing of data with external people is made much easier via
webbased applications, because only one signature is needed in order to
create forms for every pseudofolder in a container.
Change-Id: I4237f141022382131977ff16760f5645d0391ea5
This spec describes the idea behing patch:
https://review.openstack.org/#/c/159285/
Change-Id: I95afabc3587fb4701e08ebec9f646727ae18a46d
Signed-off-by: Thiago da Silva <thiago@redhat.com>
This change adds a new section, Spec Lifecycle Rules, to the README.
I am raising them here for discussion and are based on spec
discussions at summit.
If anyone can think of better working, section name or some more
rules please leave comments.
Change-Id: I5dda349f9e3ce2a49d400eefa275301d5f2d693d
This patch updates the spec with changes discussed at the
San Francisco hackathon, Feb 2015:
* User metadata names will not be encrypted.
* Detail on storing crypto related metadata for each
resource.
* Encrypted etags will be sent at end of MIME multipart body.
* Keymaster may set a request environ variable to indicate that
encryption or decryption is not to be applied to a particular
request.
Co-Authored-By: Janie Richling <jrichli@us.ibm.com>
Change-Id: I2b7a77e6161650aaf2219e7ca92068e19831da9a
Tim Burke