I support moving it to non-voting from the experimental queue. It will be much more visible that way if something breaks. ----- Reply message ----- From: "Ivan Kolodyazhny" <e0ne at e0ne.info> To: "OpenStack Development Mailing List" <openstack-dev at lists.openstack.org> Cc: "Oleksiy Butenko" <obutenko at mirantis.com>, "Kyrylo Romanenko" <kromanenko at mirantis.com> Subject: [openstack-dev] [Cinder] python-cinderclient functional tests Date: Mon, Jul 6, 2015 1:48 PM Hi all, As you may know, we've got experimental job [1] to run functional tests [2] for python-cinderclient with devstack setup. Functional tests for python-cinderclient is very important because it's almost the only way to test python-cinderclient with Cinder API. For now, we've got only Rally which uses cinderclient to test Cinder. Tempest uses own client for all APIs. Current tests coverage are very low.. That's why I would like to ask everyone to contribute to python-cinderclient. I created etherpad [3] with current progress. You can find me (e0ne) or any other core in #openstack-cinder in IRC. Aslo, what do you think about moving cinderclient functional tests from experimental to non-voting queue to make it more public and run it with every patch to python-cinderclient? [1] https://review.openstack.org/#/c/182528/ [2] https://github.com/openstack/python-cinderclient/tree/master/cinderclient/tests/functional [3] https://etherpad.openstack.org/p/cinder-client-functional-tests Regards, Ivan Kolodyazhny -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150706/1549ea15/attachment.html>