Open Stack

Hi team,

Currently I've noticed that there are many Quantum related BPs in Tempest
and seems as if we are not managing to get things done because of different
opinions on how the tests should be implemented.

Looking at the BPs I found out a common problem which is that the test
cases are tightly coupled to what the Quantum API provides. Therefore I
fear that when these BPs are implemented, the test cases might have no
significant difference with Quantum unit tests other than not having
stubbed objects.

For the last two and a half months I did some homework and thought about
how Quantum integration tests could have maximum value on not only on
proving that the project is working but also showing that Quantum is
production ready. After talking with various stakeholders, my conclusion is
that Quantum integration tests should be designed starting from essential
NaaS requirements.

I've gathered a checklist of features needed in a NaaS in the document
below.

Link<https://docs.google.com/document/d/1y8RoCPoYMTT8l6oUgzIRBz8S_zDjfXYQY3v6IOc_CYM/edit?usp=sharing>

Based on these features I plan to first complete a CLI based testing manual
and eventually write Tempest scripts for them. I've drafted a BP at
https://blueprints.launchpad.net/tempest/+spec/quantum-naas-requirementsand
hope to get anykind of feedback from you.

Thanks!

-- 
*Intel SSG/SSD/STO/DCST/CIT*
880 Zixing Road, Zizhu Science Park, Minhang District, 200241, Shanghai,
China
+862161166500
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130322/365d3726/attachment.html>