<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Rushi,<br>
    <br>
    We're adding new tempest tests into our stackforge-api/ec2-api. The
    review will appear in a couple of days. These tests will be good for
    running against both nova/ec2-api and stackforge/ec2-api. As soon as
    they are there, you'll be more than welcome to add even more.<br>
    <br>
    Best regards,<br>
      Alex Levine<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 2/6/15 3:20 PM, Rushi Agrawal wrote:<br>
    </div>
    <blockquote
cite="mid:CAEtC-Yt8G0QAUwRcB+w6W3PJ+iaEp7bi-zKWAQfD+SvtcGK+Zw@mail.gmail.com"
      type="cite">
      <div dir="ltr">There seems to be an agreement that people are fine
        if we improve the in-tree Nova EC2 API more robust by adding
        proper Tempest tests to it, regardless of the way forward
        (in-Nova-tree vs out-of-tree repo).
        <div><br>
        </div>
        <div>But there are also concerns that Tempest is not the right
          place for these EC2 API tests. While I am not mature enough
          with testing methodologies to comment on what is good vs bad,
          I am seeing a problem if we start blocking new EC2 Tempest
          tests, and ask to move them out-of-Tempest first. This will
          particularly hurt the EC2-code-in-Nova camp (which includes
          me) who have seemingly been given a lifeline until the next
          summit to prove they care about in-tree EC2 code.</div>
        <div><br>
        </div>
        <div>So I just wanted to know what does concerned people think
          about this problem. On solution I can see is allow tests to be
          added to Tempest for now, and then make the switch
          post-summit. I am hoping moving tests out of Tempest at-once
          wouldn't be a tough job (mostly tidying import statements?). </div>
        <div><br>
        </div>
        <div>
          <div class="gmail_extra">Regards,<br>
            Rushi Agrawal</div>
          <div class="gmail_extra">Cloud Engineer,</div>
          <div class="gmail_extra">Reliance Jio Infocomm</div>
        </div>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On 5 February 2015 at 19:41, Sean
            Dague <span dir="ltr"><<a moz-do-not-send="true"
                href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span
                class="">On 02/05/2015 07:01 AM, Alexandre Levine wrote:<br>
                > Davanum,<br>
                ><br>
                > We've added the devstack support. It's in our
                stackforge repository.<br>
                > <a moz-do-not-send="true"
href="https://github.com/stackforge/ec2-api/tree/master/contrib/devstack"
                  target="_blank">https://github.com/stackforge/ec2-api/tree/master/contrib/devstack</a><br>
                ><br>
                > Best regards,<br>
                >   Alex Levine<br>
                <br>
              </span>I've converted it to a devstack external plugin
              structure in this review<br>
              - <a moz-do-not-send="true"
                href="https://review.openstack.org/#/c/153206/"
                target="_blank">https://review.openstack.org/#/c/153206/</a><br>
              <br>
              so that will make using this as simple as<br>
              <br>
              enable_plugin ec2-api <a moz-do-not-send="true"
                href="https://github.com/stackforge/ec2-api"
                target="_blank">https://github.com/stackforge/ec2-api</a><br>
              <br>
              Once that merges.<br>
              <span class=""><font color="#888888"><br>
                          -Sean<br>
                </font></span><span class="im"><br>
                --<br>
                Sean Dague<br>
                <a moz-do-not-send="true" href="http://dague.net"
                  target="_blank">http://dague.net</a><br>
                <br>
              </span>
              <div class="">
                <div class="h5">__________________________________________________________________________<br>
                  OpenStack Development Mailing List (not for usage
                  questions)<br>
                  Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
                    target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
                  <a moz-do-not-send="true"
                    href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
                    target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
        </div>
        <div class="gmail_extra"><br>
        </div>
      </div>
      <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>
    <br>
  </body>
</html>