I am certainly up for helping with this effort. I wondered about this approach:
* Starting with Tempest (mostly for its reporting, and configuration) * Creating a new category "EC2_Compat" or something like that * Trying to add in all the tests from those two repos into the new thing * Looking at what the gaps are I am not sure it makes sense for these tests to leave in tempest, but it does seem silly to create our own set of configuration and test runner code, if we don't have to. Seems too early to push this shared code into something like openstack-common-tests, but maybe that is what we need long term? A totally different approach, that sounds attractive, is testing with some of the tools people actually want to use: boto, eucatools. However, this does then mean you end up writing N times as many tests, and it means you have to somehow pick which tools you want to test. Maybe the tests are easier to write, so the fact there is more doesn't matter. While those tests don't really test if we comply with ec2, maybe they do test what people care about. Cheers, John From: openstack-bounces+john.garbutt=eu.citrix....@lists.launchpad.net [mailto:openstack-bounces+john.garbutt=eu.citrix....@lists.launchpad.net] On Behalf Of Joshua Harlow Sent: 07 May 2012 18:17 To: Doug Hellmann; Martin Packman Cc: openstack Subject: Re: [Openstack] [Nova] EC2 api testing TBD afaik. I think it would be nice if we could have one tool to rule them all, but I need to get my hands on this enstrsatus thingy to see what is there :-) I've started documenting some EC2 stuff that I see @ https://github.com/yahoo/Openstack-EC2/issues If others want to put stuff on there (or a better location, that's cool with me). On 5/4/12 3:04 PM, "Doug Hellmann" <doug.hellm...@dreamhost.com> wrote: On Fri, May 4, 2012 at 1:09 PM, Martin Packman <martin.pack...@canonical.com> wrote: At the Folsom Design Summit we discussed[1] trying to collaborate on a test suite for EC2 api support. Currently nova supports the common stuff pretty well has differing behaviour in a lot of edge cases. Having a separate suite, along the lines of tempest, that could be run against other existing clouds as well as OpenStack would let us test the tests as well, and would be useful for other projects. Various parties have done work in this direction in the past, the trick is going to be combining it into something we can all use. The existing code I know about includes aws-compat[2], Openstack-EC2[3], the tests in nova itself, some experimental code in awsome, and an Enstratus test suite. I'm hoping to find out more about the Enstratus code, James Urquhart suggested opening the remaining parts would be a reasonable step. Is there anything else out there we should look at as well? Are there any strong opinions over the right way of getting started on this? Are you going to try to get all of the code for those projects into one package, or build a meta-tool that downloads the others and uses them? I don't have an opinion one way or the other, I'm just curious. Doug Martin [1] Nova EC2 compatibility sesson etherpad <http://etherpad.openstack.org/FolsomEC2Compatibility> [2] <https://github.com/cloudscaling/aws-compat> [3] <https://github.com/yahoo/Openstack-EC2> _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
