<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body dir="auto">
<div>+1 to not having nova be the "all the things" proxy. Hopefully openstack client can help here, and its usage where needed/applicable.<br>
<br>
Sent from my really tiny device...</div>
<div><br>
On Aug 5, 2013, at 12:20 PM, "Joe Gordon" <<a href="mailto:joe.gordon0@gmail.com">joe.gordon0@gmail.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, Aug 5, 2013 at 9:11 AM, Roman Bogorodskiy <span dir="ltr">
<<a href="mailto:rbogorodskiy@mirantis.com" target="_blank">rbogorodskiy@mirantis.com</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">
<div class="im"> Joe Gordon wrote:<br>
<br>
> Hi All,<br>
><br>
> even though Glance, has been pulled out of Nova years ago, Nova still has a<br>
> images API that proxies back to Glance. Since Nova is in the process of<br>
> creating a new, V3, API, we know have a chance to re-evaluate this API.<br>
><br>
> * Do we still need this in Nova, is there any reason to not just use Glance<br>
> directly? I have vague concerns about making Glance API publicly<br>
> accessible, but I am not sure what the underlying reason is<br>
<br>
</div>
>From the end user point of view, images are strongly tied to<br>
logical models nova operates with, such as servers, flavors etc. So for<br>
an API user, it would be move convenient to manage all these in a<br>
single API, IMHO.<br>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>-1, I think Monty stated this well </div>
<div><br>
</div>
<div>"<span style="font-family:arial,sans-serif;font-size:13px">Honestly, I think we should ditch it. Glance is our image service, not</span></div>
<span style="font-family:arial,sans-serif;font-size:13px">nova, we should use it. For user-experience stuff,</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">python-openstackclient should be an excellent way to expose both through</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">a single tool without needing to proxy one service through another."</span></div>
<div class="gmail_quote"><font face="arial, sans-serif"><br>
</font></div>
<div class="gmail_quote"><font face="arial, sans-serif">We don't want nova to be the proxy for all other services, that partially defeats the purpose of splitting them off. We have better ways of making everything look like a single API, such as:</font></div>
<div class="gmail_quote"><font face="arial, sans-serif"><br>
</font></div>
<div class="gmail_quote"><font face="arial, sans-serif">* better python-openstackclient</font></div>
<div class="gmail_quote"><font face="arial, sans-serif">* Make sure all services can run as one endpoint, on the same port. So a REST call to $IP/images/ would go to glance and a call to $IP/instances would go to nova </font></div>
<div class="gmail_quote"><font face="arial, sans-serif"><br>
</font>
<div> </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">
<div class="im"><br>
> * If it is still needed in Nova today, can we remove it in the future and<br>
> if so what is the timeline?<br>
><br>
> best,<br>
> Joe Gordon<br>
<br>
</div>
<div class="">
<div class="h5">> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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>
<br>
</div>
</div>
<span class=""><font color="#888888">Roman Bogorodskiy<br>
</font></span><br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>OpenStack-dev mailing list</span><br>
<span><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a></span><br>
<span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></span><br>
</div>
</blockquote>
</body>
</html>