modifies the test to sort based on UUID

This patch modifies the volume-list filter test to perform the sorting
based on UUID instead of created_at timestamp as this timestamp might
be same for two volumes but UUID for every volume is unique.

Change-Id: Ibe1ab23c12ad8afe8d5adab6fe0c617445adc90d
Closes-Bug: 1313970
Add tests for availability-zone-list CINDER V1 API

This patch adds the JSON/XML clients and tests for CINDER
availability-zone-list V1 API

Change-Id: I4fc24e92def95d4a39d43877b120875b45bde9f9
adds tests for CINDER encryption volume-type APIs

This patch adds the JSON tests for CINDER encryption volume-type V1 APIs.
It also adds the JSON clients for following APIs :
1. cinder encryption-type-delete

Change-Id: I20a68684f950fe36653eb4304edb56e244867ca3
Add API test for resizing a stopped server

The compute API allows resizing a stopped server but we don't test it
and we've regressed that flow in the past, so add a test to guard
against it.

Change-Id: I6ca84da9deb9b9a97fad0e68b5f0845a617ae314
add test for command bash-completion

Change-Id: Ic9f02e05f8f99a30adf40266417ee4288765d7dc
Closes-bug: #1319294
Remove time.time mock from test_ssh

The function time.time is used in many places and especially in logging.
Mocking this function causes issues if the log level changes due to the
fact that every log message will cause a time.time call.

Splitting the test cases into 3 pieces since the time.sleep mock is
only usable for the good case. All tests with retries can't use it
and need to assert the result by measuring the time.

This fix is needed to use oslotest for tempest unit tests.

Change-Id: I800690f8ee1ee580cfcd71500b86782ff571ac0d
Closes-bug: bug 1320482
Fail fast during advanced networking test

This gives us the opportunity to discern whether the network
was sane prior to the server operation under scrutiny.

Change-Id: Iacc4f0307019efafda0de3abb0fa71ad13770850
Closes-bug: #1312841
Switch back to nc in test_load_balancer_basic

After test_load_balancer_basic started using inetd instead of netcat
we've started getting "BadStatusLine" errors from urllib.

That is why we need to move back to using netcat.
Also handle "BadStatusLine" error.

Related bug: 1309252
Change-Id: Ida919c63e27c6a003be4c249ba2e6f3e2ea7a7b3
Sahara: add API tests for data sources

* create/list/get/delete API tests for data sources in Swift were added
* create/list/get/delete API tests for data sources in local HDFS
  were added
* create/list/get/delete API tests for data sources in external HDFS
  were added

Partially implements: blueprint savanna-api-tests

Change-Id: I78fe5c53d3af84c04402966891c096c8cbd1253a
Start using oslotest for tempest unit tests

This commit starts using the oslotest library. The fixture
oslo-incubator library is still left in the tree because I didn't
see the Config fixture in the library tree yet.

Also, it's probably worth noting that if the lock fixture is moved
from incubator to the library that oslotest will become a runtime
requirement on tempest. (which probably means we'll want to install
it from git in the gate)

Change-Id: I638f28975dff4cde2e4eaa6c154a41e66a0746e4
Sahara: preparations for job binary internal tests

* create/list/get/delete methods to Sahara API client
  for job binary internals were added
* Method "create_job_binary_internal" was added
* tearDownClass method was expanded

Partially implements: blueprint savanna-api-tests

Change-Id: I1013ce8d93ec44d5d5961bcd887812bdd1c6fcfb
Cleanup docstring in test_l3_agent_scheduler

The docstring was incomplete in saying it required the
l3_agent_scheduler extension to be enabled.  I think it probably meant
to say that l3_agent_scheduler was listed in
network_feature_enabled.api_extensions, but that defaults to 'all' so
rather than explain how that config option works in the docstring, just
say that the l3_agent_scheduler extension is required and assume the
user understands how to configure Tempest.

Change-Id: If504bd6374b83dea24fa92f9ef6c852d76308ad1
Verify server list_addresses V2/V3 APIs attributes

This patch adds the JSON schema for Nova V2 & V3 server list_addresses
APIs response and validate the response with added
JSON schema to block the backward incompatibility change in the future.

The response body of server list_addresses V2 API is below:

{
    "addresses": {
        "private": [
            {
               "version": 4,
               "addr": "192.168.0.3"
            }
        ]
    }
}

The response body of server list_addresses V3 API is below:

{
    "addresses": {
        "private": [
            {
                "version": 4,
                "addr": "192.168.0.3",
                "type": "fixed",
                "mac_addr": "aa:bb:cc:dd:ee:ff"
            }
        ]
    }
}

Partially implements blueprint nova-api-attribute-test

Change-Id: I21392dfb8141d0cf98bf2dcbcb3fd49e75f9cbd8
Add Marconi Smoke Tests

Add smoke tests that check the existence of queues.
Add test that checks list queues.
Add test that gets queue statistics.
Add test that sets and gets queue metadata.

Tests for List Queues and Queue Stats use JSON Schema
validation.

Change-Id: I084d1ae0de4a729a913a7084f14c0d3172af29d3
Implements: blueprint add-basic-marconi-tests
Make test_server_cfn_init a scenario test

Converting test_server_cfn_init to a scenario test is long overdue
since it is more of a scenario than an exercising of the heat API.

The heat-slow job has gone non-voting because this test fails
~%50 of the time due to bug #1297560. The server boot log is now
logged regardless of success or failure to build up data to diagnose
the issue.

This also adds several convenience functions to the test base class.

Co-Authored-By: Steven Hardy <shardy@redhat.com>
Related-Bug: #1297560
Change-Id: I077aeaf2bf8b292699eb20c5a75c59df35645913
Add quota delete test to cinder

This submission is to validate delete quota set in
volumes quota set test case. Hence added delete quota
set method in both XMl and JSON interfaces.

Change-Id: I217355bfc7696b93bc1f1388635cbb9bf8850199
Update version string to follow new convention

Since adopting branchless we've moved to a different "release" model
were we just tag the tree at set points. We're using an incrementing
integer to name these tags. Since the first tag, 1 was pushed to
correspond with the start of branchless tempest. The current working
tag is 2.

Change-Id: I93be84da9bf2a09e9ca9c2f4231f1a4a75da3af9
validate server action 'console_output' attributes

This patch adds the JSON schema for Nova V2 & V3 get_console_output
server action APIs response and validate the response with added
JSON schema to block the backward incompatibility change in the future.

The response body of get_console_output V2 & V3 APIs is same and given
below:

{
        "output": "FAKE CONSOLE OUTPUT\nANOTHER\nLAST LINE"
}

Partially implements blueprint nova-api-attribute-test

Change-Id: I22e61d1fed926aa9a310a46b12748db401dec045
remove skip attributes for fixed bug

1. remove skip attributes for test_run_terminate_instance

2. add forgotten changes for commit
   55c597db0f59fc7a3eaa7bec8bc7509f5a87c884
   (Fix InvalidInstanceID.NotFound handling)

Change-Id: I616a90f98e3874a09274d961345476d47d266db0
set all build_intervals to 1s

10s build interval is really long, and not very sensible. Setting
to 1s should speed things up a lot.

Change-Id: If8332d4be8515ac574cbbf4e00cbe0a75b6ebc5d