tree 31fab41673f2d922934429688f6d721eefc5d492
parent 54451b48d8efcf3c7129d3886e238230f998709b
author Matthew Treinish <mtreinish@kortar.org> 1435692754 -0400
committer Matthew Treinish <mtreinish@kortar.org> 1438021314 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2
 
 iQIcBAABCgAGBQJVtnbDAAoJEP0SoPIUyeF3RcUQANJk+84esf7ABaVJYjjCZh2K
 3gTfxx3d3H0DWGWGYRSc0nK4jfGxOrWrWIoWF1iwwtnRy/FnxtqibU2tqCZeaewi
 BITVgbFUrPGFu1y8c0ARK3/Ide5Kqr7KWFgVwtHFhp7kyAtFcN3AKlgsiJlI33B9
 fWA/O6EKnRbD/nA6fiehiwGQ7MkwYCCO/uV+N3JkpuytbUiv/7RiORRx5x3BQ5ZC
 KOco7kW1dbOtt2fQRWYRc7OIgFMYbCBip5rhdCZbS9pwAfXxwkFfks76lfa2hXun
 KMi0nu5etjglG4tYFyWYbnRvRZj+Z6wErh7CuVXN1Kg56Exnose72sSXOgFjoMXJ
 sr0SmRR0mxMl6m5rAcoB6moc//PPNG2d/WU/KUvAvqDF6Ejc9hIcn4RrUt6m/01Y
 NJ2vXLRQh8ZQRjfK+FNcH1Z91e7XXv8VtE9oT28JdXtLoPI9FhhExNWa78cP2wmC
 chhLWgP+eDjE4oww4UhqlFPXhhZdHwHm31WIcJ+mqRp0WGQAka4KlVl91T74/0qD
 Y7Y23bG9ZhGFV8TzjCnaTVaYWZ24xcxUknOi/yAeVTJc2ct6rBOy2ECeDy4Q1OIf
 Rbb+tyj5CfFVPeTA0I/Tv3Z+N5sg1qQeLJaSgtDbqb0wwm6J2PBi7IbUu1en8E35
 iNVoYhPXNhJTxSm2oV23
 =z/VU
 -----END PGP SIGNATURE-----

Add tempest init command to tempest cli

This commit adds a new 'tempest init' command to the unified cli.
This command tempest init will be the first step of the new workflow
for running tempest. It is used to initilize a local working directory
to run tempest from. The idea being you can setup different local
working dirs for different tempest envs to test against several
different clouds.

The basic idea for this new workflow after installing tempest is
something like:

 1. mkdir tempest-newcloud
 2. cd tempest-newcloud
 3. tempest init
 4. edit local config file
 5. tempest run

The next step after this is to start working on the 'tempest run'
command. (which will include the hooks for the tempest plugin
interface) But, until that is added a test runner can be called
directly inside a local tempest working directory.

Partially Implements bp tempest-cli-improvements

Change-Id: I572267e61ba8ca86f92299e174864a7a89597207