<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Fungi (on irc) suggested the following option to run the tests without reporting them to gerrit.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’m still testing it out, but for the benefit of others using the “zuul” ci approach, try the “silent” pipeline [1]<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">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Ramy<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]https://github.com/openstack-infra/zuul/blob/master/doc/source/zuul.rst:<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-line-height-alt:10.95pt"><span style="font-family:"Helvetica","sans-serif";color:#333333">This will trigger jobs whenever a change is merged to a named branch (e.g., </span><span style="font-size:10.5pt;font-family:Consolas;color:#333333">master</span><span style="font-family:"Helvetica","sans-serif";color:#333333">).
No output will be reported to Gerrit. This is useful for side effects such as creating per-commit tarballs.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:#F7F7F7"><span style="font-size:10.5pt;font-family:Consolas;color:#333333">- name: silent<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:#F7F7F7"><span style="font-size:10.5pt;font-family:Consolas;color:#333333"> manager: IndependentPipelineManager<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:#F7F7F7"><span style="font-size:10.5pt;font-family:Consolas;color:#333333"> trigger:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt;background:#F7F7F7"><span style="font-size:10.5pt;font-family:Consolas;color:#333333"> - event: patchset-created<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"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> John Griffith [mailto:john.griffith@solidfire.com]
<br>
<b>Sent:</b> Friday, August 22, 2014 2:25 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [Cinder][third-party] How to make progress on cinder driver CI post J3<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Courier New""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Aug 22, 2014 at 11:19 AM, Asselin, Ramy <<a href="mailto:ramy.asselin@hp.com" target="_blank">ramy.asselin@hp.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Many of us are still working on setting up and testing 3<sup>rd</sup> party ci for cinder drivers.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">None of them currently have gerrit +1/-1 voting, but I heard there’s a plan to “disable” those that are “not working” post-J3 (Please correct me if I misunderstood).<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">However, Post-J3 is a great time to work on 3<sup>rd</sup> party ci for a few reasons:<o:p></o:p></p>
<p>1.<span style="font-size:7.0pt"> </span>Increases the overall QA effort when it’s most needed.<o:p></o:p></p>
<p>2.<span style="font-size:7.0pt"> </span>Many contributors have more time available since feature work is complete.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Since erroneous failing tests from non-voting ci accounts can still distract reviewers, I’d like to propose a compromise:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Marking 3<sup>rd</sup> party ci jobs still undergoing testing and stability as (non-voting).<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">e.g.<o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="background:white;border-collapse:collapse">
<tbody>
<tr>
<td style="border-top:none;border-left:solid #EEF3F5 1.0pt;border-bottom:solid #EEF3F5 1.0pt;border-right:none;padding:1.5pt 4.5pt .75pt 4.5pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span style="font-family:"Arial","sans-serif";color:black">dsvm-tempest-my-driver</span><o:p></o:p></p>
</td>
<td style="border-top:none;border-left:solid #EEF3F5 1.0pt;border-bottom:solid #EEF3F5 1.0pt;border-right:none;padding:1.5pt 4.5pt .75pt 4.5pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span style="font-family:"Arial","sans-serif";color:#007F00">SUCCESS</span><span style="font-family:"Arial","sans-serif";color:black"> in 39m 27s (non-voting)</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td style="border-top:none;border-left:solid #EEF3F5 1.0pt;border-bottom:solid #EEF3F5 1.0pt;border-right:none;padding:1.5pt 4.5pt .75pt 4.5pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span style="font-family:"Arial","sans-serif";color:black">dsvm-tempest-my-driver</span><o:p></o:p></p>
</td>
<td style="border-top:none;border-left:solid #EEF3F5 1.0pt;border-bottom:solid #EEF3F5 1.0pt;border-right:none;padding:1.5pt 4.5pt .75pt 4.5pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span style="font-family:"Arial","sans-serif";color:red">FAILURE </span><span style="font-family:"Arial","sans-serif";color:black">in 39m 54s (non-voting)</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">This way, progress can still be made by cinder vendors working on setting up 3<sup>rd</sup> party ci under ‘real’ load post J3 while minimizing distractions for cinder reviewers
and other stakeholders.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I think this is consistent with how the OpenStack “Jenkins” CI marks potentially unstable jobs.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Please share your thoughts.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Thanks,<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Ramy<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></p>
</blockquote>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family:"Cambria Math","serif""></span><span style="font-family:"Courier New"">Just FYI, I haven't necessarily heard that drivers etc are going to be removed. I would say however that the
job should be removed until it's stable. There's no reason you can't do that (just don't submit your results) and still work on fixing things up. My system for example has been running on every OpenStack commit today but I'm dumping results to a test location
while I make sure that things are stable and probably won't turn it on until late next week when I'm sure it will perform. Submitting a system that fails to start 80% of the time doesn't help any of us out IMO.<br>
<br>
I realize there's a LOT of really hard work going on and progress being made, not discounting that at all. Just pointing out that populating every review with "ci-system-xyz failed" doesn't help us out much either. If it's backend problems they need fixed,
if it's infra problems they need fixed. That's the whole point of this exercise to begin with IIRC.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Courier New"">Thanks<br>
John</span><span style="font-family:"Cambria Math","serif""></span><span style="font-family:"Courier New""><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>