<html 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="Title" content="">
<meta name="Keywords" content="">
<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:"Apple Color Emoji";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
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;}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">You just made me remember my time as police man for Neutron plugins!
</span><span style="font-size:11.0pt;font-family:"Apple Color Emoji"">☺</span><span style="font-size:11.0pt;font-family:Calibri"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Edgar<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">Sukhdev Kapur <sukhdevkapur@gmail.com><br>
<b>Reply-To: </b>"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org><br>
<b>Date: </b>Tuesday, January 24, 2017 at 3:14 PM<br>
<b>To: </b>"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org><br>
<b>Subject: </b>Re: [openstack-dev] [Neutron] PTL Candidacy<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I remember good old days when CI was introduced in Neutron (during Icehouse time frame). There was excellent momentum behind it. We did not know some of the enforcement details, which created lots of confusion/havoc.
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Now that we have a better understanding of the past issues, and lots of good ideas to address them, I think it is appropriate to reactivate the process. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">As to Jeremy's options, I think option B makes the best sense - the driver author/owner should bare the burden of declaring a driver/plugin compatible.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">cheers..<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">-Sukhdev<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Tue, Jan 24, 2017 at 12:46 PM, Jeremy Stanley <<a href="mailto:fungi@yuggoth.org" target="_blank">fungi@yuggoth.org</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">
<p class="MsoNormal">On 2017-01-24 10:51:39 -0800 (-0800), Ihar Hrachyshka wrote:<br>
> On Tue, Jan 24, 2017 at 12:50 AM, Kevin Benton <kevin@benton.pub> wrote:<br>
> > I'm on board with getting visibility into the drivers with improvements to<br>
> > driverlog, etc. What I'm uncertain of is providing much in the lines of<br>
> > 'validation'. Core reviewers don't frequently have access to the hardware or<br>
> > software required to validate these drivers so we can't be sure if the<br>
> > features really are working as expected.<br>
> ><br>
> > If validation is as flexible as you highlighted in the email, we can at<br>
> > least get it to a point where all recent CI runs are linkable from driverlog<br>
> > and people can see recent tempest runs. I don't foresee the Neutron team<br>
> > getting to a point soon where we vouch for certain drivers though just<br>
> > because it is so hard to keep up with their changes (even ignoring changes<br>
> > in the vendor hardware itself).<br>
><br>
> Good point. We may guide plugins and drivers on how to set up CI; we<br>
> may help Foundation to set up Marketplace in such a way that would<br>
> allow to automatically consume test artifacts from driver owners; we<br>
> may provide guidance to Foundation about which features are more<br>
> important to reflect that in Marketplace; but I would hope we don't<br>
> put the Neutron team on the hook to validate each driver, or even<br>
> police CI owners to produce consumable results. (The stick in the<br>
> latter case would be driver not showing up in Marketplace, or showing<br>
> up with no feature support information.)<br>
<br>
I guess the question I have is who, then, can tell our<br>
operators/users what Neutron drivers are reasonably supported? It<br>
sounds like you're saying Neutron developers are not well-placed to<br>
determine that, which leaves us with these other options:<br>
<br>
A. Have the OpenStack Foundation as maintainers of the Marketplace<br>
decide which Neutron drivers are usable (they don't really staff<br>
for this purpose so would be throwing darts I think)<br>
<br>
B. Trust the driver authors to declare whether they're supported and<br>
what features they provide (maybe that works better than I<br>
expect?)<br>
<br>
C. Identify another party with a vested interest in validating<br>
driver support (a board of operators from different organizations<br>
maybe?)<br>
<br>
D. Provide links/aggregation of QA/CI and let the consumers attempt<br>
to divine supportability for themselves (seems a bit downstream<br>
hostile)<br>
<br>
Are any of those options preferable?<br>
<span class="hoenzb"><span style="color:#888888">--</span></span><span style="color:#888888"><br>
<span class="hoenzb">Jeremy Stanley</span></span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__OpenStack-2Ddev-2Drequest-40lists.openstack.org-3Fsubject-3Aunsubscribe&d=DwMFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=stAqZEa1UaR75JvzJ0FZBG0scAKmZwHhoC7exuAKsUc&s=J3l_htX2j4f1reTu2w6i8YUD4Q_0YgpguIiCHlJB0PE&e=" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev&d=DwMFaQ&c=DS6PUFBBr_KiLo7Sjt3ljp5jaW5k2i9ijVXllEdOozc&r=G0XRJfDQsuBvqa_wpWyDAUlSpeMV4W1qfWqBfctlWwQ&m=stAqZEa1UaR75JvzJ0FZBG0scAKmZwHhoC7exuAKsUc&s=j5yF8PsqCjQ64dZ3etZCnJfe9H7rlO9gO1xHDXbUf50&e=" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>