<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">HI,<div class=""><br class=""></div><div class="">We at midokura have this automated as well, let me explain our flow so may be it useful for you guys:</div><div class=""><br class=""></div><div class="">In my opinion tempest autoconf tool should be extremely bounded to rc files where the credentials are, plus the url of the keystone, those are the minimum requiremenets for such tool, after that it is just straight forward to feed it with the rest of the details. </div><div class=""><br class=""></div><div class="">Our current approach is that we deploy our cloud with ansible and we produce a tempest.con with that deployment, then I fetch this file that is sitting in the controller node, and move it wherever is my tempest host and through some python script and the help of simpleconfigparser I finalise to set it up for our use.</div><div class=""><br class=""></div><div class="">best,</div><div class="">Albert</div><div class=""> </div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 26 Jan 2015, at 15:39, Timur Nurlygayanov <<a href="mailto:tnurlygayanov@mirantis.com" class="">tnurlygayanov@mirantis.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">Hi,<br class=""><br class=""><b class="">Yaroslav</b>,<span id="result_box" class="" lang="en"><span class=""> thank you for</span> <span class="">raising the question,</span></span> I realy like this feature, I discussed this script with several people during the OpenStack summit in Paris and heard many the same things - we need to have something like this to execute tempest tests automatically for validation of different production and test OpenStack clouds - it is real pain to create our own separate scripts for each project / team which will configure Tempest for some specific configurations / installations, because tempest configuration file can be changed and we will need to update our scripts.<br class=""><br class=""></div><div class="">We need to discuss, first of all, what we need to change in this script before this script will be merged.<br class=""></div><div class="">As I can see, the spec description [1] not fully meet the current implementation [2] and the spec looks really general - probably we can describe separate 'simple' spec for this script and just abandon the current spec or update the spec to sync spec and this script?<br class=""><br class=""></div><div class=""><b class="">David</b>, we found many issues with the current version of script, many tempest tests failed for our custom OpenStack configurations (for example, with and without Swift or Ceph) and we have our own scripts which already can solve the problem. Can we join you and edit the patch together? (or we can describe our ideas in the comments for the patch). <br class=""><br class=""></div><div class="">Also, looks like we need review from Tempest core team - they can write more valuable comments and suggest some cool ideas for the implementation.<br class=""><br class="">[1] <a href="https://review.openstack.org/#/c/94473" class="">https://review.openstack.org/#/c/94473</a><br class="">[2] <a href="https://review.openstack.org/#/c/133245" class="">https://review.openstack.org/#/c/133245<br class=""></a><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Fri, Jan 23, 2015 at 7:12 PM, Yaroslav Lobankov <span dir="ltr" class=""><<a href="mailto:ylobankov@mirantis.com" target="_blank" class="">ylobankov@mirantis.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">Hello everyone,<div class=""><br class=""></div><div class="">I would like to discuss the following patch [1] for Tempest. I think that such feature </div><div class="">as auto-configuration of Tempest would be very useful for many engineers and users. </div><div class="">I have recently tried to use the script from [1]. I rebased the patch on master and ran the script. </div><div class="">The script was finished without any errors and the tempest.conf was generated! Of course, </div><div class="">this patch needs a lot of work, but the idea looks very cool! </div><div class=""><br class=""></div><div class="">Also I would like to thank David Kranz for his working on initial version of the script.</div><div class=""><br class=""></div><div class="">Any thoughts?</div><div class=""><br class=""></div><div class="">[1] <a href="https://review.openstack.org/#/c/133245" target="_blank" class="">https://review.openstack.org/#/c/133245</a></div><div class=""><br class=""></div><div class="">Regards,</div><div class="">Yaroslav Lobankov.</div></div>
<br class="">__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class=""></blockquote></div><br class=""><br clear="all" class=""><br class="">-- <br class=""><div class="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><font color="#888888" class=""><br class=""></font><div style="font-family:arial;font-size:small" class="">Timur,</div><div style="font-family:arial;font-size:small" class="">Senior QA Engineer</div><div style="font-family:arial;font-size:small" class="">OpenStack Projects</div><div style="font-family:arial;font-size:small" class="">Mirantis Inc</div></div></div></div></div></div></div>
</div>
__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></body></html>