[all] Train goal: removing and simplifying the endpoint tripplets?

Thomas Goirand zigo at debian.org
Thu Mar 28 15:49:31 UTC 2019


During the summit in Tokyo (if I remember well), Sean Dague lead a
discussion about removing the need for having 3 endpoints per service. I
was very excited about the proposal, and it's IMO a shame it hasn't been
implemented. Everyone in the room agreed. Here the content of the
discussion as I remember it:

<discussion in Tokyo>
1/ The only service that needed the admin endpoint was Keystone. This
requirement is now gone. So we could get rid of the admin endpoint all

2/ The need for an interal vs public endpoint was only needed for
accounting (of for example bandwidth when uploading to Glance), but this
could be work-around by operators by using intelligent routing. So we
wouldn't need the internal endpoint.

This makes us only need the public endpoint, and that's it.

Then, there are these %(tenant_id)s bits in the endpoints which are also
very much annoying, and could be removed if the clients were smarter.
These are still needed, apparently, for:
- cinder
- swift
- heat
</discussion in Tokyo>

Is anyone planning to implement (at least some parts of) the above?


Thomas Goirand (zigo)

More information about the openstack-discuss mailing list