Open Stack

On 06/13/2013 10:59 AM, James Michel wrote:
> On 13/06/13 14:50, Jaroslav Henner wrote:
>> Hi,
>>
>> We wish to create some tool for automated preparation of stack for full
>> tempest run. We need it to be able to work with deployment that has been
>> prepared by Packstack [1].
>>
>> Packstack can give as an output some "answer file", which is actually an
>> ini file. We can parse that file, take some other values as input, for
>> example images locations, ... and create a tempest.conf accordingly.
>
> Actually we were looking at some smart way of configuring tempest.conf
> after having deployed openstack. Is this more-or-less what you had in mind?
>
>>
>> The questions now are:
>>   * Should this be a part of Tempest?
>>   * Should this be a separate project?
>>   * Should this be a part of the Packstack?
>>   * What about other deploying tools - should that tool have several
>> frond-ends?
>>   * Does anybody have something already?
>>
>> Any comments?
>>
>> [1] https://wiki.openstack.org/wiki/Packstack
>>
>> PS: As Attila Fazekas pointed, most things we can find dynamically from
>> the keystone/nova. True, but I don't quite like the idea to ssh to nova
>> host to get nova SQL password and tricks like that.
>>
>> Jaroslav Henner

So I really think that these tempest configuration generators should be 
back in the install tools themselves. We do this in devstack today, and 
the installer should just configure tempest.conf as it's output.

It's not clear that an intermediary tool is really useful, because it 
means that when your installer enables a new feature, you have to fix 
the installer -> question file, then fix question engine -> tempest.

	-Sean

-- 
Sean Dague
http://dague.net