[Openstack-operators] Service Catalog TNG urls

Xav Paice xavpaice at gmail.com
Mon Dec 7 10:41:39 UTC 2015

On 7 December 2015 at 14:33, Clint Byrum <clint at fewbar.com> wrote:

> Indeed, this is one paradigm where it actually creates a hardened core,
> not a squisy one, so I think it's not a terrible idea.
I tend to agree, just wish we were already there :)

> What I mean is, you'd just have two completely separate _services_,
> instead of one service, with two separate endpoint "interface" entries:
> <snip example>

I guess if the clients already have mechanisms to determine whether to use
the public url or the admin url, they can determine which service to look
up just the same.  However, that brings me back to wondering if there's any
real difference?   I'm missing something.  But like you say, if we don't
have Keystone running such that we trust it enough to call it hardened,
then that's a much more pressing issue.

What are other public cloud ops doing wrt public facing API services that
can expose admin type operations?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20151207/83801ed9/attachment.html>

More information about the OpenStack-operators mailing list