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

Add a note to the docstring that it is required to add a config section
to the proxy-server.conf and an entry to the pipeline to support history
mode.
Closes-Bug: 1619261
Change-Id: I888485ab4ece6f47db081a4d58c1aab24ce72a8a

Based on comments from patch #238799.
Change-Id: I9455cf6dc7fd12fee62439ff3c5f3255287ab1be

This comes from discussion in Bristol Hackathon (Feb 2016).
Currently Swift has a couple of choices (Global Cluster and Container
Sync) to sync the stored data into geographically distributed locations.
This patch adds the summary of the discussion comparing between
Global Cluster and Container Sync to enable operators to know which
functionality fits their own use case.
And, to be fairness with container-sync, this patch moves global
cluster docs into overview_global_cluster.rst from admin_guide.rst.
Co-Authored-By: Alistair Coles <alistair.coles@hpe.com>
Change-Id: I624eb519503ae71dbc82245c33dab6e8637d0f8b

Clarify that synced segment container names must be the same
when syncing large objects.
Also add multipart-menifest query string option to API ref
for object GETs.
Change-Id: Ib2d2a1e6c1e5eff215fc75c2b49e7d6758b17b7e
Partial-Bug: #1613681
Closes-Bug: #1613316 

This change introduces the concept of a "versioning mode" for
versioned_writes. The following modes are supported:
 * stack
 When deleting, check whether any previous versions exist in the
 versions container. If none is found, the object is deleted. If the
 most-recent version in the versions container is not a delete
 marker, it is copied into the versioned container (overwriting the
 current version if one exists) and then deleted from the versions
 container. This preserves the previous behavior.
 If the most-recent version in the versions container is a delete
 marker and a current version exists in the versioned container, the
 current version is deleted. If the most-recent version in the
 versions container is a delete marker and no current version exists
 in the versioned container, we copy the next-most-recent version
 from the versions container into the versioned container (assuming
 it exists and is not a delete marker) and delete both the
 most-recent version (i.e., the delete marker) and the just-copied
 next-most-recent version from the versions container.
 With this mode, DELETEs to versioned containers "undo" operations
 on containers. Previously this was limited to undoing PUTs, but now
 it will also undo DELETEs performed while in "history" mode.
 * history
 When deleting, check whether a current version exists in the
 versioned container. If one is found, it is copied to the versions
 container. Then an empty "delete marker" object is also put into the
 versions container; this records when the object was deleted.
 Finally, the original current version is deleted from the versioned
 container. As a result, subsequent GETs or HEADs will return a 404,
 and container listings for the versioned container do not include
 the object.
 With this mode, DELETEs to versioned containers behave like DELETEs
 to other containers, but with a history of what has happened.
Clients may specify (via a new X-Versions-Mode header) which mode a
container should use. By default, the existing "stack" mode is used.
Upgrade consideration:
======================
Clients should not use the "history" mode until all proxies in the
cluster have been upgraded. Attempting to use the "history" mode during
a rolling upgrade may result in some requests being served by proxies
running old code (which necessarily uses the "stack" mode), leading to
data loss.
Change-Id: I555dc17fefd0aa9ade681aa156da24e018ebe74b

Changed sentence: "Regions can be used to describe geo-graphically
systems characterized by lower-bandwidth"
To: "Regions can be used to describe geographical
systems characterized by lower-bandwidth"
Change-Id: I0f614a4c53dd31459f1b6297dd32a8c0f609d9ce
Closes-Bug: 1612302

The goal is to modify schedule priority and I/O scheduling class and
priority of daemon/server via configuration.
Setting is optional, default keeps current behaviour.
Use case:
Prioritize object-server to object-auditor, because all user's requests
needed to be served in peak hours and audit could wait.
Co-Authored-By: Clay Gerrard <clay.gerrard@gmail.com>
DocImpact
Change-Id: I1018a18f4706daabdb84574ffd9a58d831e68396

added comments on how to run in_process and specific
test cases
Change-Id: I485755996b15753323d30de09914d35e262fcedc
Signed-off-by: Thiago da Silva <thiago@redhat.com>

Throughout the manpages maintaining references to OpenStack Swift.
Change-Id: I2a0c2658e10a92671bfc092c0a3abaddfd8cd7d9
Closes-Bug: #1609687 

Closes-bug: #1607017
Change-Id: I365edf77c5bf34e2e51d7f10c9ea1012c1bda8ed

Change the link to the admin docs to point to #dispersion-report
rather than non-existent #cluster-health.
Change-Id: Ia2f4262c266201d4d555e7bedb8c5c2eb9fb1264

