Open Stack

On 04/08/2015 02:58 PM, David Kranz wrote:
> On 04/08/2015 02:36 PM, Matthew Treinish wrote:
>> On Wed, Apr 08, 2015 at 01:08:03PM -0400, David Kranz wrote:
>>> Since tempest no longer uses the official clients as a literal code
>>> dependency, except for the cli tests which are being removed, the clients
>>> have been dropping from requirements.txt. But when debugging issues
>>> uncovered by tempest, or when debugging tempest itself, it is useful to use
>>> the cli to check various things. I think it would be a good service to users
>>> of tempest to include the client libraries when tempest is installed on a
>>> machine. Is there a reason to not do this?
>> i> 
>>
>> Umm, so that is not what requirements.txt is for, we should only put what is
>> required to run the tempest in the requirements file. It's a package dependencies
>> list, not a list of everything you find useful for developing tempest code.
> I was more thinking of users of tempest than developers of tempest,
> though it is useful to both.
> But we can certainly say that this is an issue for those who provide
> tempest to users.

I'm in agreement with Matt here. Tempest requirements should be what
Tempest actually requires.

Installing the CLI is pretty easy, it's package installed in any Linux
distro. apt-get, yum, or even pip install and you are off and running.

I don't think having Tempest side effect dragging in the CLI tools is
useful. Those should instead be something people install themselves.

	-Sean

-- 
Sean Dague
http://dague.net