<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=gb2312">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
        {font-family:SimSun;
        panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"\@SimSun";
        panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:SimSun;}
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;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0cm;
        mso-margin-bottom-alt:auto;
        margin-left:0cm;
        font-size:12.0pt;
        font-family:SimSun;}
tt
        {mso-style-priority:99;
        font-family:SimSun;}
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 lang="EN-CA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I am going to share something that might be off the topic a bit.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Yesterday, I was pulled to the #openstack-infra channel to participant a discussion, which is related to the atomic image download in Magnum. It looks the infra
 team is not satisfied with the large image size. In particular, they need to double the timeout to accommodate the job [1] [2], which made them unhappy. Is there a way to reduce the image size? Or even better, is it possible to build the image locally instead
 of downloading it?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[1]
<a href="https://review.openstack.org/#/c/242742/">https://review.openstack.org/#/c/242742/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[2]
<a href="https://review.openstack.org/#/c/244847/">https://review.openstack.org/#/c/244847/</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hongbin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Kai Qiang Wu [mailto:wkqwu@cn.ibm.com]
<br>
<b>Sent:</b> November-13-15 12:33 AM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing ongate.<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Right now, we seems can not reduce devstack runtime. ANd @Ton, yes, download image time seems OK in jenkins job, it found about 4~5 mins<br>
<br>
But bay-creation time is interesting topic, it seems something related with heat or VM setup time consumption. But needs some investigation.<br>
<br>
<br>
<br>
Thanks<br>
<br>
Best Wishes,<br>
--------------------------------------------------------------------------------<br>
Kai Qiang Wu (<span lang="ZH-CN">Î⿪ǿ</span> Kennan<span lang="ZH-CN">£©</span><br>
IBM China System and Technology Lab, Beijing<br>
<br>
E-mail: <a href="mailto:wkqwu@cn.ibm.com">wkqwu@cn.ibm.com</a><br>
Tel: 86-10-82451647<br>
Address: Building 28(Ring Building), ZhongGuanCun Software Park, <br>
No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193<br>
--------------------------------------------------------------------------------<br>
Follow your heart. You are miracle! <br>
<br>
<img border="0" width="16" height="16" id="_x0000_i1041" src="cid:image001.gif@01D11DFF.D7C78C20" alt="Inactive hide details for "Ton Ngo" ---13/11/2015 01:13:47 pm---Thanks Eli for the analysis.  I notice that the time to downloa"><span style="color:#424282">"Ton
 Ngo" ---13/11/2015 01:13:47 pm---Thanks Eli for the analysis. I notice that the time to download the image is only around 1:15 mins</span><br>
<br>
<span style="font-size:10.0pt;color:#5F5F5F">From: </span><span style="font-size:10.0pt">"Ton Ngo" <<a href="mailto:ton@us.ibm.com">ton@us.ibm.com</a>></span><br>
<span style="font-size:10.0pt;color:#5F5F5F">To: </span><span style="font-size:10.0pt">"OpenStack Development Mailing List \(not for usage questions\)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>></span><br>
<span style="font-size:10.0pt;color:#5F5F5F">Date: </span><span style="font-size:10.0pt">13/11/2015 01:13 pm</span><br>
<span style="font-size:10.0pt;color:#5F5F5F">Subject: </span><span style="font-size:10.0pt">Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing on gate.</span><o:p></o:p></p>
<div class="MsoNormal">
<hr size="2" width="100%" noshade="" style="color:#8091A5" align="left">
</div>
<p class="MsoNormal"><br>
<br>
<br>
<span style="font-size:13.5pt">Thanks Eli for the analysis. I notice that the time to download the image is only around 1:15 mins out of some 21 mins to set up devstack. So it seems trying to reduce the size of the image won't make a significant improvement
 in the devstack time. I wonder how the image size affects the VM creation time for the cluster. If we can look at the Heat event stream, we might get an idea.
<br>
Ton,<br>
<br>
<br>
</span><img border="0" width="16" height="16" id="_x0000_i1043" src="cid:image001.gif@01D11DFF.D7C78C20" alt="Inactive hide details for Egor Guz ---11/12/2015 05:25:15 PM---Eli, First of all I would like to say thank you for your effort "><span style="font-size:13.5pt;color:#424282">Egor
 Guz ---11/12/2015 05:25:15 PM---Eli, First of all I would like to say thank you for your effort (I never seen so many path sets ;)),</span><span style="font-size:13.5pt"><br>
