RE: [cinder][ci] Cinder drivers being Unsupported and General CI Status ...
Hi Jay,
NEC Cinder CI was configured with zuul v2.5 and Jenkins, and has not been working since "Drop Xenial support". We are fixing our CI with zuul v3 using Software Factory mentioned in the last Cinder Ussuri Virtual Mid-Cycle meeting [1].
We installed Software Factory referring to guide [2], and are investigating how we can monitor openstack/cinder events and create cinder test jobs. It will be helpful if cinder-specific examples are available.
[1] https://etherpad.openstack.org/p/cinder-ussuri-mid-cycle-planning [2] https://softwarefactory-project.io/r/#/c/17097/
Thanks,
Naoki Saito E-Mail: nasaito at nec.com
From: Jay Bryant <jungleboyj at gmail.com> Sent: Thursday, January 23, 2020 4:51 AM To: openstack-discuss at lists.openstack.org; inspur.ci at inspur.com; wangyong2017 at inspur.com; Chengwei.Chou at infortrend.com; Bill.Sung at infortrend.com; Kuirong.Chen(陳奎融) <Kuirong.Chen at infortrend.com>; ido.benda at kaminario.com; srinivasd.ctr at kaminario.com; nec-cinder-ci at istorage.jp.nec.com; silvan at quobyte.com; robert at quobyte.com; felix at quobyte.com; bjoern at quobyte.com; OpenStack Development <openstack-dev at zadarastorage.com>; Shlomi Avihou | Zadara <shlomi at zadarastorage.com>; msdu-openstack at groups.ext.hpe.com Subject: [nec-cinder-ci:76204] [cinder][ci] Cinder drivers being Unsupported and General CI Status ...
All, 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: • Inspur Drivers • Infortrend • Kaminario • NEC • Quobyte • Zadara • HPE Drivers If your name is in the list above you are receiving this e-mail directly, not just through the mailing list. If you are working on resolving CI issues please let me know so we can discuss how to proceed. 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: • Unsupported: o MacroSAN Driver • Removed: o ProphetStor Driver o Nimble Storage Driver o Veritas Access Driver o Veritas CNFS Driver o Virtuozzo Storage Driver o Huawei FusionStorage Driver o Sheepdog Storage Driver 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? 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. Thank you! Jay Bryant mailto:jsbryant at electronicjungle.net IRC: jungleboyj
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?
Regards
*Tony Pearce*
On Fri, 24 Jan 2020 at 16:05, SAITO NAOKI(齊藤 直樹) nasaito@nec.com wrote:
Hi Jay,
NEC Cinder CI was configured with zuul v2.5 and Jenkins, and has not been working since "Drop Xenial support". We are fixing our CI with zuul v3 using Software Factory mentioned in the last Cinder Ussuri Virtual Mid-Cycle meeting [1].
We installed Software Factory referring to guide [2], and are investigating how we can monitor openstack/cinder events and create cinder test jobs. It will be helpful if cinder-specific examples are available.
[1] https://etherpad.openstack.org/p/cinder-ussuri-mid-cycle-planning [2] https://softwarefactory-project.io/r/#/c/17097/
Thanks,
Naoki Saito E-Mail: nasaito at nec.com
From: Jay Bryant <jungleboyj at gmail.com> Sent: Thursday, January 23, 2020 4:51 AM To: openstack-discuss at lists.openstack.org; inspur.ci at inspur.com;
wangyong2017 at inspur.com; Chengwei.Chou at infortrend.com; Bill.Sung at infortrend.com; Kuirong.Chen(陳奎融) <Kuirong.Chen at infortrend.com>; ido.benda at kaminario.com; srinivasd.ctr at kaminario.com; nec-cinder-ci at istorage.jp.nec.com; silvan at quobyte.com; robert at quobyte.com; felix at quobyte.com; bjoern at quobyte.com; OpenStack Development <openstack-dev at zadarastorage.com>; Shlomi Avihou | Zadara <shlomi at zadarastorage.com>; msdu-openstack at groups.ext.hpe.com
Subject: [nec-cinder-ci:76204] [cinder][ci] Cinder drivers being
Unsupported and General CI Status ...
All, 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:
• Inspur Drivers • Infortrend • Kaminario • NEC • Quobyte • Zadara • HPE Drivers If your name is in the list above you are receiving this e-mail
directly, not just through the mailing list.
If you are working on resolving CI issues please let me know so we can
discuss how to proceed.
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:
• Unsupported: o MacroSAN Driver • Removed: o ProphetStor Driver o Nimble Storage Driver o Veritas Access Driver o Veritas CNFS Driver o Virtuozzo Storage Driver o Huawei FusionStorage Driver o Sheepdog Storage Driver 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?
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.
Thank you! Jay Bryant mailto:jsbryant at electronicjungle.net IRC: jungleboyj
On 2020-01-24 16:55:57 +0800 (+0800), Tony Pearce wrote:
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?
Looks like Huawei already does this for their Fusioncompute driver:
https://opendev.org/x/cinder-fusioncompute
And make them available on the marketplace as an optional download for users that require it?
[...]
Yeah, I don't see it in the marketplace's Cinder drivers list. We'd also need some way to indicate that the OpenStack project can't vouch for the quality or even viability of such drivers.
Tony Pearce wrote:
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?
I still hope those vendors will step up and fix the continuous integration testing in their drivers so that they can stay in the mainline cinder repository. That would be the best outcome.
But if they don't, they could totally continue to be maintained on our infrastructure, using a separate organization/namespace to make it clear they are not maintained/supported by the "OpenStack" project.
participants (4)
-
Jeremy Stanley
-
SAITO NAOKI(齊藤 直樹)
-
Thierry Carrez
-
Tony Pearce