Change help message for volume-update

`nova volume-update <server> <volume> <volume>` to
`nova volume-update <server> <attachment> <volume>`

Change-Id: Ie820843c3e8d23659075c1d6b4fdd47f639b3b58
Closes-bug: 1326613
Convert Floating IP tests to httpretty

Change-Id: I0f6816868580af32ee93c0bfdf2c113c6c6ecd13
blueprint: httpretty-testing
Convert Floating IPs DNS tests to httpretty

Change-Id: I19dfadbe9103145a6b80d8ce10d2b6d3ce326ffa
blueprint: httpretty-testing
Convert Floating IP bulk tests to httpretty

Change-Id: I4b81963ab6a9924c5f2262f49a42baa56326964d
blueprint: httpretty-testing
Remove _print_volume from volume-update

Since the response of volume-update do not contain a body, just a status
code 202, so when calling _print_volume(volume), there will be an error:
`ERROR (AttributeError): 'NoneType' object has no attribute '_info'`.

Change-Id: I950ae7dca5e847beae7295d72d009f2d07d07c51
Closes-bug: 1321205
mask keystone token in debug output

replaying the keystone token in debug output is both completely
burdensome to read (given it's unbounded size), but it's also
potentially a security issue given that it could be used in replay
attacks.

Instead, filter the headers to sha1 sensitive things, with X-Auth-Token
being the only one listed so far. The sha1 will at least give us the
understanding of tokens being the same or different (and an administrator
could use that to figure out if they were valid later).

This also removes some extra '\n' that were being injected into the
debug logs, because they were not helping with readability.

Lastly, actually test logging. This introduces the first tests of the
logging path using the logging fixture. It's pretty basic, but does
verify that requests are logged at debug, that the SHA1 format works,
and that headers which are not listed get shown straight through.

DocImpact because this changes the curl dumped strings which people
may have been using. They can still do that as long as they generate
their own keystone token.

Change-Id: I1edb94785705c3b6a05f118b77d3aeb07461cd44
add tox target for python 3.4

Ubuntu 14.04 has python 3.4 so add a 3.4 target. 
Note that this will fail unless
you have new enough virtualenv. Recommend you install the packaged
version of 1.11.4 and get rid of any pip installed ones.

Change-Id: Ib54dc49fca2463f1c5cd788b48d06bd85be52655
Merge "mask keystone token in debug output"
adjust to {SHA1} convention for token

based on openstack-dev mailing list thread, support the {SHA1}
convention for headers that is generally agreed on.

Also fix a minor issue that Johannes found after the review landed,
which was doing substring matching instead of tuple matching.

Change-Id: I80a456c765026ac6179fd424ead01715798c1dac
Fixes wrong value description for volume-detach

The description of the <volume> argument is not proper, the <volume>
argument is indeed "ID of the volume". “Attachment ID" is the internal
term of nova/cinder. So change description 'Attachment ID of the
volume.' to 'ID of the volume to detach.'

Change-Id: I262d72f6f676e260a58d45b750dbd60fc7c3dcf5
Closes-bug: 1321073
Merge "Remove _print_volume from volume-update"
Merge "Change help message for volume-update"
Add posargs support to flake8 call

Add posargs to flake8 call in tox.ini, with this you can pass arguments
directly into flake8 using the following notation
  tox -epep8 -- --FLAKE8-ARG

This can be used to pass arguments like '--statistics' to flake8

Change-Id: Ia820d62c4a1f428d60d88b04d8a4d9b1442baa09
Merge "Convert Floating IP tests to httpretty"
Merge "Convert Floating IPs DNS tests to httpretty"
Merge "add tox target for python 3.4"
Bump hacking to 0.9.x series

In order to keep this patch to just a requirements bump, ignore new and
stricter hacking rules that are being triggered. Fixing up the code and
turning these on is out of scope of this patch and is for future
patches.

Change-Id: Ia3517e705f894b48585b957c21e7a3a6ed90e586
Merge "Convert Floating IP bulk tests to httpretty"
Merge "Add posargs support to flake8 call"
Merge "adjust to {SHA1} convention for token"