<div dir="ltr">Alex,<div><br></div><div><br></div><div><blockquote 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" class="gmail_quote"> * rally plugin should be a part of project (for example, located in functional tests directory)</blockquote><div><br></div><div>There are 2 issues with such solution: </div><div><br></div><div> 1) If rally didn't load plugin, command "rally verify <project>" won't exist </div><div> 2) Putting some strange Rally plugin to source of other projects will be quite complicated task. </div><div> I believe we should have at least POC before even asking for such stuff. </div><div><br></div><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 style="font-size:12.8000001907349px"> * use {project url} instead of {project name} in rally verify command, example:</span></blockquote><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">I agree here with Andrey, it is bad UX. Forcing people to write every time URLs is terrible. </span></div><div><span style="font-size:12.8000001907349px">They will build own tools on top of such solution. </span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">What about "rally verify nova start --url <....>" where --url is optional argument?</span></div><div><span style="font-size:12.8000001907349px">If "--url" is not specified default url is used. </span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">Best regards,</span></div><div><span style="font-size:12.8000001907349px">Boris Pavlovic </span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><br></div><div><br></div><div><br></div><div><br></div><span style="font-size:12.8000001907349px"></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 11, 2015 at 7:14 PM, Andrey Kurilin <span dir="ltr"><<a href="mailto:akurilin@mirantis.com" target="_blank">akurilin@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class="">> $ rally verify <a href="https://github.com/openstack/nova" target="_blank">https://github.com/openstack/nova</a> start<br><br></span>As one of end-users of Rally, I dislike such construction, because I don't want to remember links to repos, they are too long for me:)<br></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Wed, Mar 11, 2015 at 12:49 PM, Aleksandr Maretskiy <span dir="ltr"><<a href="mailto:amaretskiy@mirantis.com" target="_blank">amaretskiy@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>The idea is great, but IMHO we can move all project-specific code out of rally, so:<br><br> * rally plugin should be a part of project (for example, located in functional tests directory)<br></div> * use {project url} instead of {project name} in rally verify command, example:<br><br></div> $ rally verify <a href="https://github.com/openstack/nova" target="_blank">https://github.com/openstack/nova</a> start<br><br></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 10, 2015 at 6:01 PM, Timur Nurlygayanov <span dir="ltr"><<a href="mailto:tnurlygayanov@mirantis.com" target="_blank">tnurlygayanov@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>I like this idea, we use Rally for OpenStack clouds verification at scale and it is the real issue - how to run all functional tests from each project with the one script. If Rally will do this, I will use Rally to run these tests.</div><div><br></div><div>Thank you!</div></div><div class="gmail_extra"><div><div><br><div class="gmail_quote">On Mon, Mar 9, 2015 at 6:04 PM, Chris Dent <span dir="ltr"><<a href="mailto:chdent@redhat.com" target="_blank">chdent@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Mon, 9 Mar 2015, Davanum Srinivas wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2. Is there a "test" project with Gabbi based tests that you know of?<br>
</blockquote>
<br></span>
In addition to the ceilometer tests that Boris pointed out gnocchi<br>
is using it as well:<br>
<br>
<a href="https://github.com/stackforge/gnocchi/tree/master/gnocchi/tests/gabbi" target="_blank">https://github.com/stackforge/<u></u>gnocchi/tree/master/gnocchi/<u></u>tests/gabbi</a><span><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
3. What changes if any are needed in Gabbi to make this happen?<br>
</blockquote>
<br></span>
I was unable to tell from the original what "this" is and how gabbi<br>
is involved but the above link ought to be able to show you how<br>
gabbi can be used. There's also the docs (which could do with some<br>
improvement, so suggestions or pull requests welcome):<br>
<br>
<a href="http://gabbi.readthedocs.org/en/latest/" target="_blank">http://gabbi.readthedocs.org/<u></u>en/latest/</a><span><font color="#888888"><br>
<br>
-- <br>
Chris Dent tw:@anticdent freenode:cdent<br>
<a href="https://tank.peermore.com/tanks/cdent" target="_blank">https://tank.peermore.com/<u></u>tanks/cdent</a><br>
<br>
______________________________<u></u>______________________________<u></u>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.<u></u>openstack.org?subject:<u></u>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div></div></div><span><font color="#888888">-- <br><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><font color="#888888"><font color="#888888"><br></font></font><div style="font-family:arial;font-size:small">Timur,</div><div style="font-family:arial;font-size:small">Senior QA Engineer</div><div style="font-family:arial;font-size:small">OpenStack Projects</div><div style="font-family:arial;font-size:small">Mirantis Inc</div></div></div></div></div></div></div>
</font></span></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a 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>
<br></blockquote></div><br></div>
</div></div><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a 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>
<br></blockquote></div><br><br clear="all"><br>-- <br></div></div><div><div dir="ltr">Best regards,<br>Andrey Kurilin.<br></div></div>
</div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a 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>
<br></blockquote></div><br></div>