</span><span style="color:#5F5F5F"><br>
From: </span>Egor Guz <<a href="mailto:EGuz@walmartlabs.com">EGuz@walmartlabs.com</a>><span style="color:#5F5F5F"><br>
To: </span>"<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><span style="color:#5F5F5F"><br>
Date: </span>11/12/2015 05:25 PM<span style="color:#5F5F5F"><br>
Subject: </span>Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing on gate.<o:p></o:p></p>
<div class="MsoNormal">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="left">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:13.5pt"><br>
<br>
<br>
<tt>Eli,</tt><br>
<br>
<tt>First of all I would like to say thank you for your effort (I never seen so many path sets ;)), but I don¡¯t think we should remove ¡°tls_disabled=True¡± tests from gates now (maybe in L).</tt><br>
<tt>It¡¯s still vey commonly used feature and backup plan if TLS doesn¡¯t work for some reasons.</tt><br>
<br>
<tt>I think it¡¯s good idea to group tests per pipeline we should definitely follow it.</tt><br>
<br>
<tt>¡ª</tt><br>
<tt>Egor</tt><br>
<br>
<tt>From: "Qiao,Liyong" <liyong.qiao@intel.com<</tt></span><a href="mailto:liyong.qiao@intel.com"><tt><span style="font-size:13.5pt">mailto:liyong.qiao@intel.com</span></tt></a><tt><span style="font-size:13.5pt">>></span></tt><span style="font-size:13.5pt"><br>
<tt>Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<</tt></span><a href="mailto:openstack-dev@lists.openstack.org"><tt><span style="font-size:13.5pt">mailto:openstack-dev@lists.openstack.org</span></tt></a><tt><span style="font-size:13.5pt">>></span></tt><span style="font-size:13.5pt"><br>
<tt>Date: Wednesday, November 11, 2015 at 23:02</tt><br>
<tt>To: "openstack-dev@lists.openstack.org<</tt></span><a href="mailto:openstack-dev@lists.openstack.org"><tt><span style="font-size:13.5pt">mailto:openstack-dev@lists.openstack.org</span></tt></a><tt><span style="font-size:13.5pt">>" <openstack-dev@lists.openstack.org<</span></tt><a href="mailto:openstack-dev@lists.openstack.org"><tt><span style="font-size:13.5pt">mailto:openstack-dev@lists.openstack.org</span></tt></a><tt><span style="font-size:13.5pt">>></span></tt><span style="font-size:13.5pt"><br>
<tt>Subject: [openstack-dev] [Magnum][Testing] Reduce Functional testing on gate.</tt><br>
<br>
<tt>hello all:</tt><br>
<br>
<tt>I will update some Magnum functional testing status, functional/integration testing</tt><br>
<tt>is important to us, since we change/modify the Heat template rapidly, we need to</tt><br>
<tt>verify the modification is correct, so we need to cover all templates Magnum has.</tt><br>
<tt>and currently we only has k8s testing(only test with atomic image), we need to</tt><br>
<tt>add more, like swarm(WIP), mesos(under plan), also , we may need to support COS image.</tt><br>
<tt>lots of work need to be done.</tt><br>
<br>
<tt>for the functional testing time costing, we discussed during the Tokyo summit,</tt><br>
<tt>Adrian expected that we can reduce the timing cost to 20min.</tt><br>
<br>
<tt>I did some analyses on the functional/integrated testing on gate pipeline.</tt><br>
<tt>the stages will be follows:</tt><br>
<tt>take k8s functional testing for example, we did follow testing case:</tt><br>
<br>
<tt>1) baymodel creation</tt><br>
<tt>2) bay(tls_disabled=True) creation/deletion</tt><br>
<tt>3) bay(tls_disabled=False) creation to testing k8s api and delete it after testing.</tt><br>
<br>
<tt>for each stage, the time costing is follows:</tt><br>
<br>
<tt>*   devstack prepare: 5-6 mins</tt><br>
<tt>*   Running devstack: 15 mins(include downloading atomic image)</tt><br>
<tt>*   1) and 2) 15 mins</tt><br>
<tt>*   3) 15 +3 mins</tt><br>
<br>
<tt>totally about 60 mins currently a example is 1h 05m 57s</tt><br>
<tt>see </tt></span><a href="http://logs.openstack.org/10/243910/1/check/gate-functional-dsvm-magnum-k8s/5e61039/console.html"><tt><span style="font-size:13.5pt">http://logs.openstack.org/10/243910/1/check/gate-functional-dsvm-magnum-k8s/5e61039/console.html</span></tt></a><span style="font-size:13.5pt"><br>
<tt>for all time stamps.</tt><br>
<br>
<tt>I don't think it is possible to reduce time to 20 mins, since devstack setup will take 20 mins already.</tt><br>
<br>
<tt>To reduce time, I suggest to only create 1 bay each pipeline and do vary kinds of testing</tt><br>
<tt>on this bay, if want to test some specify bay (for example, network_driver etc), create</tt><br>
<tt>a new pipeline .</tt><br>
<br>
<tt>So, <span lang="ZH-CN">£É</span> think we can delete 2), since 3) will do similar things(create/delete), the different is</tt><br>
<tt>3) use tls_disabled=False. what do you think ?</tt><br>
<tt>see </tt></span><a href="https://review.openstack.org/244378"><tt><span style="font-size:13.5pt">https://review.openstack.org/244378</span></tt></a><tt><span style="font-size:13.5pt"> for the time costing, will reduce to 45 min (48m 50s in the example.)</span></tt><span style="font-size:13.5pt"><br>
<br>
<tt>=================================</tt><br>
<tt>For other related functional testing works:</tt><br>
<tt>I 'v done the split of functional testing per COE, we have pipeline as:</tt><br>
<br>
<tt>*   gate-functional-dsvm-magnum-api 30 mins</tt><br>
<tt>*   gate-functional-dsvm-magnum-k8s 60 mins</tt><br>
<br>
<tt>And for swam pipeline, patches is done, under reviewing now(works fine on gate)</tt><u><span style="color:blue"><br>
</span></u></span><a href="https://review.openstack.org/244391"><tt><span style="font-size:13.5pt">https://review.openstack.org/244391</span></tt></a><u><span style="font-size:13.5pt;color:blue"><br>
</span></u><a href="https://review.openstack.org/226125"><tt><span style="font-size:13.5pt">https://review.openstack.org/226125</span></tt></a><span style="font-size:13.5pt"><br>
<br>
<tt>========================</tt><br>
<br>
<tt>--</tt><br>
<tt>BR, Eli(Li Yong)Qiao</tt><br>
<tt>__________________________________________________________________________</tt><br>
<tt>OpenStack Development Mailing List (not for usage questions)</tt><br>
<tt>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a></tt><u><span style="color:blue"><br>
</span></u></span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><span style="font-size:13.5pt">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</span></tt></a><span style="font-size:13.5pt"><br>
<br>
</span><tt>__________________________________________________________________________</tt><br>
<tt>OpenStack Development Mailing List (not for usage questions)</tt><br>
<tt>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a></tt><br>
<tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></tt><br>
<br>
<br>
<o:p></o:p></p>
</div>
</body>
</html>