Fix resource_setup order in scenarios

As resource_setup() document says, we should check skip condition before
resource_setup. However some functions in scenarios setup resources
before skip checks. We should avoid to setup unnecessary resources as
possible. This commit fixes the order.

Change-Id: Id0529fc80f2b80f028fd078140fe5fd7459e9309
Test to update port with CIDR value

creating a port with allowed address pair
verifying the port creation with allowed address pair

creating a port, updating a port with CIDR value
verifying the port creation with CIDR value

creating a port, updating a port with Multiple ip and Multiple mac
verifying the port updation with Multiple ip and Multiple mac

Change-Id: I22a041df97f9f630b66c48f92f4c0da12db75b0a
Remove "Disabled Reason" from test_cinder_service_list

The CLI test test_cinder_service_list checks the output of
"cinder service-list" for a set of column titles. One of the titles
it expects to find is "Disabled Reason". However, this title is not
guaranteed to be in the output; cinderclient only appends it if
the value shows up in the response from the server.

Change-Id: I060bad255ff17b132737a8878c26e7d5cf9dce82
Closes-Bug: #1392662
Update docs for regenerating sample conf file

Change-Id: I0999b75f43248b7e3e826845aaabff239aeab013
Creating individual resources for vpnaas test case

As per design there is only one vpn-service object per router.
Tempest test cases were failing due to creation of multiple
vpn service object for the same single router by raising an
router in use execption.so creating individual resources for
each test cases.

Closes-Bug: 1376104

Change-Id: Id327488c039374160bbfaa9705b869a38aa0583c
Fix empty string as id in create flavor request

test_get_flavor_details_for_deleted_flavor specify "" as the
id value for creating the flavor.

Nova V2 API validation is loose and the API accepts this
value. However, V2.1 API will not allow empty string as id.

This patch fix this by passing 'None' as id in this test.

Change-Id: I86419368a4c85aaf039278999d3d8c3c1e224c74
Make delete_container use expected_success

This is the new standard for tests that use the api client.

See also: I07316db1f51d0562919ed2a50f002011944bfdb1

Change-Id: I309084ab0d13fa3bf3a84dcbe4ddee5b24284b66
enable cinder v2 api for volumetype test

The existing code is updated with the cinder v2 api.

Partially implements: blueprint cinder-v2-api-tests

Change-Id: I2e01284cad090a0633ae472c5995986bd55dc349
Make every swift clients use expected_success

Based on an original work by Swapnil Kulkarni in
I6a5511969d0432345529da6cd82544d2f8187468

Partially Implements blueprint: client-checks-success

Change-Id: I80bc2c2723bfeabb35fafc2b5733800ab5449f8c
Merge "enable cinder v2 api for volumetype test"
Merge "Update docs for regenerating sample conf file"
Merge "Make delete_container use expected_success"
Merge "Fix resource_setup order in scenarios"
Merge "Fix empty string as id in create flavor request"
Merge "Remove "Disabled Reason" from test_cinder_service_list"
Merge "Make every swift clients use expected_success"
Merge "Creating individual resources for vpnaas test case"
Merge "Test to update port with CIDR value"