Remove the repeated OPTIONS section headers, which looks odd
and is inconsistent with swift-dispersion-populate.
Change-Id: I6d894e3b61002ddf7c0ea8a78cde226617eb11a6

This change adds -P / --policy-name option to the swift-dispersion
manpages. Also tidied up a little removing some extra whitespace at the
end of lines.
Change-Id: Ic3372379994964e96258939580452f94fb575a06
Closes-Bug: #1605686 

Running functional tests in the in-process mode uses
the default value for the pipeline. This patch adds support
to specify the SWIFT_TEST_IN_PROCESS_CONF_LOADER variable
to point to a labeled function that changes the proxy
configuration for the functional test.
The patch also adds a new tox environment
func-in-process-encryption
which runs with the environment variable
SWIFT_TEST_IN_PROCESS_CONF_LOADER=encryption
The motivation for this change is to put support in place for an
upstream CI job that will functionally test using encryption
middleware in the pipeline. The gate job is proposed at:
https://review.openstack.org/#/c/348292/
Change-Id: I15c4b20f1d2be57ae21c69c614f6a9579145bee9

Change-Id: I6f0cc1004a40e77345c641c0e5076f2f5dadb891

Change-Id: Icabc5a8316f5e8fd887bb42358ad03e9c43d0765

Change-Id: If764de0a28f5afb858b3e892b35fe5fa147a0650

If the curl command is used exactly as in the help, the ampersand
in the signature is interpreted as an operator and the curl
command breaks. I am aware of developers who have wasted a lot of
time because of this.
Change-Id: I6468c9a098b56db8242a2cf2c23b7a4857bd8574

An high or increasing partition count due to storing handoffs can have
some severe side-effects, and replication might never be able to catch
up. This patch adds a note to the admin_guide how to check this.
Change-Id: Ib4e161d68f1a82236dbf5fac13ef9a13ac4bbf18

Deployment guide does not talk about the region. Also, it does not
specify that regions and zones need to be ints.
This patch adds brief description about region and changes numbers
to int. Also, adds region in the document that talks about ring data
struture.
Change-Id: I04ce42fb3e5c1f08e7f7ff6be23482cee8bdeb71
Partial-Bug: #1583551 

In the swift deployment guide, region is missing from the syntax of
adding a new device to the swift-ring-builder.
This patch adds region in the syntax.
Change-Id: I43e247c92d461efd530c0f82ca3daddcb9e2ba5b
Closes-Bug: #1584127 

Drive-by fix for crypto filter_factory test.
Add note to encryption doc to highlight that root secret
should not be changed (follow up on earlier review comment).
Co-Authored-By: Tim Burke <tim.burke@gmail.com>
Change-Id: I9776cddd4d045408325342983e285a00c992bfae

Fixed naming conventions of Keystone, Swift and proxy servers in
the docs.
Change-Id: I294afd8d7bffa8c1fc299f5812effacb9ad08910

libssl-dev/openssl-devel are already listed in other-requirements.txt;
add them to installation instructions in the SAIO docs.
Change-Id: I3dc07213ff8dac1299d3eb68d3448a77e15c79af

Change-Id: Iffad70b2fd901b305dc66d363039b7df44d619da

Change-Id: I4e7bb85ce746fcb1ec3a4cbf534761e4e47634c9
Closes-Bug: #1599888 

Co-Authored-By: Christian Cachin <cca@zurich.ibm.com>
Co-Authored-By: Mahati Chamarthy <mahati.chamarthy@gmail.com>
Co-Authored-By: Peter Chng <pchng@ca.ibm.com>
Co-Authored-By: Tim Burke <tim.burke@gmail.com>
Co-Authored-By: Thiago da Silva <thiago@redhat.com>
Co-Authored-By: Clay Gerrard <clay.gerrard@gmail.com>
Co-Authored-By: Jonathan Hinson <jlhinson@us.ibm.com>
Co-Authored-By: Samuel Merritt <sam@swiftstack.com>
Co-Authored-By: Janie Richling <jrichli@us.ibm.com>
Co-Authored-By: Hamdi Roumani <roumani@ca.ibm.com>
Co-Authored-By: Kota Tsuyuzaki <tsuyuzaki.kota@lab.ntt.co.jp>
Change-Id: I1d8b030b9c8f81a232da5d6f93f442e46e331af2

Include a note in container-sync docs pointing to specific
configuration needed to be compatible with encryption.
Also remove the sample encryption root secret from
proxy-server.conf-sample and in-process test setup. Remove encryption
middleware from the default proxy pipeline.
Change-Id: Ibceac485813f3ac819a53e644995749735592a55