Hi, I've created a patch for qcow2 on scenario tests part.[1] But I'd like to know someone already do like this or not because I'd like to avoid conflict works. [1] https://review.openstack.org/#/c/75312/ On Fri, Feb 21, 2014 at 7:01 AM, David Kranz <dkranz at redhat.com> wrote: > On 02/20/2014 04:53 PM, Sean Dague wrote: >>> On 02/20/2014 04:31 PM, David Kranz wrote: >>>>> Running this test in tempest requires an ami image triple to be on the >>> disk where tempest is running in order for the test to upload it. It >>> would be a lot easier if this test could use a simple image file >>> instead. That image file could even be obtained from the cloud being >>> tested while configuring tempest. Is there a reason to keep the >>> three-part image? >>>>> I have no issue changing this to a single part image, as long as we >> could find a way that we can make it work with cirros in the gate >> (mostly because it can run in really low mem footprint). >>>> Is there a cirros single part image somewhere? Honestly it would be much >> simpler even in the devstack environment. >>>> -Sean >>> http://download.cirros-cloud.net/0.3.1/cirros-0.3.1-x86_64-disk.img >>>> _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Masayuki Igawa -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140221/4734a6c5/attachment.html>