<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Good to know. I think it's a good idea to implement a common compute
verifier after instances booted. Maybe we can define different
checking levels so that it can be leveraged by different test cases.
I will see what I can do. <br>
<br>
<div class="moz-cite-prefix">On 24/06/14 22:27, Sean Dague wrote:<br>
</div>
<blockquote cite="mid:53A952A5.8080101@dague.net" type="cite">
<pre wrap="">On 06/24/2014 01:29 AM, Fei Long Wang wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Greetings,
We're leveraging the scenario test of Tempest to do the end-to-end
functional test to make sure everything work great after upgrade,
patching, etc. And We're happy to fill the gaps we found. However, I'm a
little bit confused about the test policy from the scenario test
perspective, especially comparing with the API test. IMHO, scenario test
will cover some typical work flows of one specific service or mixed
services, and it would be nice to make sure the function is really
working instead of just checking the object status from OpenStack
perspective. Is that correct?
For example, live migration of Nova, it has been covered in API test of
Tempest (see
<a class="moz-txt-link-freetext" href="https://github.com/openstack/tempest/blob/master/tempest/api/compute/test_live_block_migration.py">https://github.com/openstack/tempest/blob/master/tempest/api/compute/test_live_block_migration.py</a>).
But as you see, it just checks if the instance is Active or not instead
of checking if the instance can be login/ssh successfully. Obviously,
from an real world view, we'd like to check if it's working indeed. So
the question is, should this be improved? If so, the enhanced code
should be in API test, scenario test or any other places? Thanks you.
</pre>
</blockquote>
<pre wrap="">
The fact that computes aren't verified fully during the API testing is
mostly historical. I think they should be. The run_ssh flag used to be
used for this, however because of some long standing race conditions in
the networking stack, that wasn't able to be turned on in upstream
testing. My guess is that it's rotted now.
We've had some conversations in the QA team about a compute verifier
that would be run after any of the compute jobs to make sure they booted
correctly, and more importantly, did a very consistent set of debug
capture when they didn't. Would be great if that's something you'd like
to help out with.
-Sean
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Cheers & Best regards,
Fei Long Wang (王飞龙)
--------------------------------------------------------------------------
Senior Cloud Software Engineer
Tel: +64-48032246
Email: <a class="moz-txt-link-abbreviated" href="mailto:flwang@catalyst.net.nz">flwang@catalyst.net.nz</a>
Catalyst IT Limited
Level 6, Catalyst House, 150 Willis Street, Wellington
-------------------------------------------------------------------------- </pre>
</body>
</html>