[openstack-dev] [cinder][neutron][all] New third-party-ci testing requirements for OpenStack Compatible mark
sombrafam at gmail.com
Tue Sep 29 15:04:43 UTC 2015
There are some questions that came to my mind.
Cinder has near zero tolerance to backends that does not have a CI running.
So, can one assume that all drivers in Cinder will have the "OpenStack
When you say that the driver have to 'pass' the integration tests, what
tests do you consider? All tests in tempest? All patches? Do you have any
criteria to determine if a backend is passing or not?
About this "OpenStack Compatible" flag, how does it work? Will you hold a
list with the Compatible vendors? Is anything a vendor need to to in order
to use this?
On Mon, Sep 28, 2015 at 5:55 PM, Kyle Mestery <mestery at mestery.com> wrote:
> The Neutron team also discussed this in Vancouver, you can see the
> etherpad here . We talked about the idea of creating a validation suite,
> and it sounds like that's something we should again discuss in Tokyo for
> the Mitaka cycle. I think a validation suite would be a great step forward
> for Neutron third-party CI systems to use to validate they work with a
>  https://etherpad.openstack.org/p/YVR-neutron-third-party-ci-liberty
> On Sun, Sep 27, 2015 at 11:39 AM, Armando M. <armamig at gmail.com> wrote:
>> On 25 September 2015 at 15:40, Chris Hoge <chris at openstack.org> wrote:
>>> In November, the OpenStack Foundation will start requiring vendors
>>> new "OpenStack Compatible" storage driver licenses to start passing the
>>> third-party integration tests.
>> The new program was approved by the Board at
>>> the July meeting in Austin and follows the improvement of the testing
>>> and technical requirements for the "OpenStack Powered" program. This is
>>> part of the effort of the Foundation to use the OpenStack brand to
>>> guarantee a
>>> base-level of interoperability and consistency for OpenStack users and to
>>> protect the work of our community of developers by applying a trademark
>>> by their technical efforts.
>>> The Cinder driver testing is the first step of a larger effort to apply
>>> community determined standards to the Foundation marketing programs.
>>> starting with Cinder because it has a successful testing program in
>>> place, and
>>> we have plans to extend the program to network drivers and OpenStack
>>> applications. We're going require CI testing for new "OpenStack
>>> storage licenses starting on November 1, and plan to roll out network and
>>> application testing in 2016.
>>> One of our goals is to work with project leaders and developers to help
>>> define and implement these test programs. The standards for third-party
>>> drivers and applications should be determined by the developers and users
>>> in our community, who are experts in how to maintain the quality of the
>>> We welcome and feedback on this program, and are also happy to answer any
>>> questions you might have.
>> Thanks for spearheading this effort.
>> Do you have more information/pointers about the program, and how Cinder
>> in particular is
>> paving the way for other projects to follow?
>>> Chris Hoge
>>> Interop Engineer
>>> OpenStack Foundation
>>> OpenStack Development Mailing List (not for usage questions)
>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> OpenStack Development Mailing List (not for usage questions)
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev