Scenario manager: catch Exception in get_remote_client

Several scenarios have the same try/catch block around get_remote_client,
let's factor this.

Change-Id: Ib22624236503c2ee7665af006a4976fe4b127705
Firewall as a service API Test Enhancement

 Add Test to insert and remove firewall rule to firewall policy
    -Create a firewall rule
    -Create a firewall policy
    -Insert a firewall rule to policy
    -Validate the insertion of rule to policy
    -Create another firewall rule
    -Insert the another rule after the first rule
    -Validate the postion after the rule insertion after the first rule
    -Remove the rule inserted second time
    -Again Insert that  rule before the first rule
    -Validate the position of rule inserted before  the first rule

    Add Test audited attributes of firewall policy
    -Create a firewall policy
    -Validate the default audited attribute
    -Update the audited attribute to true
    -Insert a firewall rule
    -Validate the audited attributes of the firewall
     policy

Change-Id: Ib3fefb42b976e2ebb6921cab4290e9c7dbaa58c2
Basic networks Scenario Test Enhancements

Add test to update router admin_state_up attribute of the router
-Update admin_state_up attribute of router to False and check public
 connectivity
-Update admin_state_up attribute of router back to True and check public
 connectivity again

Change-Id: I3fd56c44411ff6919e15dd1033f6c13e58271f4b
Ironic: Remove few misguided negative tests on ports

As part of https://bugs.launchpad.net/ironic/+bug/1398350 Ironic is fixing
a bug where the josn-fields in the resources only accepted string and
int, as part of the work Ironic will now support any json serializable
value on those fields.

Some negative tests on ports were considering float to be a malformed
value, which they are not. This patch is removing those tests.

This patch is also adding tests checking for the new supported values
in the API.

The patch in Ironic adding support for multiple types is this one:
https://review.openstack.org/#/c/137762/

Change-Id: I02e95d77a90b3c1a8e203cf83cc0ec28b5460e58
Log the credentials used to clear networks

Without knowing what credentials are used to cleanup its difficult to
figure out what "Clearing network: None, subnet: None, router: None"
means.

Change-Id: I649d64f8aecc77d13837b4f0a06911f975b5ccb8
Add more verbose info for wait_for_..._status methods

If this method failed because the resource will not reach desired
status, you just know expected status, not actual status at time of
timeout. It can help with debugging.

Change-Id: I583f0739bf771dd587acd13c1453ae6a440a9e87
Merge "Log the credentials used to clear networks"
Revert "Log the credentials used to clear networks"

This is using the incorrect format and it's spewing errors everywhere.

This reverts commit 38156b7a2a23666b1908c5c97d210b3676c12090.

Change-Id: If3d32320eb707531b9b37324ddbebeeb62574041
Ensure extension aliases are used for nova based services

This commit fixes the extension checker in verify-tempest-config to
ensure that nova and nova based services are using the extension
aliases instead of the extension names. The extension names are meant
to be human readable and are not the best way to identify it. This is
what the tempest code is also expecting, however in some cases the
name was still being used by the verify tool, which was incorrect. As
part of this it was necessary to fix several other places where name
was being used instead of alias, or other extension list formatting
response checking was incorrect.

Change-Id: I35f5db655f065f29760515a26db1fb508d229393
Merge "Revert "Log the credentials used to clear networks""
Merge "Ironic: Remove few misguided negative tests on ports"
Merge "Scenario manager: catch Exception in get_remote_client"
Merge "Firewall as a service API Test Enhancement"
Merge "Add more verbose info for wait_for_..._status methods"
Merge "Basic networks Scenario Test Enhancements"
Merge "Ensure extension aliases are used for nova based services"