[openstack-dev] [cinder] All Cinder Volume Drivers Must Have A Third Party CI by March 19, 2014

Mike Perez thingee at gmail.com
Fri Jan 16 03:31:54 UTC 2015

*Note: A more detailed email about this has been sent to all Cinder
volume driver maintainers directly.*

In the Jan 14th 2015 16:00 UTC Cinder IRC meeting [1], it was agreed
by Cinder core and participating vendors that the deadline for vendors
to have a third party CI would be:

March 19th 2015

There are requirements set for OpenStack Third Party CI's [2]. In
addition Cinder third party CI's must:

1) Test all volume drivers your company has integrated in Cinder.
2) Test all fabrics your solution uses.

For example, if your company has two volume drivers in Cinder and they
both use ISCSI and FibreChannel, you would need to have a CI that
tests against four backends and reports the results for each backend,
for every Cinder upstream patch. To test we're using a subset of tests
in Tempest [6].

To get started, read OpenStack's third party testing documentation
[32]. There are a variety of solutions [3] that help setting up a CI,
third party mentoring meetings [4], and designated people to answer
questions with setting up a third party CI in the #openstack-cinder
room [5].

If a solution is not being tested in a CI system and reporting to
OpenStack gerrit Cinder patches by the deadline of March 19th 2015, a
volume driver could be removed from the Cinder repository as of the
Kilo release. Without a CI system, Cinder core is unable to verify
your driver works in the Kilo release of Cinder. We will make sure
OpenStack users are aware of this via the OpenStack users mailing list
and Kilo release notes.

Cinder third party CI's have been discussed throughout a variety of
ways last year:

* Cinder IRC Meetings: [1][9][10][11][12][13][14][15][16]
* Midcycle meetups: [17]
* OpenStack dev list: [18][19][20][21][22][23][24][25][26][27][28][29]
* Design summit sessions: [30][31]

If there is something not clear about this email, please email me
*directly* with your question. You can also reach me as thingee on
Freenode IRC in the #openstack-cinder channel. Again I want you all to
be successful in this, and take advantage of this testing you will
have with your product. Please communicate with me and reach out to
the team for help.

Mike Perez

[1] - http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-01-14-16.00.log.html#l-21
[2] - http://ci.openstack.org/third_party.html#requirements
[3] - https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Existing_CI_Solutions
[4] - https://wiki.openstack.org/wiki/Meetings/ThirdParty
[5] - https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#Questions
[6] - https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#What_tests_do_I_use.3F
[7] - http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-12-10-16.00.log.html#l-471
[8] - http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-11-19-16.00.log.html#l-34
[9] - http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-10-29-16.00.log.html#l-224
[10] - http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-10-15-16.00.log.html#l-59
[11] - http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-10-08-16.00.log.html#l-17
[12] - http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-09-17-16.00.log.html#l-244
[13] - http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-07-02-16.01.log.html#l-141
[14] - http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-07-23-16.00.log.html#l-161
[15] - http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-06-18-16.02.log.html#l-255
[16] - http://eavesdrop.openstack.org/meetings/cinder/2014/cinder.2014-05-21-16.00.log.html#l-310
[17] - https://etherpad.openstack.org/p/cinder-meetup-summer-2014
[18] - http://lists.openstack.org/pipermail/openstack-dev/2014-September/045137.html
[19] - http://lists.openstack.org/pipermail/openstack-dev/2014-October/047673.html
[20] - http://lists.openstack.org/pipermail/openstack-dev/2014-July/039103.html
[21] - http://lists.openstack.org/pipermail/openstack-dev/2014-December/051957.html
[22] - http://lists.openstack.org/pipermail/openstack-dev/2014-August/043392.html
[23] - http://lists.openstack.org/pipermail/openstack-dev/2014-August/042672.html
[24] - http://lists.openstack.org/pipermail/openstack-dev/2014-August/041748.html
[25] - http://lists.openstack.org/pipermail/openstack-dev/2014-February/026999.html
[26] - http://lists.openstack.org/pipermail/openstack-dev/2014-March/028707.html
[27] - http://lists.openstack.org/pipermail/openstack-dev/2014-July/039057.html
[28] - http://lists.openstack.org/pipermail/openstack-dev/2014-February/027527.html
[29] - http://lists.openstack.org/pipermail/openstack-dev/2014-August/041704.html
[30] - https://etherpad.openstack.org/p/juno-cinder-3rd-party-cert-and-verification
[31] - http://junodesignsummit.sched.org/event/56eae44976e986f39c858d784344c7d0
[32] - http://ci.openstack.org/third_party.html

More information about the OpenStack-dev mailing list