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