<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 08/18/2014 04:57 PM, Matthew
Treinish wrote:<br>
</div>
<blockquote cite="mid:20140818205758.GA16145@Sazabi.treinish"
type="cite">
<pre wrap="">On Sat, Aug 16, 2014 at 06:27:19PM +0200, Marc Koderer wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi all,
Am 15.08.2014 um 23:31 schrieb Jay Pipes <a class="moz-txt-link-rfc2396E" href="mailto:jaypipes@gmail.com"><jaypipes@gmail.com></a>:
</pre>
<blockquote type="cite">
<pre wrap="">
I suggest that "tempest" should be the name of the import'able library, and that the integration tests themselves should be what is pulled out of the current Tempest repository, into their own repo called "openstack-integration-tests" or "os-integration-tests“.
</pre>
</blockquote>
<pre wrap="">
why not keeping it simple:
tempest: importable test library
tempest-tests: all the test cases
Simple, obvious and clear ;)
</pre>
</blockquote>
<pre wrap="">
While I agree that I like how this looks, and that it keeps things simple, I
don't think it's too feasible. The problem is the tempest namespace is already
kind of large and established. The libification effort, while reducing some of
that, doesn't eliminate it completely. So what this ends meaning is that we'll
have to do a rename for a large project in order to split certain functionality
out into a smaller library. Which really doesn't seem like the best way to do
it, because a rename is a considerable effort.
Another wrinkle to consider is that the tempest namespace on pypi is already in
use: <a class="moz-txt-link-freetext" href="https://pypi.python.org/pypi/Tempest">https://pypi.python.org/pypi/Tempest</a> so if we wanted to publish the library
as tempest we'd need to figure out what to do about that.
-Matt Treinish</pre>
</blockquote>
Yes, I agree. Tempest is also used by Refstack, Rally, and I'm sure
many other parts of our ecosystem. I would vote for tempest-lib as
the library and keeping tempest to mean the same thing in the
ecosystem as it does at present. I would also not be opposed to a
different name than tempest-lib if it were related to its function.<br>
<br>
-David<br>
<blockquote cite="mid:20140818205758.GA16145@Sazabi.treinish"
type="cite">
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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>