<div dir="ltr">Hi all, a suggestion for the drivers which are not being supported from the vendor and as such are being removed from Openstack. Could the
removed drivers
be maintained in Openstack's git? And make them available on the marketplace as an optional download for users that require it? <div><br></div><div>Regards<br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><p><br></p><p style="background-image:initial;background-position:initial;background-repeat:initial"><a name="SignatureSanitizer_SafeHtmlFilter__MailAutoSig"><b><span style="font-size:10pt;font-family:Arial,sans-serif;color:black">Tony Pearce</span></b></a><span style="font-size:9pt;font-family:Arial,sans-serif;color:black"> </span></p><p>
</p><p> </p></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 24 Jan 2020 at 16:05, SAITO NAOKI(齊藤 直樹) <<a href="mailto:nasaito@nec.com">nasaito@nec.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Jay,<br>
<br>
NEC Cinder CI was configured with zuul v2.5 and Jenkins, and has not<br>
been working since "Drop Xenial support".<br>
We are fixing our CI with zuul v3 using Software Factory mentioned in<br>
the last Cinder Ussuri Virtual Mid-Cycle meeting [1].<br>
<br>
We installed Software Factory referring to guide [2],<br>
and are investigating how we can monitor openstack/cinder events and<br>
create cinder test jobs.<br>
It will be helpful if cinder-specific examples are available.<br>
<br>
[1] <a href="https://etherpad.openstack.org/p/cinder-ussuri-mid-cycle-planning" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/cinder-ussuri-mid-cycle-planning</a><br>
[2] <a href="https://softwarefactory-project.io/r/#/c/17097/" rel="noreferrer" target="_blank">https://softwarefactory-project.io/r/#/c/17097/</a><br>
<br>
Thanks,<br>
<br>
Naoki Saito<br>
E-Mail: nasaito at <a href="http://nec.com" rel="noreferrer" target="_blank">nec.com</a><br>
<br>
> From: Jay Bryant <jungleboyj at <a href="http://gmail.com" rel="noreferrer" target="_blank">gmail.com</a>> <br>
> Sent: Thursday, January 23, 2020 4:51 AM<br>
> To: openstack-discuss at <a href="http://lists.openstack.org" rel="noreferrer" target="_blank">lists.openstack.org</a>; <a href="http://inspur.ci" rel="noreferrer" target="_blank">inspur.ci</a> at <a href="http://inspur.com" rel="noreferrer" target="_blank">inspur.com</a>; wangyong2017 at <a href="http://inspur.com" rel="noreferrer" target="_blank">inspur.com</a>; Chengwei.Chou at <a href="http://infortrend.com" rel="noreferrer" target="_blank">infortrend.com</a>; Bill.Sung at <a href="http://infortrend.com" rel="noreferrer" target="_blank">infortrend.com</a>; Kuirong.Chen(陳奎融) <Kuirong.Chen at <a href="http://infortrend.com" rel="noreferrer" target="_blank">infortrend.com</a>>; ido.benda at <a href="http://kaminario.com" rel="noreferrer" target="_blank">kaminario.com</a>; srinivasd.ctr at <a href="http://kaminario.com" rel="noreferrer" target="_blank">kaminario.com</a>; nec-cinder-ci at <a href="http://istorage.jp.nec.com" rel="noreferrer" target="_blank">istorage.jp.nec.com</a>; silvan at <a href="http://quobyte.com" rel="noreferrer" target="_blank">quobyte.com</a>; robert at <a href="http://quobyte.com" rel="noreferrer" target="_blank">quobyte.com</a>; felix at <a href="http://quobyte.com" rel="noreferrer" target="_blank">quobyte.com</a>; bjoern at <a href="http://quobyte.com" rel="noreferrer" target="_blank">quobyte.com</a>; OpenStack Development <openstack-dev at <a href="http://zadarastorage.com" rel="noreferrer" target="_blank">zadarastorage.com</a>>; Shlomi Avihou | Zadara <shlomi at <a href="http://zadarastorage.com" rel="noreferrer" target="_blank">zadarastorage.com</a>>; msdu-openstack at <a href="http://groups.ext.hpe.com" rel="noreferrer" target="_blank">groups.ext.hpe.com</a><br>
> Subject: [nec-cinder-ci:76204] [cinder][ci] Cinder drivers being Unsupported and General CI Status ...<br>
> <br>
> All,<br>
> We once again are at the point in the release where we are talking about 3rd Party CI and what is going on for Cinder. At the moment I have analyzed drivers that have not successfully reported results on a Cinder patch in 30 or more days and have put together the following list of drivers to be unsupported in the Ussuri release:<br>
> • Inspur Drivers<br>
> • Infortrend<br>
> • Kaminario<br>
> • NEC<br>
> • Quobyte<br>
> • Zadara<br>
> • HPE Drivers<br>
> If your name is in the list above you are receiving this e-mail directly, not just through the mailing list.<br>
> If you are working on resolving CI issues please let me know so we can discuss how to proceed.<br>
> In addition to the fact that we will be pushing up unsupported patches for the drivers above, we have already unsupported and removed a number of drivers during this release. They are as follows:<br>
> • Unsupported:<br>
> o MacroSAN Driver<br>
> • Removed:<br>
> o ProphetStor Driver<br>
> o Nimble Storage Driver<br>
> o Veritas Access Driver<br>
> o Veritas CNFS Driver<br>
> o Virtuozzo Storage Driver<br>
> o Huawei FusionStorage Driver<br>
> o Sheepdog Storage Driver<br>
> Obviously we are reaching the point that the number of drivers leaving the community is concerning and it has sparked discussions around the fact that maybe our 3rd Party CI approach isn't working as intended. So what do we do? Just mark drivers unsupported and no longer remove drivers? Do we restore drivers that have recently been removed?<br>
> We are planning to have further discussion around these questions at our next Cinder meeting in #openstack-meeting-4 on Wednesday, 1/29/20 at 14:00 UTC. If you have thoughts or strong opinions around this topic please join us.<br>
> Thank you!<br>
> Jay Bryant<br>
> mailto:<a href="mailto:jsbryant" target="_blank">jsbryant</a> at <a href="http://electronicjungle.net" rel="noreferrer" target="_blank">electronicjungle.net</a><br>
> IRC: jungleboyj<br>
</blockquote></div>