<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:"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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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">Having 3<sup>rd</sup> party CI report results automatically will be helpful.<o:p></o:p></p>
<p class="MsoNormal">While it is possible for PTLs to report per release which drivers should be listed in marketplace for release, currently PTLs are signed for this extra work.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Driver owners submitting DriverLog updates per release – not a big deal.<o:p></o:p></p>
<p class="MsoNormal">Extra work on Ilya.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I think we can define a rule for removal. If driver entry was not updated for 2(?) releases then remove it. We can run questionnaire for what the right # for it.<o:p></o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Arkady<o:p></o:p></p>
<p class="MsoNormal"><a name="_MailEndCompose"><o:p> </o:p></a></p>
<span style="mso-bookmark:_MailEndCompose"></span>
<p class="MsoNormal"><b>From:</b> Ilya Shakhat [mailto:shakhat@gmail.com] <br>
<b>Sent:</b> Thursday, March 1, 2018 4:44 AM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org><br>
<b>Subject:</b> [openstack-dev] [DriverLog] DriverLog future<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi!<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">For those who do not know, DriverLog is a community registry of 3rd-party drivers for OpenStack hosted together with Stackalytics [1]. The project started 4 years ago and by now contains information about 220
drivers. The data from DriverLog is also consumed by official Marketplace [2].<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Here I would like to discuss directions for DriverLog and 3rd-party driver registry as general.<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">1) Being a single community-wide registry was good initially, it allowed to quickly collect description for most of drivers in a single place. But in a long term this approach stopped working - not many projects
remember to update the information stored in some random place, right?<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Mike already pointed to this problem a year ago [3] and the idea was to move driver list to projects (and thus move responsibility to them too) and have an aggregated list of drivers produced by infra. Do we
have any progress in this direction? Is it a time to start deprecation of DriverLog and consider transition during Rocky release?<o:p></o:p></p>
</div>
<p class="MsoNormal">2) As a project with 4 years history DriverLog's list only increased over the time with quite few removals. Now it still has drivers with the latest version Liberty or drivers for non-maintained projects (e.g. Fuel). While it maybe makes
sense to keep all of them for operators who run older versions, it may produce a feeling that the majority of drivers are old. One of solutions for this is to show by default drivers for active releases only (Pike and ahead). If done this will apply to both
DriverLog and Marketplace. <o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Any other ideas or suggestions?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks,<br>
I<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br>
[1] <a href="http://stackalytics.com/report/driverlog">http://stackalytics.com/report/driverlog</a><br>
[2] <a href="https://www.openstack.org/marketplace/drivers/">https://www.openstack.org/marketplace/drivers/</a><br>
[3] <a href="http://lists.openstack.org/pipermail/openstack-dev/2017-January/110151.html">
http://lists.openstack.org/pipermail/openstack-dev/2017-January/110151.html</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>