Add a check for compute api versions to verify_tempest_config

This commit adds another verification method to the
verify_tempest_config script that adds a check to see if the compute
v3 api is enabled.

Partially implements bp config-verification

Change-Id: Idae7db73c9eba94b7f74ec2f71e20d4267aa582c
Fix parameter type spelling tempest HOT template

HOT template file heat_minimal_hot.yaml uses uppercase spelling
for parameters, where HOT should use lowercase (e.g. string instead
of String).
While code has has been toloerant so far, the following change for
parameter schema validation refactoring make checking more strict
and causes tempest to fail:

https://review.openstack.org/67183

This patch fixes parameter type spelling in the tempest HOT
template.

Change-Id: I52a1b2272cd299cce3259805ee240a5782772aa4
Closes-Bug: #1270833
Fix parameter in auth error message

Using Idenitity V3 auth method the AuthenticationFailure exception waits for
the project name parameter to show it's message correctly.

Change-Id: I1458f6c20cf65057663ecbf52a931c288fd4275c
Use automated create and update methods for core network resources

The patch makes use of automatic create and update methods for
networks, subnets, ports. Bulk create method was moved to base client
to get rid of code duplication in json and xml versions.

Change-Id: I0e1295d6c195187d36b3b811a0dd28c5477cd07b
Use unittest2.TestSuite with py26

The tempest master branch with tox -efull with py26 command,
produces a lot of tierDownClass failures,
because it tries to tearDown an already tearDowned class.

By switching to unittest2.TestSuite the issue is solved.

Change-Id: I7a5d21af62bafb13cdc8a0dcc20ed3f742aa214f
Merge "Fix parameter in auth error message"
Merge "Use automated create and update methods for core network resources"
Specify 'active' status for deleting situations

The test creates 3 backups with the rotation 2 and checks that
2 backups exist with getting its image list. test_create_backup
fails sometimes due to the existence of 3 backups.

Glance v1 delete_image API changes an image's status to 'deleted'
then the deleted flag to 'true'. If getting a list between the
status change and the delete flag change, we can get a list including
the deleting backup also like the following:

{"images": [
  {"status": "deleted", "name": "backup-1-tempest-438772029",
   "deleted": false, ..},
  {"status": "active", "name": "backup-2-tempest-2111479443",
   "deleted": false, ..},

To avoid this situation, this patch adds the status 'active' to the
calls which get the backup list.

Change-Id: I59966534a8eb1430604cada1f64b8c8df46a5f17
Closes-Bug: #1267326
Merge "Use unittest2.TestSuite with py26"
Merge "Specify 'active' status for deleting situations"
Merge "Fix parameter type spelling tempest HOT template"
Merge "Add a check for compute api versions to verify_tempest_config"