<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas","serif";
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'>+1 for decoupling Tempest from devstack<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'>Openstack deployment tool is TripleO / Heat –so it would be good to have an Heat template to deploy and configure Tempest<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'>andrea<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='margin-left:36.0pt'><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext'>From:</span></b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:windowtext'> David Kranz [mailto:dkranz@redhat.com] <br><b>Sent:</b> 12 February 2014 23:23<br><b>To:</b> OpenStack Development Mailing List (not for usage questions)<br><b>Subject:</b> Re: [openstack-dev] [qa][tempest][rally] Rally & Tempest integration: tempest.conf autogeneration<o:p></o:p></span></p></div></div><p class=MsoNormal style='margin-left:36.0pt'><o:p> </o:p></p><div><p class=MsoNormal style='margin-left:36.0pt'>On 02/12/2014 05:55 PM, Sean Dague wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre style='margin-left:36.0pt'>On 02/12/2014 05:08 PM, Boris Pavlovic wrote:<o:p></o:p></pre><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre style='margin-left:36.0pt'>Hi all, <o:p></o:p></pre><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'>It goes without saying words that actually tempest[1] is only one public<o:p></o:p></pre><pre style='margin-left:36.0pt'>known tool that could fully verify deployments and ensure dthat they work.<o:p></o:p></pre><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'>In Rally[2] we would like to use it as a cloud verifier (before<o:p></o:p></pre><pre style='margin-left:36.0pt'>benchmarking it is actually very useful;) to ensure that cloud work). We<o:p></o:p></pre><pre style='margin-left:36.0pt'>are going to build on top of tempest pretty interface and aliases &<o:p></o:p></pre><pre style='margin-left:36.0pt'>support of working with different clouds. E.g.: <o:p></o:p></pre><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'>rally use deployment <uuid> # use some deployment that is registered in<o:p></o:p></pre><pre style='margin-left:36.0pt'>Rally<o:p></o:p></pre><pre style='margin-left:36.0pt'>rally verify nova # Run only nova tests against `in-use` deployment <o:p></o:p></pre><pre style='margin-left:36.0pt'>rally verify small/big/full # set of tests<o:p></o:p></pre><pre style='margin-left:36.0pt'>rally verify list # List all verification results for this deployment<o:p></o:p></pre><pre style='margin-left:36.0pt'>rally verify show <id> # Show detailed information<o:p></o:p></pre><pre style='margin-left:36.0pt'># Okay we found that something failed, fixed it in cloud, restart<o:p></o:p></pre><pre style='margin-left:36.0pt'>service and we would like you to run only failed tests<o:p></o:p></pre><pre style='margin-left:36.0pt'>rally verify latest_failed # do it in one simple command<o:p></o:p></pre><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'>These commands should be very smart, generate proper tempest.conf for<o:p></o:p></pre><pre style='margin-left:36.0pt'>specific cloud, prepare cloud for tempest testing, store somewhere<o:p></o:p></pre><pre style='margin-left:36.0pt'>results and so on and so on. So at the end we will have very simple way<o:p></o:p></pre><pre style='margin-left:36.0pt'>to work with tempest. <o:p></o:p></pre><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'>We added first patch that adds base functionality to Rally [3]: <o:p></o:p></pre><pre style='margin-left:36.0pt'><a href="https://review.openstack.org/#/c/70131/">https://review.openstack.org/#/c/70131/</a><o:p></o:p></pre><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'>At QA meeting I discussed it with David Kranz, as a result we agree that <o:p></o:p></pre><pre style='margin-left:36.0pt'>part of this functionality (tempest.conf generator & cloud prepare),<o:p></o:p></pre><pre style='margin-left:36.0pt'>should be implemented inside tempest.<o:p></o:p></pre><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'>Current situation is not super cool because, there are at least 4<o:p></o:p></pre><pre style='margin-left:36.0pt'>projects where we are generating in different way tempest.conf: <o:p></o:p></pre><pre style='margin-left:36.0pt'>1) DevStack<o:p></o:p></pre><pre style='margin-left:36.0pt'>2) Fuel CI<o:p></o:p></pre><pre style='margin-left:36.0pt'>3) Rally<o:p></o:p></pre><pre style='margin-left:36.0pt'>4) Tempest (currently broken)<o:p></o:p></pre><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'>To put it in a nutshell, it's clear that we should make only 1<o:p></o:p></pre><pre style='margin-left:36.0pt'>tempest.conf generator [4], that will cover all cases, and will be<o:p></o:p></pre><pre style='margin-left:36.0pt'>enough simple to be used in all other projects. <o:p></o:p></pre></blockquote><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'>So in the past the issue was we could never get anyone to agree on one.<o:p></o:p></pre><pre style='margin-left:36.0pt'>For instance, devstack makes some really fine grained decisions, and the<o:p></o:p></pre><pre style='margin-left:36.0pt'>RDO team showed up with a very different answer file approach, which<o:p></o:p></pre><pre style='margin-left:36.0pt'>wouldn't work for devstack (it had the wrong level of knob changing).<o:p></o:p></pre><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'>And if the end of the day you replace build a tempest config generator,<o:p></o:p></pre><pre style='margin-left:36.0pt'>which takes 200 options, I'm not entirely sure how that was better than<o:p></o:p></pre><pre style='margin-left:36.0pt'>just setting those 200 options directly.<o:p></o:p></pre><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'>So while happy to consider options here, realize that there is a reason<o:p></o:p></pre><pre style='margin-left:36.0pt'>this has been punted before.<o:p></o:p></pre><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'> -Sean<o:p></o:p></pre></blockquote><p class=MsoNormal style='margin-left:36.0pt'>I have thought about this and think we can do better. I will present a spec when I get a chance if no one else does. I would leave devstack out<br>of it, at least for now. In general it would be good to decouple tempest from devstack a little more, especially as it gains wider use in rally, refstack, etc. For example, there are default paths and stuff in tempest.conf.sample that refer to files that are only put there by devstack.<br><br> -David<br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre style='margin-left:36.0pt'><o:p> </o:p></pre><pre style='margin-left:36.0pt'><o:p> </o:p></pre><p class=MsoNormal style='margin-left:36.0pt'><br><br><br><o:p></o:p></p><pre style='margin-left:36.0pt'>_______________________________________________<o:p></o:p></pre><pre style='margin-left:36.0pt'>OpenStack-dev mailing list<o:p></o:p></pre><pre style='margin-left:36.0pt'><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><o:p></o:p></pre><pre style='margin-left:36.0pt'><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></pre></blockquote><p class=MsoNormal style='margin-left:36.0pt'><o:p> </o:p></p></div></body></html>