I intend to introduce a requirement for 3rd party CI for Manila during
the Liberty release. This shouldn't be a surprise to anyone because I've
been talking about it, but in case anyone didn't hear about it, now you
have.
I expect that by the Liberty release date, every driver in the tree
should have working/reporting vendor CI, similar to what the Cinder
project requires [1]. In order to achieve this goal, I will be setting
some deadlines at various points during the release, and I want the
community to help define those goals and to agree that they're
reasonable. I'm optimistic that this shouldn't be a terribly difficult
process because nearly all the drivers in Manila are maintained by
vendors who also have Cinder drivers and who have experience with
OpenStack CI systems.
However, if there's anyone who hasn't had to implement a CI system in
the past, for Cinder or any other OpenStack project, then I can't stress
enough how important it will be to get started on it early. Please
contact me and let me know if CI systems are new to you so we can make
sure to get you the help you'll need to be successful.
I'm going to write up a draft plan before the Vancouver summit for
CI-related deadlines and circulate it to be decided at one of the weekly
IRC meetings (most likely the one after the design summit).
[1] - https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers
-Ben Swartzlander
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
