Open Stack

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 at kaminario.com>
Sent: 23 January 2020 18:11
To: jsbryant at electronicjungle.net <jsbryant at electronicjungle.net>; openstack-discuss at lists.openstack.org <openstack-discuss at lists.openstack.org>; inspur.ci at inspur.com <inspur.ci at inspur.com>; wangyong2017 at inspur.com <wangyong2017 at inspur.com>; Chengwei.Chou at infortrend.com <Chengwei.Chou at infortrend.com>; Bill.Sung at infortrend.com <Bill.Sung at infortrend.com>; Kuirong.Chen(陳奎融) <Kuirong.Chen at infortrend.com>; Srinivas Dasthagiri <srinivasd.ctr at kaminario.com>; nec-cinder-ci at istorage.jp.nec.com <nec-cinder-ci at istorage.jp.nec.com>; silvan at quobyte.com <silvan at quobyte.com>; robert at quobyte.com <robert at quobyte.com>; felix at quobyte.com <felix at quobyte.com>; bjoern 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 <msdu-openstack at 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 at kaminario.com<mailto:nir.carasso at kaminario.com>



From: Jay Bryant <jungleboyj at gmail.com>
Sent: Wednesday, January 22, 2020 21:51
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 <Ido.Benda at kaminario.com>; Srinivas Dasthagiri <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: [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 at electronicjungle.net<mailto:jsbryant at electronicjungle.net>

IRC:  jungleboyj


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200203/f111b59d/attachment-0001.html>