<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">Hi Mark,<br>
<br>
I'd like to get ~ the same coverage for the api+reg as we have for
api+sqlalchemy. The problem is that currently we are not running
any functional tests against v2 api+reg. I tried to enable the v2
tests there is for registry as well, but due to some fundamental
differences they will not work with noauth like they do on v1.<br>
<br>
BR,<br>
Erno<br>
<br>
On 18/04/14 16:23, Mark Washenberger wrote:<br>
</div>
<blockquote
cite="mid:CAJyP2C92_wM6R8C1voEwKvKML7o41o7j8SimGUVWQmnSag24UQ@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div dir="ltr">Hi Erno,
<div><br>
</div>
<div>Just looking for a little more information here. What are
the particular areas around keystone integration in the v2
api+registry stack that you want to test? Is the v2 api + v2
registry stack using keystone differently than how v1 api + v1
registry stack uses it?</div>
<div><br>
</div>
<div>Thanks</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Fri, Apr 18, 2014 at 6:35 AM, Erno
Kuvaja <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:kuvaja@hp.com" target="_blank">kuvaja@hp.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
I have been trying to enable functional testing for Glance
API v2 using data_api = glance.db.registry.api without great
success.<br>
<br>
The current functionality of the v2 api+reg relies on the
fact that keystone is used and our current tests does not
facilitate that expectation.<br>
<br>
I do not like either option I have managed to come up with
so now is time to call for help. Currently only way I see we
could run the registry tests is to convert our functional
tests using keystone instead of noauth or write test suite
that passes API server and targets the registry directly.
Neither of these are great as starting keystone would make
the already long taking functional tests even longer and
more resource hog on top of that we would have a need to
pull in keystone just to run glance tests; on the other hand
bypassing API server would not give us any guarantee that
the behavior of the glance is the same regardless which
data_api is used.<br>
<br>
At this point any ideas/discussion would be more than
welcome how we can make these tests running on both
configurations.<br>
<br>
Thanks,<br>
Erno<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:OpenStack-dev@lists.openstack.org"
target="_blank">OpenStack-dev@lists.openstack.org</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>
</blockquote>
</div>
<br>
</div>
<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>