Open Stack

On 03/26/2013 09:27 PM, Yaniv Kaul wrote:
> Without the ability to configure OpenStack,  it's not going to fly.  Configure means:
> 0. Installation scenarios (installation of different components on different hosts)
> 1. Ini files manipulation (nova.conf and friends)  and restarting services
> 2. JSON files manipulation (policy files)
> 3. Configuration via the API (and/or nova-manage)
>
> The above are basic blocks to any true scenario (and end to end) testing.
> Y.

I disagree. It's important that we hold the line that Tempest is not an 
installer, tempest is a validator.

Devstack is an installer. Packstack is an installer. How you get working 
code should be arbitrary and outside the scope of tempest.

A tempest scenario could always run a set of pre-checks to figure out if 
it's possible for it to run. If that's impossible to tell from our admin 
apis on services, we should enhance the components (nova, quantum, etc) 
to give us interfaces that let us get enough info to figure out if the 
scenario is runnable.

	-Sean

-- 
Sean Dague
http://dague.net