As discussed in the last Cinder meeting [1], in order to have your volume driver readded into the Kilo release, you must have a CI reporting and stable for five days prior to 4/6.
This includes: 1) Providing logs to screen sessions, etc configs, tempest output [2]. 2) You should be running around 304 tests if you're following instructions from the Cinder third party wiki [3]. If you're running less than that, your CI will be *NOT* be considered satisfactory for skipping tests. I will also be emailing individuals who have already asked for exceptions, just to make sure communication was clear. [1] - http://eavesdrop.openstack.org/meetings/cinder/2015/cinder.2015-03-25-16.00.log.html#l-173 [2] - http://ci.openstack.org/third_party.html#requirements [3] - https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#What_tests_do_I_use.3F -- Mike Perez __________________________________________________________________________ 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
