Missed configuration examples for internal and admin endpoints

[Annie Melen]

Greetings!

Recently I’ve found out that official Designate Install Guide contains only public endpoint creation example, not internal and admin endpoints:

$ openstack endpoint create --region RegionOne \
  dns public http://controller:9001/

Is it strongly recommended to create only publicURL, or I can/should also create internal and admin URLs? I want to split out public and internal layers for all installing OpenStack APIs, so it looks like necessary to have three endpoints instead one…

Regards,
Annie

[Dr. Jens Harbott (j-harbott)]

The admin endpoint only ever made sense for keystone v2, since now keystone only supports v3, it should be dropped everywhere.

Regarding the internal endpoint, you can create it and use it e.g. when other services like Neutron talk to Designate, as opposed to the public endpoint which is mainly intended to be used by your end users.

This is a topic however which I think is more a general deployment related issue, the Designate Installation Guide only provides instructions for setting up a simple demo deployment, so adding information about the other endpoints seems to be out of scope for me.

[Annie Melen (anniemelen)]

Thanks for quick response!

Indeed, I have Identity API v3 so I don't care about admin endpoint, but looking at other OpenStack Install Guides, we can notice that all of them have internal endpoint creation example. I'm sure we should to add it to Designate Install Guide to minimize possible doubtes while configuring services...

Regards, Annie