Open Stack

?Jean-Daniel,


Actually, I needed to take a step back to catch one important detail that I missed.


"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."


All the original thoughts I had still hold true, but the purpose of the DefCore tests is too identify non-standard behavior from the cloud-under-test, which it did. The question of whether this particular snag is relevant for interop is still valid.


Daryl


________________________________
From: Catherine Cuong Diep <cdiep at us.ibm.com>
Sent: Thursday, March 10, 2016 9:42 AM
To: Daryl Walleck
Cc: Jean-Daniel Bonnetot; defcore-committee at lists.openstack.org
Subject: Fw: [OpenStack-DefCore] Discussing tests


I think the question for DefCore to review is:

Is "being able to delete an image that is not done saving " an important capability for interoperability ?

Catherine Diep
IBM Silicon Valley Laboratory, San Jose, California 95141
cdiep at us.ibm.com, Tel: (408) 463-4352 T/L: 543-4352
----- Forwarded by Catherine Cuong Diep/San Jose/IBM on 03/10/2016 07:37 AM -----

From: Daryl Walleck <daryl.walleck at RACKSPACE.COM>
To: Jean-Daniel Bonnetot <jean-daniel.bonnetot at corp.ovh.com>, "defcore-committee at lists.openstack.org" <defcore-committee at lists.openstack.org>
Date: 03/10/2016 07:25 AM
Subject: Re: [OpenStack-DefCore] Discussing tests

________________________________



My understanding of that test is that it is validating the system behavior being able to delete an image that is not done saving.

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.

Daryl

From: Jean-Daniel Bonnetot<mailto:jean-daniel.bonnetot at corp.ovh.com>
Sent: Thursday, March 10, 2016 9:05 AM
To: defcore-committee at lists.openstack.org<mailto:defcore-committee at lists.openstack.org>
Subject: [OpenStack-DefCore] Discussing tests

Hi defcore,

Not sure it's the right place to discuss about it but I try ;)

I'm using refstack to test our Public Cloud at OVH and I have question about a test which make trouble on our solution.

I run the 2015.07 guidelines.
The test is tempest.api.compute.images.test_images.ImagesTestJSON.test_delete_saving_image.

I saw this test corresponds to the compute-images-delete capability.
I understand that image deletion is required, but why the test is deletion on a saving image?

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.
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.

compute-images-delete is marked as atomic but it's not from my point of view.


--
Jean-Daniel Bonnetot
http://www.ovh.com<http://www.ovh.com/>
@pilgrimstack




_______________________________________________
Defcore-committee mailing list
Defcore-committee at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee_______________________________________________
Defcore-committee mailing list
Defcore-committee at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/defcore-committee/attachments/20160310/160b6fde/attachment.html>