<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none"><!-- P { margin-top: 0px; margin-bottom: 0px; }--></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>I think this also brings up a good point from yesterday's discussion about "what is an interim test?". We all vigorously agree that compliance to the API contract falls into interop testing. We also agreed that non-happy path (negative responses) are also
in the scope of interop. I think this test brings up another aspect important to interop, which for lack of a better term I will call application behavior.<br>
</p>
<p><br>
</p>
<p>It would be easy for the API responses to the create image/delete image to meet the correct response codes and schemas, but the behavior of the application to not be correct (the delete request is ignored, the image goes into the error state). Given that
we consider non-happy path API tests to be in consideration for interop, I think non-happy path application behavior would also fall into scope. I do think we can be more clear about what aspects of the OpenStack projects fall into scope (the artifacts created
by an application like VMs, volumes, etc are others that we include in our tests now) so that it is more apparent what tests should fall into scope.<br>
</p>
<p><br>
</p>
<p>Daryl<br>
</p>
<div dir="auto" style="color: rgb(33, 33, 33);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Gema Gomez-Solano <gema.gomez-solano@canonical.com><br>
<b>Sent:</b> Thursday, March 10, 2016 9:59 AM<br>
<b>To:</b> Catherine Cuong Diep<br>
<b>Cc:</b> Daryl Walleck; defcore-committee@lists.openstack.org<br>
<b>Subject:</b> Re: [OpenStack-DefCore] Fw: Discussing tests</font>
<div> </div>
</div>
<div>
<div>In my view the call to delete image should work regardless of the status of the image (from interoperability viewpoint). This is an async call, right? so it should be queued and dealt with in due time (i.e. whenever the save operation is finished). This
is the behavior I would expect as an end user, havent looked at the test yet, will do when i get home!</div>
<div id="AppleMailSignature"><br>
</div>
<div id="AppleMailSignature">Cheers,</div>
<div id="AppleMailSignature">Gema<br>
<br>
Sent from my iPhone</div>
<div><br>
On 10 Mar 2016, at 09:42, Catherine Cuong Diep <<a href="mailto:cdiep@us.ibm.com">cdiep@us.ibm.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<p>I think the question for DefCore to review is:<br>
<br>
Is "being able to delete an image that is not done saving " an important capability for interoperability ?<br>
<br>
Catherine Diep<br>
IBM Silicon Valley Laboratory, San Jose, California 95141<br>
<a href="mailto:cdiep@us.ibm.com">cdiep@us.ibm.com</a>, Tel: (408) 463-4352 T/L: 543-4352<br>
<font size="2" color="#800080">----- Forwarded by Catherine Cuong Diep/San Jose/IBM</font><font size="2" color="#800080"> on 03/10/2016 07:37 AM</font><font size="2" color="#800080"> -----</font><br>
<br>
<font size="2" color="#5F5F5F">From: </font><font size="2">Daryl Walleck <<a href="mailto:daryl.walleck@rackspace.com">daryl.walleck@RACKSPACE.COM</a>></font><br>
<font size="2" color="#5F5F5F">To: </font><font size="2">Jean-Daniel Bonnetot <<a href="mailto:jean-daniel.bonnetot@corp.ovh.com">jean-daniel.bonnetot@corp.ovh.com</a>>, "<a href="mailto:defcore-committee@lists.openstack.org">defcore-committee@lists.openstack.org</a>"
<<a href="mailto:defcore-committee@lists.openstack.org">defcore-committee@lists.openstack.org</a>></font><br>
<font size="2" color="#5F5F5F">Date: </font><font size="2">03/10/2016 07:25 AM</font><br>
<font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [OpenStack-DefCore] Discussing tests</font><br>
</p>
<hr width="100%" size="2" align="left" noshade="" style="color:#8091A5">
<br>
<br>
<br>
<font face="Calibri">My understanding of that test is that it is validating the system behavior being able to delete an image that is not done saving.</font><br>
<font face="Calibri"></font><br>
<font face="Calibri">As to your question of atomicity, one of the outcomes of the DefCore midcycle is an audit of the existing tests to provide a precise list of what API calls each test makes and what assertions are really being made. The outcome of that audit
should help with these types of questions about individual tests.</font><br>
<font face="Calibri"></font><br>
<font face="Calibri">Daryl</font><br>
<font size="4" face="Times New Roman"></font><br>
<b><font face="Calibri">From: </font></b><a href="mailto:jean-daniel.bonnetot@corp.ovh.com"><u><font color="#0000FF" face="Calibri">Jean-Daniel Bonnetot</font></u></a><b><font face="Calibri"><br>
Sent: </font></b><font face="Calibri">Thursday, March 10, 2016 9:05 AM</font><b><font face="Calibri"><br>
To: </font></b><a href="mailto:defcore-committee@lists.openstack.org"><u><font color="#0000FF" face="Calibri">defcore-committee@lists.openstack.org</font></u></a><b><font face="Calibri"><br>
Subject: </font></b><font face="Calibri">[OpenStack-DefCore] Discussing tests</font><br>
<font size="4" face="Times New Roman"></font>
<p>Hi defcore,<br>
<br>
Not sure it’s the right place to discuss about it but I try ;)<br>
<br>
I’m using refstack to test our Public Cloud at OVH and I have question about a test which make trouble on our solution.<br>
<br>
I run the 2015.07 guidelines.<br>
The test is tempest.api.compute.images.test_images.ImagesTestJSON.test_delete_saving_image.<br>
<br>
I saw this test corresponds to the compute-images-delete capability. <br>
I understand that image deletion is required, but why the test is deletion on a saving image?<br>
<br>
In this particular case, at OVH we had to patch Glance to forbid deletion if the image is in saving state because of some Ceph issue.<br>
I saw that during the last meetup you talked about "Atomicity of tests », I think that’s what I’m talking about too and I agree that it’s a problem we need to solve.<br>
<br>
compute-images-delete is marked as atomic but it’s not from my point of view.<br>
<br>
<br>
--<br>
Jean-Daniel Bonnetot<u><font color="#0000FF"><br>
</font></u><a href="http://www.ovh.com/"><u><font color="#0000FF">http://www.ovh.com</font></u></a><br>
@pilgrimstack<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Defcore-committee mailing list<br>
<a href="mailto:Defcore-committee@lists.openstack.org">Defcore-committee@lists.openstack.org</a><u><font color="#0000FF"><br>
</font></u><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee"><u><font color="#0000FF">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</font></u></a><tt>_______________________________________________<br>
Defcore-committee mailing list<br>
<a href="mailto:Defcore-committee@lists.openstack.org">Defcore-committee@lists.openstack.org</a><br>
</tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a></tt><tt><br>
</tt></p>
<p><br>
</p>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Defcore-committee mailing list</span><br>
<span><a href="mailto:Defcore-committee@lists.openstack.org">Defcore-committee@lists.openstack.org</a></span><br>
<span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee</a></span><br>
</div>
</blockquote>
</div>
</div>
</body>
</html>