Open Stack

What's the point of a service catalog (list of endpoints) if we don't want
to use it?! Looking up endpoints should be a cacheable request and in the
grand scheme of things -- low impact.

Nate
On Jun 18, 2012 10:13 AM, "Kevin L. Mitchell" <kevin.mitchell at rackspace.com>
wrote:

> On Fri, 2012-06-15 at 20:54 -0400, Lars Kellogg-Stedman wrote:
> > Thanks for the reply, makes sense.  Just to make sure I understand
> > things, it sounds like Nova does not currently query Keystone for
> > endpoints and continues to rely on explicit configuration (or to
> > rephrase your answer, "the reason these options have not gone away is
> > because Nova does not yet have the necessary support for Keystone").
> > Is that approximately correct?
>
> The problem with the Keystone endpoints is that you have to make a query
> to Keystone to get them.  We want to reduce the number of hits we make
> on Keystone, not increase them—there are already too many as it is.
> Thus, I suspect that nova may not even use the Keystone endpoints.  It
> *does* support image URLs, however.  Thus, you use the options to
> configure the default glance endpoint, and if you want to hit another
> glance, you simply give a URL to the desired image rather than a simple
> identifier.
>
> (My comments about the support for endpoints in this email may differ
> from my previous comments; chalk that up to further reflection on the
> problem being solved…)
> --
> Kevin L. Mitchell <kevin.mitchell at rackspace.com>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120618/adb867e0/attachment.html>