<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 2/2/15 8:30 PM, Matthew Treinish
wrote:<br>
</div>
<blockquote cite="mid:20150202173025.GA1229@sazabi.kortar.org"
type="cite">
<pre wrap="">On Mon, Feb 02, 2015 at 07:35:46PM +0300, Alexandre Levine wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Thank you Sean.
We'll be tons of EC2 Tempest tests for your attention shortly.
How would you prefer them? In several reviews, I believe. Not in one, right?
</pre>
</blockquote>
<pre wrap="">
Let's take a step back for a sec. How many tests and what kind are we talking
about here?
</pre>
</blockquote>
We've got our root in /tempest/thirdparty/aws/ec2 (which we
considered a better naming than boto) and it works via botocore (so
no boto in any case).<br>
12 files with 79 API tests.<br>
However we've got additionally some amount of complex scenario tests
as well, unfortunately using boto, not botocore. Most of them though
are about VPC stuff so those we'll run against our stackforge's EC2
only.<br>
<br>
Please let us know where and how to put it.<br>
<br>
<blockquote cite="mid:20150202173025.GA1229@sazabi.kortar.org"
type="cite">
<pre wrap="">
I'm thinking it might be better to not just try and dump all this stuff in
tempest. While in the past we've just dumped all of this in tempest, moving
forward I don't think that's what we want to be doing. The current ec2 tests
have always felt out of place to me in tempest and historically haven't been
maintained as well as the other tests. If we're talking about ramping up the ec2
testing we probably should look at migrating everything elsewhere, especially
given that it just essentially nova testing. I see 2 better options here: we
either put the tests in the tree for the project with the ec2 implementation, or
we create a new repo like tempest-ec2 for testing this. In either case we'll
leverage tempest-lib to make sure the bits your existing testing is relying on
are consumable outside of the tempest repo.
-Matt Treinish
</pre>
<blockquote type="cite">
<pre wrap="">On 2/2/15 6:55 PM, Sean Dague wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 02/02/2015 07:01 AM, Alexandre Levine wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Michael,
I'm rather new here, especially in regard to communication matters, so
I'd also be glad to understand how it's done and then I can drive it if
it's ok with everybody.
By saying EC2 sub team - who did you keep in mind? From my team 3
persons are involved.
>From the technical point of view the transition plan could look somewhat
like this (sequence can be different):
1. Triage EC2 bugs and fix showstoppers in nova's EC2.
2. Contribute Tempest tests for EC2 functionality and employ them
against nova's EC2.
3. Write spec for required API to be exposed from nova so that we get
full info.
4. Triage and fix all of the existing nova's EC2 bugs worth fixing.
5. Set up Tempest testing of the stackforge/ec2 (if that's possible).
6. Communicate and discover all of the existing questions and
problematic points for the switching from existing EC2 API to the new
one. Provide solutions or decisions about them.
7. Do performance testing of the new stackforge/ec2 and provide fixes if
any bottlenecks come up.
8. Have all of the above prepared for the Vancouver summit and discuss
the situation there.
Michael, I am still wondering, who's going to be responsible for timely
reviews and approvals of the fixes and tests we're going to contribute
to nova? So far this is the biggest risk. Is there anyway to allow some
of us to participate in the process?
</pre>
</blockquote>
<pre wrap="">I am happy to volunteer to shephard these reviews. I'll try to keep an
eye on them, and if something is blocking please just ping me directly
on IRC in #openstack-nova or bring them forward to the weekly Nova meeting.
-Sean
</pre>
</blockquote>
<pre wrap="">
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
</blockquote>
<br>
</body>
</html>