Security groups are a non-configurable resource for ssh validation

[Daryl Walleck]

The resource validation setup (https://github.com/openstack/tempest/blob/master/tempest/test.py#L532) will create security groups and rules unless a value for these parameters is passed into the method. However, there's currently no way to impact this value, so these resources are always required. This is problematic if your environment either does not have security groups or does not have the nova os-security-groups extension enabled.

Based on the above mentioned code, a very straightforward solution would be to add a new configuration to the validation section (use_security_groups?) and use that configured value if no other parameter is provided, much like is done with auth_method and connect_method.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/214743

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/214743
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=c6cc91dada17cf6a91a3f8e4dc159cdfda4734a0
Submitter: Jenkins
Branch: master

commit c6cc91dada17cf6a91a3f8e4dc159cdfda4734a0
Author: Brandon Palm <email address hidden>
Date: Wed Aug 19 13:20:21 2015 -0500

    Added CONF.validation entry security_method

    Added a config entry for defaulting the security_group and
    security_group_rules instead of just hard-coding it if no
    variable is provided.

    This should still provide the same functionality as previously
    written but give the option to be more flexible for
    different environments that don't need the security_group
    variables enabled.

    Change-Id: Ic78805849d6dc1950f334d0142714b62a98ccf0a
    Closes-Bug: #1486198