The Neutron team also discussed this in Vancouver, you can see the etherpad here [1]. 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 release.
[1] https://etherpad.openstack.org/p/YVR-neutron-third-party-ci-liberty On Sun, Sep 27, 2015 at 11:39 AM, Armando M. <arma...@gmail.com> wrote: > > > On 25 September 2015 at 15:40, Chris Hoge <ch...@openstack.org> wrote: > >> In November, the OpenStack Foundation will start requiring vendors >> requesting >> new "OpenStack Compatible" storage driver licenses to start passing the >> Cinder >> 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 >> standards >> and technical requirements for the "OpenStack Powered" program. This is >> all >> 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 >> backed >> 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. We're >> 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 >> Compatible" >> 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 us >> 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 >> ecosystem. >> >> 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? > > Thanks, > Armando > > >> Thanks! >> >> Chris Hoge >> Interop Engineer >> OpenStack Foundation >> __________________________________________________________________________ >> 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 >> > > > __________________________________________________________________________ > 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 > >
__________________________________________________________________________ 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
