Add tox job to build docs

This commit adds a tox job to build the docs. It calls the setup.py
build_sphinx command.

Change-Id: I84dbd1aaea142bbe45c73df04856e128621143db
Change of copyright to HP for keystone regions

Modified copyight header from "OpenStack Foundation" to
"Hewlett-Packard Development Company, L.P" as the following files
were submitted by  Hewlett-Packard Development Company according to the
review link https://review.openstack.org/#/c/93347/

tempest/api/identity/admin/v3/test_regions.py
tempest/services/identity/v3/json/region_client.py
tempest/services/identity/v3/xml/region_client.py

Change-Id: Id6ff2717d882b165636f010590d00dd2ebb4e184
Add a skip for bug #1334368

Trust checking for 204 response is incorrect to support httpd based
deployment because mod_wsgi could translate a HEAD call to GET.
According to HTTP spec HEAD needs to respond with the same
response as GET.

This disables the trust check for HTTP 204 for
changeId: I13ce159cbe9739d4bf5d321fc4bd069245f32734

Once the changes to Icehouse and Juno (master) are accepted, this
can be modified to look for HTTP 200 and re-enabled.

Change-Id: I5e7d7dab2fc1432888bf8c691cae9f2109ac2fec
Partial-Bug: #1334368
Merge "Add a skip for bug #1334368"
First part of moving success response checking to identity client

Adds client success checking and removes test code checking of responses
for methods contained in the IdentityClient classes. This includes
IdentityClientJSON, IdentityClientXML, IdentityV3ClientJSON and
IdentityV3ClientXML. It also includes v3 ServiceClientJSON and
ServiceClientXML since the service methods seem to have been split out when
the v3 clients were created. This is a large patch but it was important to
make these changes together because there were changes in return codes between
v2 and v3 but the method names are in many cases the same. I didn't want to
risk a mistake by trying to separate v2/v3 into separate changes.

The doc for some keystone list apis says they can return 200 or 203. Only
one of the calls to list-users-for-tenant was checking for both so it seems
that 203 is not actually returned. I removed the check for 203.

Doing this uncovered a case where there was an unbound variable and an
incorrect status check that combined to create a test that passed. This bug was
also fixed.

Closes-Bug: 1336826
Partially implements: blueprint client-checks-success

Change-Id: I75633b5b94b1750a623f6a2b8adaae1efc5c7c9c
Merge remote-tracking branch 'upstream/master'
Merge "Change of copyright to HP for keystone regions"
Merge "Add tox job to build docs"
Merge "First part of moving success response checking to identity client"
Merge remote-tracking branch 'upstream/master'