Mu understanding of Keystone is rudimentary, please comment to clarify it for me.
If public_endpoint or admin_endpoint is not set as Adam mentioned host_url is used and we get the correct url (in case if there is no addition in path, but it's a different story). But in fact this situation hides a real problem.
If these values are set, endpoint_type is used to construct the url and endpoint_type is *always* 'admin' now. In service.py
we create an app with 2 identical routers inside and from my experience the first one is always returned to process a request. I've changed order of append() and started get 'public' Version app always. Obviously, I'm missing something here, but I don't understand that design.
We always deploy 2 (sub)apps (admin and public) on every server, even if admin_bind_host and public_bind_host (deprecated, what should I use instead?) are specified. Those 2 apps identical and the only one is used. So, perhaps we should get rid of the second one?
Mu understanding of Keystone is rudimentary, please comment to clarify it for me.
If public_endpoint or admin_endpoint is not set as Adam mentioned host_url is used and we get the correct url (in case if there is no addition in path, but it's a different story). But in fact this situation hides a real problem.
If these values are set, endpoint_type is used to construct the url and endpoint_type is *always* 'admin' now. In service.py
http:// git.openstack. org/cgit/ openstack/ keystone/ tree/keystone/ service. py#n114
we create an app with 2 identical routers inside and from my experience the first one is always returned to process a request. I've changed order of append() and started get 'public' Version app always. Obviously, I'm missing something here, but I don't understand that design.
We always deploy 2 (sub)apps (admin and public) on every server, even if admin_bind_host and public_bind_host (deprecated, what should I use instead?) are specified. Those 2 apps identical and the only one is used. So, perhaps we should get rid of the second one?