[openstack-dev] [QA][ec2-api][nova] Future of Tempest ec2 tests
alexandrelevine at gmail.com
Mon Oct 12 15:10:27 UTC 2015
I'd like to provide you with some info in regard to standalone EC2 API part.
I can't claim clear understanding of tempest development directions but
here are the things to take in account about EC2 API:
1. Standalone EC2 API carry all of its tests including previously
tempest ones as in-project functional tests.
2. As far as I recall all of the original tempest EC2 API tests are
covered. (not true for all S3 tests, though)
3. We're trying to use RefStack for checking EC2 API compatibility as
well. And RefStack works with tempest tests so we'd have to somehow
connect our tests with RefStack.
Most probably I'll be in Tokyo if you'd want to discuss it in more details.
On 10/12/15 5:41 PM, Matthew Treinish wrote:
> Hi everyone,
> I think it's time we revisit having ec2 api tests in the tempest tree. They have
> always been something that was really out of scope for tempest, since tempest is
> about using and testing the OpenStack APIs, not OpenStack's implementation of
> amazon's APIs. We only kept these tests around because nova was still providing
> and "supporting" the ec2 implementation in tree. However, with nova deprecating
> their ec2 api implementation and the start of the standalone ec2-api project as
> well as the start of the tempest external test plugin interface I think mitaka
> is the time to drop the in-tree tempest support for ec2 and movign it to an
> external plugin.
> I'd like to have the tempest tests fully moved to an external plugin and out of
> the tempest tree by mitaka-1. To that end I started the work of creating a
> and pushed up patches to remove ec2 from tempest:
> and a test patch using the plugin:
> (look at the periodic-tempest-dsvm-all-master results)
> The plugin doesn't quite work yet, since I just copy and pasted the test code,
> so there are a couple things that still need to be fixed. But I got all of it
> importing correctly and it attempts to run all the tests.
> But, I really need someone to take things over, since I have limited time to
> continue pushing this, and definitely don't have the throughput to continue
> maintaining the plugin after we get things working. What I have up on github
> should be a good starting point that's easy to take over.
> Matthew Treinish
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev