<html><body><p>Hi Daniel & Gema,<br><br>I am all for minimizing the barrier of entry for end users. My main concern is the maintenance and trouble shooting support of the script for ALL cloud deployments. I support the idea as long as this has been considered and addressed in advance.<br><br>Catherine <br><font size="2" color="#800080">----- Forwarded by Catherine Cuong Diep/San Jose/IBM</font><font size="2" color="#800080"> on 08/19/2016 09:34 AM</font><font size="2" color="#800080"> -----</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Gema Gomez <gema.gomez-solano@linaro.org></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">defcore-committee@lists.openstack.org</font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">08/19/2016 03:45 AM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [OpenStack-DefCore] Recommended tempest.conf settings</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><tt>Hi Daniel & Catherine,<br><br>I think we should definitely write the documentation, I will be doing<br>that and sending a patch for review for it.<br><br>Then Daniel and I can also work on the integration of this script, make<br>sure script and documentation are in sync and have a commit for that so<br>people can try it and Catherine can determine whether it is going to be<br>helpful and release some of the time she spends helping people configure<br>tempest or not.<br><br>The one problem I see is the maintenance overhead of this script, but we<br>have that overhead now distributed amongst all the people running the<br>tests and it ends up increasing the barrier of entry to running the<br>tests for end users.<br><br>If RefStack is not the right place for it we could also have it as a<br>helper script in the Defcore repo, so I think this work is valuable if<br>we implement it/document it the right way.<br><br>Thanks,<br>Gema<br><br>On 19/08/16 07:40, Daniel Mellado wrote:<br>> Hi Catherine,<br>> <br>> The script should work for any cloud, as long as it gets the credentials<br>> for it and an identity endpoint. It's not tied to any specific distribution.<br>> <br>> As Chris was pointing that one of the goals was to have that into<br>> RefStack (quoting)<br>> <br>>>>> One of our stated goals is to only need to provide an endpoint and<br>>>>> credentials to<br>>>>> do interoperability testing, but the current state of Tempest and<br>>> OpenStack<br>>>>> make that a goal we’ll reach further down the line. Optimistically next<br>>>>> year, but<br>>>>> discoverability and configuration is an open problem.<br>>>>><br>> <br>> I was thinking about having it integrated or at least used as a base of<br>> what it could do. If you have any concerns we could make it optional and<br>> as Gema has also volunteered to do testing I think it'd be a nice<br>> addition. Please get back to me if you have any doubt or comment ;)<br>> <br>> Thanks!<br>> <br>> Daniel<br>> <br>> El 18/08/16 a las 22:15, Catherine Cuong Diep escribió:<br>>> Hi Gema and Daniel,<br>>><br>>> I think a recommendation document is preferred. If it is to integrate in<br>>> RefStack, we need to ensure that it would work for all variation of<br>>> cloud deployments. BTW, slide 15 thru 17 in [1] documented the common<br>>> settings recommend for RefStack/DefCore test.<br>>><br>>> [1]<br>>> </tt><tt><a href="https://docs.google.com/presentation/d/1CoegiPzVp8G4VLdrOYTX9ZI_E-PTRx0gWVpuF9ElKRU/edit#slide=id.g85e96ad23_3_27">https://docs.google.com/presentation/d/1CoegiPzVp8G4VLdrOYTX9ZI_E-PTRx0gWVpuF9ElKRU/edit#slide=id.g85e96ad23_3_27</a></tt><tt><br>>><br>>> Catherine<br>>> ----- Forwarded by Catherine Cuong Diep/San Jose/IBMon 08/18/2016 11:08<br>>> AM-----<br>>><br>>> From: Gema Gomez <gema.gomez-solano@linaro.org><br>>> To: defcore-committee@lists.openstack.org<br>>> Date: 08/18/2016 01:17 AM<br>>> Subject: Re: [OpenStack-DefCore] Recommended tempest.conf settings<br>>><br>>> ------------------------------------------------------------------------<br>>><br>>><br>>><br>>> Daniel,<br>>><br>>> integrating this in RefStack would be awesome :D If you want to do the<br>>> integration, then we can review and make sure we are not relying too<br>>> much on capabilities that are not in the guidelines and I can help<br>>> organise/do testing from the end user perspective, we can coordinate<br>>> with a few other folks also for testing. Then we document how to use it<br>>> in the instructions of the client. It would be really handy for users, I<br>>> think.<br>>><br>>> Catherine, any thoughts? would this work in your view?<br>>><br>>> Cheers,<br>>> Gema<br>>><br>>><br>>> On 18/08/16 08:53, Daniel Mellado wrote:<br>>>> Hi Gema,<br>>>><br>>>> Thanks for pointing this out, I think it's quite helpful and would deff<br>>>> come in handy when configuring and running as it looks like everybody<br>>>> has been hitting the same wall.<br>>>><br>>>> Chris, what you're speaking about surely resembles what our<br>>>> configure_tempest script does in our tempest fork<br>>>><br>>>><br>>> </tt><tt><a href="https://github.com/redhat-openstack/tempest/blob/master/tools/config_tempest.py">https://github.com/redhat-openstack/tempest/blob/master/tools/config_tempest.py</a></tt><tt><br>>>><br>>>> it configures tempest using api discovery, and for sure can be tweaked<br>>>> to add any necessary refstack settings. I'll be going to put this into<br>>>> its own repo but I was wondering if you'd be interested about<br>>>> integrating it with refstack so it could handle tempest configuration,<br>>>> if that's the case I could totally handle that or help with it.<br>>>><br>>>> Thanks!<br>>>><br>>>> Daniel<br>>>><br>>>> El 17/08/16 a las 20:44, Chris Hoge escribió:<br>>>>> It’s more of a guide on how to configure Tempest for RefStack Client<br>>> runs.<br>>>>><br>>>>> One of our stated goals is to only need to provide an endpoint and<br>>>>> credentials to<br>>>>> do interoperability testing, but the current state of Tempest and<br>>> OpenStack<br>>>>> make that a goal we’ll reach further down the line. Optimistically next<br>>>>> year, but<br>>>>> discoverability and configuration is an open problem.<br>>>>><br>>>>> Chris<br>>>>><br>>>>>> On Aug 17, 2016, at 10:10 AM, Tim Bell <Tim.Bell@cern.ch<br>>>>>> <</tt><tt><a href="mailto:Tim.Bell@cern.ch">mailto:Tim.Bell@cern.ch</a></tt><tt>>> wrote:<br>>>>>><br>>>>>> <br>>>>>> Great to see these resources as we are using multiple OpenStack clouds.<br>>>>>> <br>>>>>> How does this differ from refstack?<br>>>>>> <br>>>>>> Tim<br>>>>>> <br>>>>>> *From: *Egle Sigler <ushnishtha@hotmail.com<br>>>>>> <</tt><tt><a href="mailto:ushnishtha@hotmail.com">mailto:ushnishtha@hotmail.com</a></tt><tt>>><br>>>>>> *Date: *Wednesday 17 August 2016 at 19:03<br>>>>>> *To: *Gema Gomez <gema.gomez-solano@linaro.org<br>>>>>> <</tt><tt><a href="mailto:gema.gomez-solano@linaro.org">mailto:gema.gomez-solano@linaro.org</a></tt><tt>>>,<br>>>>>> "defcore-committee@lists.openstack.org<br>>>>>> <</tt><tt><a href="mailto:defcore-committee@lists.openstack.org">mailto:defcore-committee@lists.openstack.org</a></tt><tt>>"<br>>>>>> <defcore-committee@lists.openstack.org<br>>>>>> <</tt><tt><a href="mailto:defcore-committee@lists.openstack.org">mailto:defcore-committee@lists.openstack.org</a></tt><tt>>><br>>>>>> *Subject: *Re: [OpenStack-DefCore] Recommended tempest.conf settings<br>>>>>> <br>>>>>>> Thank you for starting this Gema, I think it will really help a lot<br>>>>>>> of people getting started once we have this.<br>>>>>>> <br>>>>>>> -Egle<br>>>>>>><br>>>>>>> <br>>>>>>><br>>>>>>><br>>> ------------------------------------------------------------------------<br>>>>>>> *From:* Gema Gomez <gema.gomez-solano@linaro.org<br>>>>>>> <</tt><tt><a href="mailto:gema.gomez-solano@linaro.org">mailto:gema.gomez-solano@linaro.org</a></tt><tt>>><br>>>>>>> *Sent:* Wednesday, August 17, 2016 12:01 PM<br>>>>>>> *To:* defcore-committee@lists.openstack.org<br>>>>>>> <</tt><tt><a href="mailto:defcore-committee@lists.openstack.org">mailto:defcore-committee@lists.openstack.org</a></tt><tt>><br>>>>>>> *Subject:* Re: [OpenStack-DefCore] Recommended tempest.conf settings<br>>>>>>> <br>>>>>>> Hi all,<br>>>>>>><br>>>>>>> we are going to be writing a recommendation document on how to<br>>> configure<br>>>>>>> tempest to be able to run the interop tests. The idea is to lower the<br>>>>>>> entry barrier for end users to be able to run the interop tests.<br>>>>>>><br>>>>>>> We have created an etherpad where some notes have started to appear:<br>>>>>>> </tt><tt><a href="https://etherpad.openstack.org/p/defcore-tempest-configuration">https://etherpad.openstack.org/p/defcore-tempest-configuration</a></tt><tt><br>>>>>>><br>>>>>>> If you could please share your notes there I will run through some<br>>> tests<br>>>>>>> to validate that the options and sane and write a document explaining<br>>>>>>> how to configure tempest for newbies. Share what you have, I will make<br>>>>>>> sense of it all and unify it.<br>>>>>>><br>>>>>>> Thanks in advance!<br>>>>>>> Gema<br>>>>>>><br>>>>>>> On 16/08/16 18:37, Gema Gomez wrote:<br>>>>>>><br>>>>>>><br>>>>>>>> Hi,<br>>>>>>>><br>>>>>>>> I remember we discussed during the midcycle about the recommended<br>>>>>>>> tempest.conf and hogepoge and catherine had very solid definite<br>>>>>>>> recommendations for it.<br>>>>>>>><br>>>>>>>> If you could share them I'd like to put some document together for our<br>>>>>>>> repo or for RefStack, wherever it belongs, with the recommendations.<br>>>>>>>><br>>>>>>>> Cheers,<br>>>>>>>> Gema<br>>>>>>><br>>>>>>><br>>>>>>> --<br>>>>>>> Gema Gomez-Solano<br>>>>>>> Tech Lead, SDI<br>>>>>>> Linaro Ltd<br>>>>>>> IRC: gema@#linaro on irc.freenode.net <</tt><tt><a href="http://irc.freenode.net">http://irc.freenode.net</a></tt><tt>><br>>>>>>><br>>>>>>> _______________________________________________<br>>>>>>> Defcore-committee mailing list<br>>>>>>> Defcore-committee@lists.openstack.org<br>>>>>>> <</tt><tt><a href="mailto:Defcore-committee@lists.openstack.org">mailto:Defcore-committee@lists.openstack.org</a></tt><tt>><br>>>>>>> </tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a></tt><tt><br>>>>>> _______________________________________________<br>>>>>> Defcore-committee mailing list<br>>>>>> Defcore-committee@lists.openstack.org<br>>>>>> <</tt><tt><a href="mailto:Defcore-committee@lists.openstack.org">mailto:Defcore-committee@lists.openstack.org</a></tt><tt>><br>>>>>> </tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a></tt><tt><br>>>>><br>>>>><br>>>>><br>>>>> _______________________________________________<br>>>>> Defcore-committee mailing list<br>>>>> Defcore-committee@lists.openstack.org<br>>>>> </tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a></tt><tt><br>>>>><br>>>><br>>>> _______________________________________________<br>>>> Defcore-committee mailing list<br>>>> Defcore-committee@lists.openstack.org<br>>>> </tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a></tt><tt><br>>>><br>>><br>>> -- <br>>> Gema Gomez-Solano<br>>> Tech Lead, SDI<br>>> Linaro Ltd<br>>> IRC: gema@#linaro on irc.freenode.net<br>>><br>>> _______________________________________________<br>>> Defcore-committee mailing list<br>>> Defcore-committee@lists.openstack.org<br>>> </tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a></tt><tt><br>>><br>>><br>>><br>>><br>>><br>>> _______________________________________________<br>>> Defcore-committee mailing list<br>>> Defcore-committee@lists.openstack.org<br>>> </tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a></tt><tt><br>>><br>> <br>> _______________________________________________<br>> Defcore-committee mailing list<br>> Defcore-committee@lists.openstack.org<br>> </tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a></tt><tt><br>> <br><br>-- <br>Gema Gomez-Solano<br>Tech Lead, SDI<br>Linaro Ltd<br>IRC: gema@#linaro on irc.freenode.net<br><br>_______________________________________________<br>Defcore-committee mailing list<br>Defcore-committee@lists.openstack.org<br></tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a></tt><tt><br><br></tt><br><BR>
</body></html>