Configuring test environment should be handled in contrail-test

[Harish Kumar]

Currently test environment configuration is happening from contrail-fabric-utils (tester.setup_test_env), thus contrail-test have a critical dependency on contrail-fabric-utils.

This dependency should be reduced by handling the configuration from contrail-test itself.

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/16039
Submitter: Harish Kumar (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/16039
Committed: http://github.org/Juniper/contrail-test/commit/a6a4e89cdd662c29371ea1eaa7ff17099e450300
Submitter: Zuul
Branch: master

commit a6a4e89cdd662c29371ea1eaa7ff17099e450300
Author: hkumarmk <email address hidden>
Date: Wed Dec 30 13:52:58 2015 +0530

Configure test env from run_tests.sh itself

This is to avoid dependency on fabutils to setup test environment and to
make contrail-test self sustained.

Added tools/configure.py which accept test directory and
contrail_fab_path as parameters and generate sanity_params.ini and
sanity_testbed.json from testbed.

modified run_tests.sh to check if $config_file (default to
sanity_params.ini) exists and if not, run tools/configure.py to generate
both sanity_params.ini and sanity_testbed.json. It also modified to
accept one more parameter --contrail-fab-path, with default to
/opt/contrail/utils so that one can provide fab path in case of using
different path.

Change-Id: I0abc675ee59474c1131135266da6412f8a77d24e
Fixes-Bug: #1530051