It sounds to me like you are describing how a developer uses Keystone, not
a user. My reference to 'application deployer' was to someone trying to run
something like a mail server on an openstack cloud.
On Aug 6, 2014 7:07 AM, "Russell Bryant" <> wrote:

> On 08/05/2014 06:13 PM, Kevin Benton wrote:
> > That makes sense. It's not quite a fair analogy though to compare to
> > reintroducing projects or tenants because Keystone endpoints aren't
> > 'user-facing' so to speak. i.e. a regular user (application deployer,
> > instance operator, etc) should never have to see or understand the
> > purpose of a Keystone endpoint.
> An end user that is consuming any OpenStack API absolutely must
> understand endpoints in the service catalog.  The entire purpose of the
> catalog is so that an application only needs to know the API endpoint to
> keystone and is then able to discover where the rest of the APIs are
> located.  They are very much user facing, IMO.
> --
> Russell Bryant
> _______________________________________________
> OpenStack-dev mailing list
OpenStack-dev mailing list

Reply via email to