Fix for container sync not syncing last rowid

Bug 1079439

Change-Id: I1985a7176f34931ecb0f24c0289f18df5e934598
Improve container-sync docs.

Two improvements: first, document that the container-sync process
connects to the remote cluster's proxy server, so outbound
connectivity is required.

Second, rewrite the behind-the-scenes container-sync example and add
some ASCII-art diagrams.

Fixes bug 1068430.

Bonus fix of docstring in wsgi.py to squelch a sphinx warning.

Change-Id: I85bd56c2bd14431e13f7c57a43852777f14014fb
Updates to use new keystoneclient middleware.

Updates the proxy-server.conf-sample and docs to use
the new Keystoneclient middleware class name.

Change-Id: I3727f7b7328a2513347b8ef257c270126df36d7b
Merge "Fix for container sync not syncing last rowid"
Merge "Updates to use new keystoneclient middleware."
Added --top option to swift-recon -d

When showing the disk usage dispersion graph it is often useful to
know what those top full drives are so you can do further research.
Now you can run 'swift-recon -d --top 10' to list the top ten devices
by fullness after the usual dispersion graph.

Change-Id: I7ddb2141e55e0613f69750fabe544940192c2d48
Swob bugfixes; for ? in names specifically

It was discovered that uploading items with ? in their names (encoded
with %3F of course) made Swob fail in that it trimmed off everything
after the ? as if it were a query string.

Change-Id: Ie686db9a2177aafad2e77c307ffc3f446646fbb5
bp/cross-tenant-acls: allow tenantId:user, tenantName:user, and *:user ALCs

Change-Id: I7cfe77b3f03172814814f2e2bae04a3ae184efb0
Merge "Improve container-sync docs."
406 if we can't satisfy Accept

The container and account servers should respond with 406 if the Accept header
isn't satisfiable.  This behavior is defined in RFC 2616 section 14.1.

Change-Id: I8a67ccafe33dc70ef4f7794686a54fbc8581f4dc
Merge "Added --top option to swift-recon -d"
Merge "406 if we can't satisfy Accept"
drop_privileges should also set HOME

E.g. if HOME is not set, swift-proxy will create the
keystone_signing file not in HOME but in /root.
This is because the swift user doesn't have a shell
in /etc/passwd and so it doesn't set environment variables
when impersonating.

Change-Id: I3013007e0dadf6ddccc176e142b7c78c5d63a351
Ignore pycscope files

Change-Id: I5fe38f28896d086e56ba9e718b02227d87dd4a2d
Signed-off-by: Peter Portante <peter.portante@redhat.com>
Allow optional, temporary healthcheck failure.

A deployer may want to remove a Swift node from a load balancer for
maintenance or upgrade.  This patch provides an optional mechanism for
this.  The healthcheck filter config can specify "disable_path" which is
a filesystem path.  If a file is present at that location, the
healthcheck middleware returns a 503 with a body of "DISABLED BY FILE".

So a deployer can configure "disable_path" and then touch that
filesystem path, wait for the proxy to be removed from the load balancer
pool, perform maintenance/upgrade, and then remove the "disable_path"
file.

Also cleaned up the conf file man pages a bit.

Change-Id: I1759c78c74910a54c720f298d4d8e6fa57a4dab4
Merge "Allow optional, temporary healthcheck failure."
Merge "drop_privileges should also set HOME"
Merge "bp/cross-tenant-acls: allow tenantId:user, tenantName:user, and *:user ALCs"
capture resetswift output in probetests

This change makes the dots prettier during probetests

When calling the resetswift script, the probetests will use subprocess
to redirect stderr to stdout and capture stdout into a buffer.  We print
the captured buffer from resetswift's combined stdout/stderr and let
nosetests stdout capturing handle printing the output for debug only if a
test fails.

Change-Id: I022512f2ef5a4c43b0e49264bad1bca98c1f0299
Allow dot test runners from any dir

Currently the .*test files in the source tree root seem to assume you're
in that directory when you run them.  This change should work exactly
the same except for removing that restriction.

Change-Id: I9b037016490dd6d5b515cb2c3cad2f99ee40bb6d