<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Agreed on a separate repo.<br>
<br>
I'm honestly a little unsure how in-service-repo would ever work
long<br>
term, given that tempest's requirements will match master, and may<br>
not be compatible with N releases ago's $service requirements..<br>
<br>
Thoughts on how that might work, or is it just that no service has
had<br>
an in-repo plugin for long enough to hit this yet?<br>
<br>
Thanks,<br>
Kiall<br>
<br>
On 04/04/16 17:16, Andrea Frittoli wrote:<br>
</div>
<blockquote
cite="mid:CAB7WYGUU_-nGXCKCtHtwDbGztY7e=7hChjSp5X7DNdk=4fBX4A@mail.gmail.com"
type="cite">
<div dir="ltr">I look forward to the first (as far as I
know) tempest plugin for a service in its own repo! :)
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Mon, Apr 4, 2016 at 4:49 PM Hayes, Graham <<a
moz-do-not-send="true" href="mailto:graham.hayes@hpe.com"><a class="moz-txt-link-abbreviated" href="mailto:graham.hayes@hpe.com">graham.hayes@hpe.com</a></a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On
04/04/2016 16:36, Jordan Pittier wrote:<br>
><br>
> On Mon, Apr 4, 2016 at 5:01 PM, Hayes, Graham <<a
moz-do-not-send="true" href="mailto:graham.hayes@hpe.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:graham.hayes@hpe.com">graham.hayes@hpe.com</a></a><br>
> <mailto:<a moz-do-not-send="true"
href="mailto:graham.hayes@hpe.com" target="_blank">graham.hayes@hpe.com</a>>>
wrote:<br>
><br>
> As we have started to move to a tempest plugin for
our functional test<br>
> suite, we have 2 choices about where it lives.<br>
><br>
> 1 - In repo (as we have [0] currently)<br>
> 2 - In a repo of its own (something like
openstack/designate-tempest)<br>
><br>
> There are several advantages to a separate repo:<br>
><br>
> * It will force us to make API changes compatable<br>
> * * This could cause us to be slower at merging
changes [1]<br>
> * It allows us to be branchless (like tempest is)<br>
> * It can be its own installable package, and a (much)
shorter list<br>
> of requirements.<br>
><br>
> I am not a Designate contributor, but as a Tempest
contributor we<br>
> recommend to use a separate repo. See<br>
> <a moz-do-not-send="true"
href="http://docs.openstack.org/developer/tempest/plugin.html#standalone-plugin-vs-in-repo-plugin"
rel="noreferrer" target="_blank">http://docs.openstack.org/developer/tempest/plugin.html#standalone-plugin-vs-in-repo-plugin</a><br>
> for more details.<br>
<br>
Yeap - that was one of the reasons I will leaning towards the
separate<br>
repo. The only thing stopping us was that I cannot see any
other project<br>
who does it [2]<br>
<br>
We just had a quick discussion in IRC[3] and we are going to
go with<br>
the separate repo anyway.<br>
<br>
2 -<br>
<a moz-do-not-send="true"
href="http://codesearch.openstack.org/?q=%5Etempest&i=nope&files=setup.cfg&repos="
rel="noreferrer" target="_blank">http://codesearch.openstack.org/?q=%5Etempest&i=nope&files=setup.cfg&repos=</a><br>
3 -<br>
<a moz-do-not-send="true"
href="http://eavesdrop.openstack.org/irclogs/%23openstack-dns/%23openstack-dns.2016-04-04.log.html#t2016-04-04T15:05:38"
rel="noreferrer" target="_blank">http://eavesdrop.openstack.org/irclogs/%23openstack-dns/%23openstack-dns.2016-04-04.log.html#t2016-04-04T15:05:38</a><br>
<br>
<br>
> If everyone is OK with a separate repo, I will go
ahead and start the<br>
> creation process.<br>
><br>
> Thanks<br>
><br>
> - Graham<br>
><br>
><br>
> 0 - <a moz-do-not-send="true"
href="https://review.openstack.org/283511" rel="noreferrer"
target="_blank">https://review.openstack.org/283511</a><br>
> 1 -<br>
> <a moz-do-not-send="true"
href="http://docs.openstack.org/developer/tempest/HACKING.html#branchless-tempest-considerations"
rel="noreferrer" target="_blank">http://docs.openstack.org/developer/tempest/HACKING.html#branchless-tempest-considerations</a><br>
><br>
>
__________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage
questions)<br>
> Unsubscribe:<br>
> <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <<a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank">http://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"
rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
<br>
<br>
__________________________________________________________________________<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"
rel="noreferrer" 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"
rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</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>