Open Stack

Hi Catherine,

The script should work for any cloud, as long as it gets the credentials
for it and an identity endpoint. It's not tied to any specific distribution.

As Chris was pointing that one of the goals was to have that into
RefStack (quoting)

>>> One of our stated goals is to only need to provide an endpoint and
>>> credentials to
>>> do interoperability testing, but the current state of Tempest and
> OpenStack
>>> make that a goal we’ll reach further down the line. Optimistically next
>>> year, but
>>> discoverability and configuration is an open problem.
>>>

I was thinking about having it integrated or at least used as a base of
what it could do. If you have any concerns we could make it optional and
as Gema has also volunteered to do testing I think it'd be a nice
addition. Please get back to me if you have any doubt or comment ;)

Thanks!

Daniel

El 18/08/16 a las 22:15, Catherine Cuong Diep escribió:
> Hi Gema and Daniel,
> 
> I think a recommendation document is preferred. If it is to integrate in
> RefStack, we need to ensure that it would work for all variation of
> cloud deployments. BTW, slide 15 thru 17 in [1] documented the common
> settings recommend for RefStack/DefCore test.
> 
> [1]
> https://docs.google.com/presentation/d/1CoegiPzVp8G4VLdrOYTX9ZI_E-PTRx0gWVpuF9ElKRU/edit#slide=id.g85e96ad23_3_27
> 
> Catherine
> ----- Forwarded by Catherine Cuong Diep/San Jose/IBMon 08/18/2016 11:08
> AM-----
> 
> From: Gema Gomez <gema.gomez-solano at linaro.org>
> To: defcore-committee at lists.openstack.org
> Date: 08/18/2016 01:17 AM
> Subject: Re: [OpenStack-DefCore] Recommended tempest.conf settings
> 
> ------------------------------------------------------------------------
> 
> 
> 
> Daniel,
> 
> integrating this in RefStack would be awesome :D If you want to do the
> integration, then we can review and make sure we are not relying too
> much on capabilities that are not in the guidelines and I can help
> organise/do testing from the end user perspective, we can coordinate
> with a few other folks also for testing. Then we document how to use it
> in the instructions of the client. It would be really handy for users, I
> think.
> 
> Catherine, any thoughts? would this work in your view?
> 
> Cheers,
> Gema
> 
> 
> On 18/08/16 08:53, Daniel Mellado wrote:
>> Hi Gema,
>>
>> Thanks for pointing this out, I think it's quite helpful and would deff
>> come in handy when configuring and running as it looks like everybody
>> has been hitting the same wall.
>>
>> Chris, what you're speaking about surely resembles what our
>> configure_tempest script does in our tempest fork
>>
>>
> https://github.com/redhat-openstack/tempest/blob/master/tools/config_tempest.py
>>
>> it configures tempest using api discovery, and for sure can be tweaked
>> to add any necessary refstack settings. I'll be going to put this into
>> its own repo but I was wondering if you'd be interested about
>> integrating it with refstack so it could handle tempest configuration,
>> if that's the case I could totally handle that or help with it.
>>
>> Thanks!
>>
>> Daniel
>>
>> El 17/08/16 a las 20:44, Chris Hoge escribió:
>>> It’s more of a guide on how to configure Tempest for RefStack Client
> runs.
>>>
>>> One of our stated goals is to only need to provide an endpoint and
>>> credentials to
>>> do interoperability testing, but the current state of Tempest and
> OpenStack
>>> make that a goal we’ll reach further down the line. Optimistically next
>>> year, but
>>> discoverability and configuration is an open problem.
>>>
>>> Chris
>>>
>>>> On Aug 17, 2016, at 10:10 AM, Tim Bell <Tim.Bell at cern.ch
>>>> <mailto:Tim.Bell at cern.ch>> wrote:
>>>>
>>>>  
>>>> Great to see these resources as we are using multiple OpenStack clouds.
>>>>  
>>>> How does this differ from refstack?
>>>>  
>>>> Tim
>>>>  
>>>> *From: *Egle Sigler <ushnishtha at hotmail.com
>>>> <mailto:ushnishtha at hotmail.com>>
>>>> *Date: *Wednesday 17 August 2016 at 19:03
>>>> *To: *Gema Gomez <gema.gomez-solano at linaro.org
>>>> <mailto:gema.gomez-solano at linaro.org>>,
>>>> "defcore-committee at lists.openstack.org
>>>> <mailto:defcore-committee at lists.openstack.org>"
>>>> <defcore-committee at lists.openstack.org
>>>> <mailto:defcore-committee at lists.openstack.org>>
>>>> *Subject: *Re: [OpenStack-DefCore] Recommended tempest.conf settings
>>>>  
>>>>> Thank you for starting this Gema, I think it will really help a lot
>>>>> of people getting started once we have this.
>>>>>  
>>>>> -Egle
>>>>>
>>>>>  
>>>>>
>>>>>
> ------------------------------------------------------------------------
>>>>> *From:* Gema Gomez <gema.gomez-solano at linaro.org
>>>>> <mailto:gema.gomez-solano at linaro.org>>
>>>>> *Sent:* Wednesday, August 17, 2016 12:01 PM
>>>>> *To:* defcore-committee at lists.openstack.org
>>>>> <mailto:defcore-committee at lists.openstack.org>
>>>>> *Subject:* Re: [OpenStack-DefCore] Recommended tempest.conf settings
>>>>>  
>>>>> Hi all,
>>>>>
>>>>> we are going to be writing a recommendation document on how to
> configure
>>>>> tempest to be able to run the interop tests. The idea is to lower the
>>>>> entry barrier for end users to be able to run the interop tests.
>>>>>
>>>>> We have created an etherpad where some notes have started to appear:
>>>>> https://etherpad.openstack.org/p/defcore-tempest-configuration
>>>>>
>>>>> If you could please share your notes there I will run through some
> tests
>>>>> to validate that the options and sane and write a document explaining
>>>>> how to configure tempest for newbies. Share what you have, I will make
>>>>> sense of it all and unify it.
>>>>>
>>>>> Thanks in advance!
>>>>> Gema
>>>>>
>>>>> On 16/08/16 18:37, Gema Gomez wrote:
>>>>>
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I remember we discussed during the midcycle about the recommended
>>>>>> tempest.conf and hogepoge and catherine had very solid definite
>>>>>> recommendations for it.
>>>>>>
>>>>>> If you could share them I'd like to put some document together for our
>>>>>> repo or for RefStack, wherever it belongs, with the recommendations.
>>>>>>
>>>>>> Cheers,
>>>>>> Gema
>>>>>
>>>>>
>>>>> --
>>>>> Gema Gomez-Solano
>>>>> Tech Lead, SDI
>>>>> Linaro Ltd
>>>>> IRC: gema@#linaro on irc.freenode.net <http://irc.freenode.net>
>>>>>
>>>>> _______________________________________________
>>>>> Defcore-committee mailing list
>>>>> Defcore-committee at lists.openstack.org
>>>>> <mailto:Defcore-committee at lists.openstack.org>
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
>>>> _______________________________________________
>>>> Defcore-committee mailing list
>>>> Defcore-committee at lists.openstack.org
>>>> <mailto:Defcore-committee at lists.openstack.org>
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
>>>
>>>
>>>
>>> _______________________________________________
>>> Defcore-committee mailing list
>>> Defcore-committee at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
>>>
>>
>> _______________________________________________
>> Defcore-committee mailing list
>> Defcore-committee at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
>>
> 
> -- 
> Gema Gomez-Solano
> Tech Lead, SDI
> Linaro Ltd
> IRC: gema@#linaro on irc.freenode.net
> 
> _______________________________________________
> Defcore-committee mailing list
> Defcore-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
> 
> 
> 
> 
> 
> _______________________________________________
> Defcore-committee mailing list
> Defcore-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
>