From a6b4b8f04295897e04e64cec95167098ffae7bfc Mon Sep 17 00:00:00 2001 From: Brian Rosmaita Date: Sat, 7 Feb 2015 20:33:01 +0000 Subject: [PATCH] Clarified doc of public_endpoint config option Rewrote description of the public_endpoint configuration option to make the purpose of the setting more explicit. Change-Id: Ic4d5ce9884b6641eed076e5b6fad71ec0e6659a4 Closes-Bug: #1419328 --- doc/source/configuring.rst | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/doc/source/configuring.rst b/doc/source/configuring.rst index 297352a097..b401c6b009 100644 --- a/doc/source/configuring.rst +++ b/doc/source/configuring.rst @@ -1402,10 +1402,14 @@ profiling will not be triggered even profiling feature is enabled. Configuring Glance public endpoint ---------------------------------- -When Glance API service is ran behind a proxy, operator probably need to -configure a proper public endpoint to versions URL instead of use host owned -which run service really. Glance allows configure a public endpoint URL to -represent the proxy's URL. +This setting allows an operator to configure the endpoint URL that will +appear in the Glance "versions" response (that is, the response to +``GET /``\ ). This can be necessary when the Glance API service is run +behind a proxy because the default endpoint displayed in the versions +response is that of the host actually running the API service. If +Glance is being run behind a load balancer, for example, direct access +to individual hosts running the Glance API may not be allowed, hence the +load balancer URL would be used for this value. * ``public_endpoint=``