[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 jsbryant@electronicjungle.net IRC: jungleboyj
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 jsbryant@electronicjungle.net IRC: jungleboyj
Hi Jay, Kaminario’s CI is broken since the drop of Xenial support<https://github.com/openstack/devstack/commit/2e6677869925c86c01cae883b3dde6cccad81d30#diff-bf9b573c0ab6dc360b113034fe6c58a2>. We are working to resolve the these issues. Ido Benda www.kaminario.com<http://www.kaminario.com/> Mobile: +(972)-52-4799393 E-Mail: ido.benda@kaminario.com<mailto:nir.carasso@kaminario.com> From: Jay Bryant <jungleboyj@gmail.com> Sent: Wednesday, January 22, 2020 21:51 To: openstack-discuss@lists.openstack.org; inspur.ci@inspur.com; wangyong2017@inspur.com; Chengwei.Chou@infortrend.com; Bill.Sung@infortrend.com; Kuirong.Chen(陳奎融) <Kuirong.Chen@infortrend.com>; Ido Benda <Ido.Benda@kaminario.com>; Srinivas Dasthagiri <srinivasd.ctr@kaminario.com>; nec-cinder-ci@istorage.jp.nec.com; silvan@quobyte.com; robert@quobyte.com; felix@quobyte.com; bjoern@quobyte.com; OpenStack Development <openstack-dev@zadarastorage.com>; Shlomi Avihou | Zadara <shlomi@zadarastorage.com>; msdu-openstack@groups.ext.hpe.com Subject: [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: * MacroSAN Driver * Removed: * ProphetStor Driver * Nimble Storage Driver * Veritas Access Driver * Veritas CNFS Driver * Virtuozzo Storage Driver * Huawei FusionStorage Driver * 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 jsbryant@electronicjungle.net<mailto:jsbryant@electronicjungle.net> IRC: jungleboyj
Hi Jay, We are working on Kaminario CI fresh configuration(since it is too old, it has broken). We have communicated with OpenStack-infra community for the suggestions and documentation. One of the community member suggested us to go with manual CI configuration(Not third party CI) instead of CI configuration with puppet architecture(Since it is moving to Ansible). But we did not get documents for all other CI components except ZuulV3 from community. Can you please confirm us that we have to go with manual CI components configuration. If YES, can you please provide us the necessary document to configure openstack CI without using puppet modules. If NO, Shall we configure the CI with puppet modules in order to make Kaminario CI up and running for now and later we will upgrade the CI to use Zuul V3. Shall we go with this approach? Thanks & Regards Srinivas & Venkata Krishna ________________________________ From: Ido Benda <Ido.Benda@kaminario.com> Sent: 23 January 2020 18:11 To: jsbryant@electronicjungle.net <jsbryant@electronicjungle.net>; openstack-discuss@lists.openstack.org <openstack-discuss@lists.openstack.org>; inspur.ci@inspur.com <inspur.ci@inspur.com>; wangyong2017@inspur.com <wangyong2017@inspur.com>; Chengwei.Chou@infortrend.com <Chengwei.Chou@infortrend.com>; Bill.Sung@infortrend.com <Bill.Sung@infortrend.com>; Kuirong.Chen(陳奎融) <Kuirong.Chen@infortrend.com>; Srinivas Dasthagiri <srinivasd.ctr@kaminario.com>; nec-cinder-ci@istorage.jp.nec.com <nec-cinder-ci@istorage.jp.nec.com>; silvan@quobyte.com <silvan@quobyte.com>; robert@quobyte.com <robert@quobyte.com>; felix@quobyte.com <felix@quobyte.com>; bjoern@quobyte.com <bjoern@quobyte.com>; OpenStack Development <openstack-dev@zadarastorage.com>; Shlomi Avihou | Zadara <shlomi@zadarastorage.com>; msdu-openstack@groups.ext.hpe.com <msdu-openstack@groups.ext.hpe.com> Subject: RE: [cinder][ci] Cinder drivers being Unsupported and General CI Status ... Hi Jay, Kaminario’s CI is broken since the drop of Xenial support<https://github.com/openstack/devstack/commit/2e6677869925c86c01cae883b3dde6cccad81d30#diff-bf9b573c0ab6dc360b113034fe6c58a2>. We are working to resolve the these issues. Ido Benda www.kaminario.com<http://www.kaminario.com/> Mobile: +(972)-52-4799393 E-Mail: ido.benda@kaminario.com<mailto:nir.carasso@kaminario.com> From: Jay Bryant <jungleboyj@gmail.com> Sent: Wednesday, January 22, 2020 21:51 To: openstack-discuss@lists.openstack.org; inspur.ci@inspur.com; wangyong2017@inspur.com; Chengwei.Chou@infortrend.com; Bill.Sung@infortrend.com; Kuirong.Chen(陳奎融) <Kuirong.Chen@infortrend.com>; Ido Benda <Ido.Benda@kaminario.com>; Srinivas Dasthagiri <srinivasd.ctr@kaminario.com>; nec-cinder-ci@istorage.jp.nec.com; silvan@quobyte.com; robert@quobyte.com; felix@quobyte.com; bjoern@quobyte.com; OpenStack Development <openstack-dev@zadarastorage.com>; Shlomi Avihou | Zadara <shlomi@zadarastorage.com>; msdu-openstack@groups.ext.hpe.com Subject: [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: * MacroSAN Driver * Removed: * ProphetStor Driver * Nimble Storage Driver * Veritas Access Driver * Veritas CNFS Driver * Virtuozzo Storage Driver * Huawei FusionStorage Driver * 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 jsbryant@electronicjungle.net<mailto:jsbryant@electronicjungle.net> IRC: jungleboyj
On 2020-02-03 13:50:03 +0000 (+0000), Srinivas Dasthagiri wrote:
We are working on Kaminario CI fresh configuration(since it is too old, it has broken). We have communicated with OpenStack-infra community for the suggestions and documentation. One of the community member suggested us to go with manual CI configuration(Not third party CI) instead of CI configuration with puppet architecture(Since it is moving to Ansible). But we did not get documents for all other CI components except ZuulV3 from community. [...]
To clarify that recommendation, it was to build a third-party CI system by reading the documentation for the components you're going to use and understanding how they work. The old Puppet-based documentation you're referring to was written by some operators of third-party CI systems but not kept updated, so the versions of software it would need if you follow it would be years-old and in some cases (especially Jenkins and associated plug-ins) dangerously unsafe to connect to the internet due to widely-known security vulnerabilities in the versions you'd have to use. Modern versions of the tools you would want to use are well-documented, there's just no current document explaining exactly how to use them together for the exact situation you're in without having to understand how the software works. Many folks in your situation seem to want someone else to provide a simple walk-through for them, so until someone who is in your situation (maybe you?) takes the time to gain familiarity with recent versions of CI software and publish some documentation on how you got it communicating correctly with OpenDev's Gerrit deployment, such a walk-through is not going to exist. But even that, if not kept current, will quickly fall stale: all of those components, including Gerrit itself, need updating over time to address bugs and security vulnerabilities, and those updates occasionally come with backward-incompatible behavior changes. People maintaining these third-party CI systems are going to need to *stay* familiar with the software they're running, keep on top of necessary behavior and configuration changes over time, and update any new walk-through document accordingly so that it doesn't wind up in the same state as the one we had. -- Jeremy Stanley
Jay Bryant wrote:
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
We (OSF) reached out to our contacts at those companies (except Kaminario who already replied here), to increase the chances that they get the message. Please note that Inspur is in the middle of (extended) holidays in China and may be slow to respond :) -- Thierry Carrez (ttx)
On 1/28/2020 4:05 AM, Thierry Carrez wrote:
Jay Bryant wrote:
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
We (OSF) reached out to our contacts at those companies (except Kaminario who already replied here), to increase the chances that they get the message.
Please note that Inspur is in the middle of (extended) holidays in China and may be slow to respond :)
Thank you! We have started seeing some more responses as a result. It is appreciated. Jay
Greetings, The Zadara CI system is up and reporting again Thanks, Shlomi. On Wed, Jan 22, 2020 at 9:51 PM Jay Bryant <jungleboyj@gmail.com> wrote:
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: - MacroSAN Driver - Removed: - ProphetStor Driver - Nimble Storage Driver - Veritas Access Driver - Veritas CNFS Driver - Virtuozzo Storage Driver - Huawei FusionStorage Driver - 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
jsbryant@electronicjungle.net
IRC: jungleboyj
Hi jay, Infortrend third part CI is broken for some reason, I’ll check our environment and resolve it. KuiRong Software Design Dept.II Ext. 7125 From: Jay Bryant <jungleboyj@gmail.com> Sent: Thursday, January 23, 2020 3:51 AM To: openstack-discuss@lists.openstack.org; inspur.ci@inspur.com; wangyong2017@inspur.com; Chengwei.Chou(周政緯) <Chengwei.Chou@infortrend.com>; Bill.Sung(宋柏毅) <Bill.Sung@infortrend.com>; Kuirong.Chen(陳奎融) <Kuirong.Chen@infortrend.com>; ido.benda@kaminario.com; srinivasd.ctr@kaminario.com; nec-cinder-ci@istorage.jp.nec.com; silvan@quobyte.com; robert@quobyte.com; felix@quobyte.com; bjoern@quobyte.com; OpenStack Development <openstack-dev@zadarastorage.com>; Shlomi Avihou | Zadara <shlomi@zadarastorage.com>; msdu-openstack@groups.ext.hpe.com Subject: [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: * MacroSAN Driver * Removed: * ProphetStor Driver * Nimble Storage Driver * Veritas Access Driver * Veritas CNFS Driver * Virtuozzo Storage Driver * Huawei FusionStorage Driver * 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 jsbryant@electronicjungle.net<mailto:jsbryant@electronicjungle.net> IRC: jungleboyj
participants (7)
-
Ido Benda
-
Jay Bryant
-
Jeremy Stanley
-
Kuirong.Chen(陳奎融)
-
Shlomi Avihou
-
Srinivas Dasthagiri
-
Thierry Carrez